Red Hat Bugzilla – Bug 597983
Continually suspending guest to memory caused migration failed
Last modified: 2015-05-24 20:05:32 EDT
Description of problem:
I try to execute s3 in guest, and do migration at the same time. When migration completed, check the migration status by monitor command.
guest1-monitor) migrate tcp:0:4444
guest1 -monitor) info migrate
Migration status: failed
_Actually_, guest has been migrated to dest VM.
Version-Release number of selected component (if applicable):
host kernel: 2.6.32-25.el6.x86_64
# rpm -qa |grep qemu
Steps to Reproduce:
1. boot up src and dest VMs.
2. continually execute s3 in guest
# while true; do echo "mem" > /sys/power/state; done
3. try to do migration
guest1-qemu) migrate tcp:0:4444
guest1-qemu) info migrate
migration completed successfully
1. Command line:
guest1) qemu-kvm -name 'vm1' -drive file=/root/autotest/client/tests/kvm/images/RHEL-Server-5.5-64.qcow2,if=ide,cache=none,boot=on -net nic,vlan=0,model=e1000,macaddr=02:A9:7C:6C:3b:4d -net tap,vlan=0,ifname=e1000_1,downscript=no -m 512 -smp 1 -soundhw ac97 -vnc :0 -usbdevice tablet -rtc-td-hack -no-hpet -cpu qemu64,+sse2 -no-kvm-pit-reinjection -serial unix:/tmp/serial-20100528-180850-IsP5,server,nowait -snapshot
guest2) qemu-kvm -name 'vm2' -drive file=/root/autotest/client/tests/kvm/images/RHEL-Server-6.0-64.qcow2,if=ide,cache=none,boot=on -net nic,vlan=0,model=e1000,macaddr=02:A9:7C:6C:3b:4d -net tap,vlan=0,ifname=e1000_2,downscript=no -m 512 -smp 1 -soundhw ac97 -vnc :2 -usbdevice tablet -rtc-td-hack -no-hpet -cpu qemu64,+sse2 -no-kvm-pit-reinjection -serial unix:/tmp/serial-20100528-180850-IsP52,server,nowait -snapshot -incoming tcp:0:4444
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
Did s3 always work regardless of migration? What's the guest type?
s3 works well regardless of migration.
rhel55 guest, kernel: 2.6.18-201.el5.x86_64
Please retest on latest bits, I'm unable to reproduce on:
With guest in S3 loop, migration completes and 'info migrate' on the migration source reports the migration as completed successfully.
(In reply to comment #6)
> Please retest on latest bits, I'm unable to reproduce on:
> With guest in S3 loop, migration completes and 'info migrate' on the migration
> source reports the migration as completed successfully.
I also could not reproduce this bug.
. qemu-kvm-0.12.1.2-2.129.el6.x86_64 & 2.6.32-94.el6.x86_64 [success]
. qemu-kvm-0.12.1.2-2.129.el6.x86_64 & 2.6.32-99.el6.x86_64 [success]
This seems to be fixed in qemu-kvm-0.12.1.2-2.129.el6.x86_64, if not earlier.