17.04.2010 23:52, Espen Berg wrote:
Den 15.04.2010 09:35, skrev Espen Berg:
We have three KVM hosts that supports live-migration between them, but
one of our problems is time drifting. The three frontends has different
CPU frequency and the KVM guests adopt the frequency from the host
machine where it was first started.
What do you mean by "adopts" ? Note that the cpu frequency
means nothing for all the modern operating systems, at least
since the days of common usage of MS-DOS which relied on CPU
frequency for its time functions. All interesting things are
now done using timers instead, and timers (which don't depend
on CPU frequency again) usually work quite well.
What complicates things is that the most cheap and accurate
enough time source is TSC (time stamp counter register in
the CPU), but it will definitely be different on each
machine. For that, 0.12.3 kvm and 2.6.32 kernel (I think)
introduced a compensation. See for example -tdf kvm option.
[]
Is there any solution to our problems, or is a reboot the only safe
solution?
Well, reboot is definitely a safe solution.
Is there no one with similar problems here? :\ Guess I should file a bug
report or something if the same problems occur in the latest version. I
can't se any changes in change log after 0.11.x that relate to this
problem. We can't be the only one that uses different CPUs in a
migration environment.
Actually there is a difference in 0.12.
Since this is a cluster in production, I'm not able to try the latest
version either.
Well, that's difficult one, no? It either works or not.
If you can't try anything else, why to ask? :)
/mjt
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
