diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2025-05-29 16:31:47 -0400 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2025-06-04 18:16:34 +0200 |
| commit | 2e887187454e57d04522099d4f04d17137d6e05c (patch) | |
| tree | b2f44be17bdf45353cc012fbf4338683ebc8d76f /python/scripts/vendor.py | |
| parent | b04b7c79c478743d414a684673519431b022c808 (diff) | |
| download | qemu-2e887187454e57d04522099d4f04d17137d6e05c.zip qemu-2e887187454e57d04522099d4f04d17137d6e05c.tar.gz qemu-2e887187454e57d04522099d4f04d17137d6e05c.tar.bz2 | |
iotests: fix 240
Commit 2e8e18c2e463 ("virtio-scsi: add iothread-vq-mapping parameter")
removed the limitation that virtio-scsi devices must successfully set
the AioContext on their BlockBackends. This was made possible thanks to
the QEMU multi-queue block layer.
This change broke qemu-iotests 240, which checks that adding a
virtio-scsi device with a drive that is already in another AioContext
will fail.
Update the test to take the relaxed behavior into account. I considered
removing this test case entirely, but the code coverage still seems
valuable.
Fixes: 2e8e18c2e463 ("virtio-scsi: add iothread-vq-mapping parameter")
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Tested-by: Eric Blake <eblake@redhat.com>
Message-ID: <20250529203147.180338-1-stefanha@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'python/scripts/vendor.py')
0 files changed, 0 insertions, 0 deletions