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.
Created attachment 603412 [details] detail call trace Description of problem: Hot add a virtio storage to guest. run dd to the added storage in guest. And at the meantime device_del the storage which will cause guest reboot. after guest re-boot up , the virtio storage is still existing in the guest. Version-Release number of selected component (if applicable): 2.6.32-294.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.boot a guest 2. hotplug a disk 1). {"execute":"qmp_capabilities"} 2). {"execute":"__com.redhat_drive_add","arguments":{"file":"/home/storage.raw","format":"raw","id":"test30"}} 3). {"execute":"device_add","arguments":{"driver":"virtio-blk-pci","drive":"test30","id":"test30"}} 3. run dd in guest #dd if=/dev/zero of=/dev/vdb bs=1M count=2048 4. hot-unplug the disk {"execute":"device_del","arguments":{"id":"test30"}} (do this command while step 3 is running) Actual results: guest reboot the guest reboot. Expected results: Additional info: 1. cmd /usr/libexec/qemu-kvm -monitor stdio -chardev socket,id=serial_jpan,path=/tmp/serial-debug,server,nowait -device isa-serial,chardev=serial_jpan -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 -drive file=/home/rhel6.3.img,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=raw,aio=threads -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,netdev=idDh5tTU,mac=9a:67:8e:6f:af:02,id=ndev00idDh5tTU,bus=pci.0,addr=0x3 -netdev tap,id=idDh5tTU,vhost=on,script=/etc/qemu-ifup -m 2048 -smp 2,cores=1,threads=1,sockets=2 -cpu 'Penryn' -rtc base=utc,clock=host,driftfix=slew -M rhel6.3.0 -boot order=cdn,once=d,menu=off -no-kvm-pit-reinjection -enable-kvm -spice port=5936,disable-ticketing -vga qxl -qmp tcp:0:4444,server,nowait 2. host: qemu-kvm-0.12.1.2-2.302.el6.x86_64 processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Quad CPU Q9500 @ 2.83GHz stepping : 10 cpu MHz : 2000.000 cache size : 3072 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts tpr_shadow vnmi flexpriority 3. guest info 2.6.32-294.el6.x86_64 4. call trace: attached