Bugs item #2948108, was opened at 2010-02-08 14:06 Message generated for change (Comment added) made by ramereth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2948108&group_id=180599
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Lance Albertson (ramereth) Assigned to: Nobody/Anonymous (nobody) Summary: qemu-kvm fails to migrate properly in 0.12.2 Initial Comment: I'm using Ganeti and encountered a problem [1] with migrating KVM virtual machines. I have confirmed that this is not a problem specific to Ganeti and is also happening to the Libvirt project [2]. When migrating from host A to host B, everything goes fine however the guest VM (running CentOS 5.4) clock changes to approximately 600 seconds in the future. When attempting to migrate back to host B, the VM locks up and stops responding. However, if you fix the clock prior to syncing back to host A, the migration happens however the clock on the VM literally stops so the guest is pretty unusable. I tried the same scenario using Ubuntu 9.10 for the guest OS and has different issues. Upon migrating to host B, the clock on the guest VM was ahead by over 3 days into the future. Then when I migrate it back to host A the VM locks up hard. I can confirm I have no problem using migration when using 0.11.1. Here's the detail information about our setup: Hardware: Intel(R) Xeon(R) CPU 5160 @ 3.00GHz qemu-kvm: 0.12.2 kernel: 2.6.29-hardened Linux OS: Gentoo Hardened If you need more information, please let me know and I'll be happy to provide it. Thanks- [1] http://groups.google.com/group/ganeti/browse_thread/thread/9b2c556557e749cf [2] http://thread.gmane.org/gmane.comp.emulators.libvirt/20771 ---------------------------------------------------------------------- >Comment By: Lance Albertson (ramereth) Date: 2010-02-08 16:13 Message: It seems to work if I use something like acpi_pm for the clock source (on Debian). The clock also seemed to stay in time. I haven't tested it on the other OS's but it seems that CentOS doesn't even use kvmclock (which means sense considering the age of the kernel). ---------------------------------------------------------------------- Comment By: Brian Jackson (iggy_cav) Date: 2010-02-08 15:54 Message: guest you can either use the no-kvmclock boot param or choose a different clock in: /sys/devices/system/clocksource/clocksource0/current_clocksource possible values are in: /sys/devices/system/clocksource/clocksource0/available_clocksource ---------------------------------------------------------------------- Comment By: Lance Albertson (ramereth) Date: 2010-02-08 15:27 Message: Are you wanting me to try this on the guest or host system? ---------------------------------------------------------------------- Comment By: Brian Jackson (iggy_cav) Date: 2010-02-08 15:09 Message: This has been mentioned a few times in irc and possibly on the mailing list. No one has really come up with a fix. Can you try without kvmclock? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2948108&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
