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.
Description of problem:
Try to remove a virtio disk device that is in use via monitor or qmp, it will fail. rhel6 and windows2k8r2 guest have the same issue.
This is a regression issue. reason:
1.for qemu-kvm-rhev-0.12.1.2-2.334
cannot be removed
2.for qemu-kvm-rhev-0.12.1.2-2.209
can be removed
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-0.12.1.2-2.334.el6.x86_64
# uname -r
2.6.32-340.el6.x86_64
guest:
rhel6 and windows2k8
How reproducible:
100%
Steps to Reproduce:
1./usr/libexec/qemu-kvm -enable-kvm -m 2G -smp 4 -name rhel6 -uuid ddcbfb49-3411-1701-3c36-6bdbc00bedb9 -rtc base=utc,clock=host,driftfix=slew -boot c -drive file=/home/rhel6.4.qcow2,if=none,id=drive-virtio-0-1,format=qcow2,cache=none,werror=report,rerror=report -device virtio-blk-pci,drive=drive-virtio-0-1,id=virt0-0-1 -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:50:a4:c2:c5 -vnc :1 -device virtio-balloon-pci,id=ballooning -monitor stdio -qmp tcp:0:4455,server,nowait -serial unix:/home/error-message,server,nowait -drive file=/root/live-block-copy/5g.qcow2,format=qcow2,if=none,id=drive-disk,cache=none,werror=ignore,rerror=ignore -device virtio-blk-pci,scsi=off,drive=drive-disk,id=image
2.copy a big file to second disk
3.device_del image
4.info block via monitor
info block
drive-virtio-0-1: removable=0 file=/home/rhel6.4.qcow2 ro=0 drv=qcow2 encrypted=0
drive-disk: removable=0 file=/root/live-block-copy/5g.qcow2 ro=0 drv=qcow2 encrypted=0
ide1-cd0: removable=1 locked=0 tray-open=0 io-status=ok [not inserted]
floppy0: removable=1 locked=0 tray-open=0 [not inserted]
sd0: removable=1 locked=0 tray-open=0 [not inserted]
5.info pci via monitor
Bus 0, device 6, function 0:
SCSI controller: PCI device 1af4:1001
IRQ 10.
BAR0: I/O at 0xc0c0 [0xc0ff].
BAR1: 32 bit memory at 0xf2040000 [0xf2040fff].
id "image"
Actual results:
Expected results:
should be deleted
Additional info:
Tested three scenarios. and scenario 1 can verify this bug 734051.
1. qemu-kvm-0.12.1.2-2.209
guest kernel-2.6.32-296.el6
result:
secondary disk can be removed successfully via device_del
2. qemu-kvm-rhev-0.12.1.2-2.334.el6.x86_64.rpm
guest kernel-2.6.32-296.el6
result:
secondary disk cann't be removed via device_del(check guest and info pci/block)
3. qemu-kvm-rhev-0.12.1.2-2.334.el6.x86_64.rpm
guest kernel-2.6.32-340.el6.x86_64
result:
secondary disk cann't be removed via device_del(check guest and info pci/block)
So, kernel-296 and qemu-kvm-209 support remove device after bug 734051 is fixed. For this bug, whatever kernel 296 or 340. The latest qemu-kvm don't support remove device.
Another scenario, Tested this issue with qemu-kvm-0.12.1.2-2.334.el6.x86_64 and kernel 2.6.32-342.el6.x86_64
Result:
device_del still cann't remove device is in use, but guest will show call trace and automatic restart after a few minutes. Meantime device will be automatically removed after guest reboot as well. I attached call trace message.
summary testing result with fix v2
1. guest don't appear panic
2. device will be removed automatically after i/o operation is done(execute device_del image that is in use).
3. guest work well
Asias has a working fix, but,
As this is not a regression
And it was not sent upstream yet
And we are late in 6.4
I prefer not to take a risk and defer to 6.5.
Asias will add a tech note explaining how to avoid it.
Description of problem: Try to remove a virtio disk device that is in use via monitor or qmp, it will fail. rhel6 and windows2k8r2 guest have the same issue. This is a regression issue. reason: 1.for qemu-kvm-rhev-0.12.1.2-2.334 cannot be removed 2.for qemu-kvm-rhev-0.12.1.2-2.209 can be removed Version-Release number of selected component (if applicable): qemu-kvm-rhev-0.12.1.2-2.334.el6.x86_64 # uname -r 2.6.32-340.el6.x86_64 guest: rhel6 and windows2k8 How reproducible: 100% Steps to Reproduce: 1./usr/libexec/qemu-kvm -enable-kvm -m 2G -smp 4 -name rhel6 -uuid ddcbfb49-3411-1701-3c36-6bdbc00bedb9 -rtc base=utc,clock=host,driftfix=slew -boot c -drive file=/home/rhel6.4.qcow2,if=none,id=drive-virtio-0-1,format=qcow2,cache=none,werror=report,rerror=report -device virtio-blk-pci,drive=drive-virtio-0-1,id=virt0-0-1 -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:50:a4:c2:c5 -vnc :1 -device virtio-balloon-pci,id=ballooning -monitor stdio -qmp tcp:0:4455,server,nowait -serial unix:/home/error-message,server,nowait -drive file=/root/live-block-copy/5g.qcow2,format=qcow2,if=none,id=drive-disk,cache=none,werror=ignore,rerror=ignore -device virtio-blk-pci,scsi=off,drive=drive-disk,id=image 2.copy a big file to second disk 3.device_del image 4.info block via monitor info block drive-virtio-0-1: removable=0 file=/home/rhel6.4.qcow2 ro=0 drv=qcow2 encrypted=0 drive-disk: removable=0 file=/root/live-block-copy/5g.qcow2 ro=0 drv=qcow2 encrypted=0 ide1-cd0: removable=1 locked=0 tray-open=0 io-status=ok [not inserted] floppy0: removable=1 locked=0 tray-open=0 [not inserted] sd0: removable=1 locked=0 tray-open=0 [not inserted] 5.info pci via monitor Bus 0, device 6, function 0: SCSI controller: PCI device 1af4:1001 IRQ 10. BAR0: I/O at 0xc0c0 [0xc0ff]. BAR1: 32 bit memory at 0xf2040000 [0xf2040fff]. id "image" Actual results: Expected results: should be deleted Additional info: