I am getting a frozen guest when migrating from an Opteron 6274
an Opteron 6174 host (amd fam10h). The live migration completes
the guest is frozen: vcn screen is still there, but no input is
no kernel output is seen. Trying "c" on the qemu-monitor does not
I am using "-cpu Opteron_G3" which I assumed would be ok for both
In the opposite direction (migrating from an amd fam10h host to an
host) the guest continues to run on the destination. However, on
successfull live migrations, I notice a "clocksource unstable"
message on the
guest kernel (using the default kvm-clock clocksource) e.g.
Clocksource tsc unstable (delta = -1500533439 ns)
Same situation (guest runs on destination with clocksource unstable
happens when migrating between fam15h hosts (I have not tried
Changing the clocksource (tsc, acpi_pm, hpet) does not solve the
Also tried with "-cpu kvm64" with same result.
qemu-kvm version: 0.15.1, 1.0 or qemu-kvm/master
Host kernel: 3.0.15 (on both hosts)
Guest kernel: 3.0.6 or 3.2
this is the qemu-kvm command line used on the source host:
kvm -enable-kvm -m 1024 -smp 1 -cpu Opteron_G3,check -drive \
-monitor stdio -vnc 0.0.0.0:6 -vga std -chardev pty,id=charserial0
isa-serial,chardev=charserial0,id=serial0 -usb -device
The destination host has the same command line with an added
tcp:4444". I have mainly tested this with non-shared storage (but
storage has the same result). Migration is triggered with "migrate
Do the TSC microarchitecture changes in amdfam15h (see AMD SW
guide for fam15h, 47414 Rev 3.02 Appendix E) affect pvclock
migration in same family or across families?
cpuid information follows in case it's helpful.