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.
DescriptionDaniel Berrangé
2010-04-23 12:12:45 UTC
Description of problem:
If you invoke an 'exec' based migration of a guest, the moment it starts, the entire guest stops responding to interaction over VNC. The guest remains dead after the migration has completed
Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.36.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Run
/usr/libexec/qemu-kvm -S -M pc-0.12 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name f14i686 -uuid 0874d900-61db-1dac-9396-59fc79090815 -nodefaults -chardev stdio,id=monitor -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/var/lib/libvirt/images/f14i686.img,if=none,id=drive-virtio-disk0,boot=on,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -k en-us -vga cirrus
2. Type 'cont' in monitor
3. Connect with VNC and interact with the guest
4. Type in monitor:
migrate "exec:cat >>/root/test.dump 2>/dev/null"
Actual results:
You can no longer interact with the guest OS in VNC. Further guest interactions such as querying memory balloon also hang.
Expected results:
Migration is live & guest is fully responsive at all times.
Additional info:
Tcp based migration does not appear to suffer this problem.
Comment 2RHEL Program Management
2010-04-23 14:07:21 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Further information:
- Running -no-kvm does not suffer the problem
- Running with kvm, but with -no-kvm-irqchip does not suffer the problem
Thus looks like a flaw in the kernel IRQ chip integration somehow impacting only exec based migration. Perhaps its a timing problem, since the exec based migration is much slower than tcp migration which doesn't show this hang
FYI, in my testing I was triggering the migration start while the guest was in the middle of initscripts bootup sequence, hence it almost certainly had quite high load, both CPU + disk I/O.
I am not able to reproduce it locally. I can do a migration in the middle of the boot sequence (once we enter X to have a mouse), and I can move the mouse as fast as I can, no problem here.
Later, Juan.
Wasn't able to reproduce it here on a 4GB guest:
/usr/libexec/qemu-kvm -m 4G -smp 2 -drive file=/var/lib/libvirt/images/f12.img,if=ide,cache=none,boot=on -net nic,model=virtio,vlan=1,macaddr=02:00:40:3F:20:10 -net tap,vlan=1,script=/etc/kvm-ifup.sh -boot c -uuid 17544ecc-d3a1-4d3c-a386-12daf50015f1 -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -balloon none -startdate now -name f12-source -vnc 127.0.0.1:0
qemu-kvm-0.12.1.2-2.78.el6.x86_64
kernel-2.6.32-37.el6.x86_64
Guest stayed responsive pretty much until the migration command completed.
cheers,
Jes