Document current limitation of dedicatedIOThread on scsi disks #894
Conversation
kubevirt-bot
added
the
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Alice Frosi <afrosi@redhat.com>
alicefr
force-pushed
the
doc-limitation-iothread-scsi
branch
from
4518162 to
55c042f
Compare
| `IOThreads are not supported for disks on a %s bus`. The reason for this limitation | ||
| consists that KubeVirt supports a single scsi controller for all the disks using the | ||
| `scsi` bus, and QEMU does not support assigning each IOThreads to each scsi disks, | ||
| instead they can only be assigned at the controller level. |
There was a problem hiding this comment.
Any mechanism for setting it at the controller level available right now?
There was a problem hiding this comment.
Since we refuse at the webhook level when we set the dedicatedIOThread, no. The current code could assign a single iothread, like the emulatorThread. However, libvirt does support multiple iothreads for the controller, so we could enhance this mechanism. However, I do belive that this requires some API changes since it doesn't apply on a single disk but at the entire controller level.
|
/cc @alromeros |
Document current limitation when
dedicatedIOThreadsfield is specified on scsi devices. This behavior has been introduced by kubevirt/kubevirt#11219Release note: