* [PATCH qemu-server] verify device removal: mention that device might still be busy in guest on failure
@ 2026-02-13 15:38 Fiona Ebner
0 siblings, 0 replies; only message in thread
From: Fiona Ebner @ 2026-02-13 15:38 UTC (permalink / raw)
To: pve-devel
A very likely reason for a device removal to time out is if the device
is still busy in the guest. In particular, as reported in [0], Windows
does not release a VirtIO block device when there is ongoing IO.
Increasing the timeout was considered, but during testing, either the
device was removed very quickly or not at all, so waiting longer can
be pointless and annoying.
[0]: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/1483#issuecomment-3897226530
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/QemuServer.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/QemuServer.pm b/src/PVE/QemuServer.pm
index 5d2dbe03..c2564f1f 100644
--- a/src/PVE/QemuServer.pm
+++ b/src/PVE/QemuServer.pm
@@ -4129,7 +4129,7 @@ sub qemu_devicedelverify {
sleep 1;
}
- die "error on hot-unplugging device '$deviceid'\n";
+ die "error on hot-unplugging device '$deviceid' - still busy in guest?\n";
}
sub qemu_findorcreatescsihw {
--
2.47.3
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-02-13 15:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-02-13 15:38 [PATCH qemu-server] verify device removal: mention that device might still be busy in guest on failure Fiona Ebner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.