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:
Boot guest with virtio-blk data-plane, do "drive-mirror", guest cannot shutdown and qemu-kvm hang.
Version-Release number of selected component (if applicable):
kernel-3.10.0-302.el7.x86_64
qemu-kvm-rhev-2.3.0-15.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. boot a guest with virtio-blk data-plane
# /usr/libexec/qemu-kvm -name rhel7 -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -m 4096 -cpu SandyBridge -realtime mlock=on -sandbox off -smp 4,maxcpus=4,sockets=4,cores=1,threads=1 -object iothread,id=iothread0 -drive file=/home/rhel7.2.qcow2,if=none,id=data-disk1,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,drive=data-disk1,iothread=iothread0,bus=pci.0,addr=0x6,id=data-disk1 -drive file=/home/data-disk.qcow2,if=none,id=data-disk2,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,drive=data-disk2,iothread=iothread0,bus=pci.0,addr=0x7,id=data-disk2 -netdev tap,id=hostnet0,vhost=on,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=b6:72:66:f5:7d:93,bus=pci.0,addr=0x9 -device sga -spice port=5910,password=redhat-vga,disable-ticketing -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -qmp tcp:0:4466,server,nowait -serial unix:/tmp/ttym,server,nowait -monitor stdio
2. do drive-mirror
{"execute":"qmp_capabilities"}
{"return": {}}
{ "execute": "drive-mirror", "arguments": { "device": "data-disk2", "target": "/root/sn1", "format": "qcow2", "sync": "full"}}
{"return": {}}
3. inside guest, do shutdown
# shutdown -h now
Actual results:
after step2, "drive-mirror" can return without error info
after step3, guest cannot shutdown and qemu-kvm hang.
Expected results:
after step3, guest can shutdown and qemu-kvm can quit without error info.
Additional info:
On host, check the serial console:
# nc -U /tmp/ttym
Red Hat Enterprise Linux Server 7.2 Beta (Maipo)
Kernel 3.10.0-302.el7.x86_64 on an x86_64
dhcp-9-29 login: Powering off.
[ 90.737329] Power down.
Looks like a bdrv_set_aio_context() or bdrv_drain_all() issue. Deferring to RHEL 7.2 since the scenario to trigger it doesn't appear critical enough for an exception.
Description of problem: Boot guest with virtio-blk data-plane, do "drive-mirror", guest cannot shutdown and qemu-kvm hang. Version-Release number of selected component (if applicable): kernel-3.10.0-302.el7.x86_64 qemu-kvm-rhev-2.3.0-15.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot a guest with virtio-blk data-plane # /usr/libexec/qemu-kvm -name rhel7 -S -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off -m 4096 -cpu SandyBridge -realtime mlock=on -sandbox off -smp 4,maxcpus=4,sockets=4,cores=1,threads=1 -object iothread,id=iothread0 -drive file=/home/rhel7.2.qcow2,if=none,id=data-disk1,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,drive=data-disk1,iothread=iothread0,bus=pci.0,addr=0x6,id=data-disk1 -drive file=/home/data-disk.qcow2,if=none,id=data-disk2,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,drive=data-disk2,iothread=iothread0,bus=pci.0,addr=0x7,id=data-disk2 -netdev tap,id=hostnet0,vhost=on,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=b6:72:66:f5:7d:93,bus=pci.0,addr=0x9 -device sga -spice port=5910,password=redhat-vga,disable-ticketing -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -qmp tcp:0:4466,server,nowait -serial unix:/tmp/ttym,server,nowait -monitor stdio 2. do drive-mirror {"execute":"qmp_capabilities"} {"return": {}} { "execute": "drive-mirror", "arguments": { "device": "data-disk2", "target": "/root/sn1", "format": "qcow2", "sync": "full"}} {"return": {}} 3. inside guest, do shutdown # shutdown -h now Actual results: after step2, "drive-mirror" can return without error info after step3, guest cannot shutdown and qemu-kvm hang. Expected results: after step3, guest can shutdown and qemu-kvm can quit without error info. Additional info: On host, check the serial console: # nc -U /tmp/ttym Red Hat Enterprise Linux Server 7.2 Beta (Maipo) Kernel 3.10.0-302.el7.x86_64 on an x86_64 dhcp-9-29 login: Powering off. [ 90.737329] Power down.