diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2024-07-31 14:32:07 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2024-08-06 20:12:39 +0200 |
| commit | 9da6bd39f92434f55573acd017841b195c60188f (patch) | |
| tree | e1136427fba751347bee08a2f42e447502667d21 /hw/remote | |
| parent | 8a0495624f23f8f01dfb1484f367174f3b3572e8 (diff) | |
| download | qemu-9da6bd39f92434f55573acd017841b195c60188f.zip qemu-9da6bd39f92434f55573acd017841b195c60188f.tar.gz qemu-9da6bd39f92434f55573acd017841b195c60188f.tar.bz2 | |
scsi-disk: Always report RESERVATION_CONFLICT to guest
In the case of scsi-block, RESERVATION_CONFLICT is not a backend error,
but indicates that the guest tried to make a request that it isn't
allowed to execute. Pass the error to the guest so that it can decide
what to do with it.
Without this, if we stop the VM in response to a RESERVATION_CONFLICT
(as is the default policy in management software such as oVirt or
KubeVirt), it can happen that the VM cannot be resumed any more because
every attempt to resume it immediately runs into the same error and
stops the VM again.
One case that expects RESERVATION_CONFLICT errors to be visible in the
guest is running the validation tests in Windows 2019's Failover Cluster
Manager, which intentionally tries to execute invalid requests to see if
they are properly rejected.
Buglink: https://issues.redhat.com/browse/RHEL-50000
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <20240731123207.27636-5-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'hw/remote')
0 files changed, 0 insertions, 0 deletions