Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I can reproduce it with virtio-win-prewhql-0.1-214.
And it passed with virtio-win-prewhql-0.1-215 on the same host.
So it's driver issue and now was fixed. I'll change the component.
host version:
qemu-kvm-6.1.0-5.module+el8.6.0+13430+8fdd5f85.x86_64
kernel-4.18.0-353.el8.kpq1.x86_64
win2019 guest.
As virtio-win issue is generally tracked in one stream, so close it as duplicate of bz1996500
*** This bug has been marked as a duplicate of bug 1996500 ***
Description of problem: as $summary Version-Release number of selected component (if applicable): qemu-kvm-docs-6.0.0-27.module+el8.5.0+12121+c40c8708.x86_64 kernel-4.18.0-329.el8.x86_64 seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch virtio-win-prewhql-0.1-207 How reproducible: 100% Steps to Reproduce: 1. start virtiofsd daemon on host # /usr/libexec/virtiofsd --socket-path=/tmp/socket1 -o source=/home/test 2. Boot up win2019 guest without vhost-user-fs-pci device -device pcie-root-port,id=pcie_extra_root_port_0,multifunction=on,bus=pcie.0,addr=0x3,chassis=5 \ -chardev socket,id=char_virtiofs_fs,path=/tmp/socket1 \ 2. hotplug virtiofs device. {"execute":"device_add","arguments":{"driver":"vhost-user-fs-pci","id":"fs-pci1","bus":"pcie_extra_root_port_0","tag":"myfs","queue-size":"1024","chardev":"char_virtiofs_fs"}} {"return": {}} 3. hot unplug virtiofs device. {"execute":"device_del","arguments":{"id":"fs-pci1"}} {"return": {}} {"timestamp": {"seconds": 1629604708, "microseconds": 786991}, "event": "DEVICE_DELETED", "data": {"path": "/machine/peripheral/fs-pci1/virtio-backend"}} {"timestamp": {"seconds": 1629604708, "microseconds": 838764}, "event": "DEVICE_DELETED", "data": {"device": "fs-pci1", "path": "/machine/peripheral/fs-pci1"}} 4. repeat step 2. {"execute":"device_add","arguments":{"driver":"vhost-user-fs-pci","id":"fs-pci1","bus":"pcie_extra_root_port_0","tag":"myfs","queue-size":"1024","chardev":"char_virtiofs_fs"}} {"return": {}} 5. in windows guest, mount the shared directory. 1) make sure virtiofs driver is installed 2) install WINFSP in guest.(download winfsp installe: http://www.secfs.net/winfsp/rel/ ) 3) start viritofs.exe(it's in virtio-win iso) C:\> virtiofs.exe -d -1 -D - 6. repeat step 3 {"execute":"device_del","arguments":{"id":"fs-pci1"}} {"return": {}} Actual results: after step3, vhost-user-fs-device is deleted. after step4, vhost-user-fs-device is added. after step5, can get the shared dirctory in guest. after step6, hotunplug failed. Didn't get device is deleted info,such as. {"timestamp": {"seconds": 1629604708, "microseconds": 786991}, "event": "DEVICE_DELETED", "data": {"path": "/machine/peripheral/fs-pci1/virtio-backend"}} {"timestamp": {"seconds": 1629604708, "microseconds": 838764}, "event": "DEVICE_DELETED", "data": {"device": "fs-pci1", "path": "/machine/peripheral/fs-pci1"}} The device is still in guest. Expected results: Can hotunplug virtiofs device. Additional info: 1) rhel guest works well with the steps above. 2) cmd line: MALLOC_PERTURB_=1 /usr/libexec/qemu-kvm \ -name 'avocado-vt-vm1' \ -sandbox on \ -machine q35 \ -device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \ -device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0 \ -nodefaults \ -device VGA,bus=pcie.0,addr=0x2 \ -m 4096 \ -object memory-backend-file,size=4G,mem-path=/dev/shm,share=yes,id=mem-mem1 \ -smp 24,maxcpus=24,cores=12,threads=1,dies=1,sockets=2 \ -numa node,memdev=mem-mem1,nodeid=0 \ -cpu 'Skylake-Server',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,+kvm_pv_unhalt \ -device pvpanic,ioport=0x505,id=idwOGXyj \ -device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \ -device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie-root-port-2,addr=0x0 \ -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=$1,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \ -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \ -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \ -device virtio-net-pci,mac=9a:80:46:fc:c0:44,id=idIrkxeJ,netdev=idc5mMT9,bus=pcie-root-port-3,addr=0x0 \ -netdev tap,id=idc5mMT9 \ -blockdev node-name=file_cd1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/iso/windows/winutils.iso,cache.direct=on,cache.no-flush=off \ -blockdev node-name=drive_cd1,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_cd1 \ -device ide-cd,id=cd1,drive=drive_cd1,write-cache=on,bus=ide.0,unit=0 \ -cdrom /home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-203.iso \ -vnc :1 -qmp tcp:0:6666,server,nowait \ -rtc base=localtime,clock=host,driftfix=slew \ -boot menu=off,order=cdn,once=c,strict=off \ -enable-kvm -monitor stdio \ -device pcie-root-port,id=pcie_extra_root_port_0,multifunction=on,bus=pcie.0,addr=0x4,chassis=5 \ -chardev socket,id=char_virtiofs_fs,path=/tmp/socket1 \ 3) pc machine type also has this issue.