-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.5
-
Yes
-
Important
-
CustomerScenariosInitiative
-
rhel-sst-virtualization-windows
-
ssg_virtualization
-
None
-
False
-
-
Yes
-
Red Hat Enterprise Linux
-
None
-
None
-
Automated
-
Unspecified Release Note Type - Unknown
-
-
x86_64
-
None
What were you trying to do that didn't work?
Win10-32 guest will hang when do cdrom unplug.
After do "{"execute": "device_del", "arguments":
, "id": "dDjraxMd"}" in qmp monitor, the vm hang.
Please provide the package NVR for which bug is seen:
kernel-5.14.0-472.el9.x86_64
qemu-kvm-9.0.0-5.el9.x86_64
virtio-win-prewhql-259
edk2-ovmf-20240524-1.el9.noarch
How reproducible:
100%
Steps to reproduce
1.Boot Win10-32 guest up.
"""
usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1' \
-machine q35,memory-backend=mem-machine_mem \
-device '
' \
-device '
' \
-nodefaults \
-device '
' \
-m 4096 \
-object '
' \
-smp 12,maxcpus=12,cores=6,threads=1,dies=1,sockets=2 \
-cpu 'EPYC',lm=off,pae=on,hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,hv-xmm-input,hv_tlbflush_ext,+kvm_pv_unhalt \
-chardev socket,path=/var/tmp/monitor-qmpmonitor1-20240815-063943-Vzp4KPNx,id=qmp_id_qmpmonitor1,server=on,wait=off \
-mon chardev=qmp_id_qmpmonitor1,mode=control \
-chardev socket,path=/var/tmp/monitor-catch_monitor-20240815-063943-Vzp4KPNx,id=qmp_id_catch_monitor,server=on,wait=off \
-mon chardev=qmp_id_catch_monitor,mode=control \
-device '
' \
-chardev socket,path=/var/tmp/serial-serial0-20240815-063943-Vzp4KPNx,id=chardev_serial0,server=on,wait=off \
-device '
' \
-chardev socket,id=seabioslog_id_20240815-063943-Vzp4KPNx,path=/var/tmp/seabios-20240815-063943-Vzp4KPNx,server=on,wait=off \
-device isa-debugcon,chardev=seabioslog_id_20240815-063943-Vzp4KPNx,iobase=0x402 \
-device '
' \
-device '
' \
-device '
' \
-device '
' \
-device '
' \
-blockdev '{"node-name": "file_image1", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/kvm_autotest_root/images/win10-32-virtio-scsi.qcow2", "cache": {"direct": true, "no-flush": false}}' \
-blockdev '{"node-name": "drive_image1", "driver": "qcow2", "read-only": false, "cache":
, "file": "file_image1"}' \
-device '
' \
-device '
' \
-device '
' \
-netdev '
' \
-blockdev '{"node-name": "file_cd2", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/kvm_autotest_root/iso/windows/virtio-win-1.9.10-0.el8.iso", "cache": {"direct": true, "no-flush": false}}' \
-blockdev '{"node-name": "drive_cd2", "driver": "raw", "read-only": true, "cache":
, "file": "file_cd2"}' \
-device '
' \
-vnc :0 \
-rtc base=localtime,clock=host,driftfix=slew \
-boot menu=off,order=cdn,once=c,strict=off \
-enable-kvm \
-device vmcoreinfo \
-monitor stdio \
-device '
'
"""
2. Hot-unplug cdrom via qmp monitor:
3. Check the vm status
Expected results
cdrom was unplugged successfully, and guest no hang
Actual results
Guest hang