On 10/03/2010 10:16 AM, Michael Tokarev wrote:
I just booted this same guest using kvm-0.12.5 - using that one
guest does not report unstable tsc, yet does not list it in the
available_clocksources. It also shows time jumps:
...
[0;0/0: 0.000000] Detected 3217.424 MHz processor.
[0;0/0: 0.006666] Calibrating delay loop (skipped) preset value.. 6437.96
BogoMIPS (lpj=10724746)
[0;0/0: 0.006666] pid_max: default: 32768 minimum: 301
[0;0/0: 0.006666] Mount-cache hash table entries: 512
[0;0/0: 0.006765] Initializing cgroup subsys ns
...
[0;0/0: 0.029999] Booting Node 0, Processors #1 Ok.
[1;0/0: 0.006666] Initializing CPU#1
[1;0/0: 0.006666] kvm-clock: cpu 1, msr 0:1e0a0c1, secondary cpu clock
[0;0/0: 0.058342] Brought up 2 CPUs
...
Most likely it's still using jiffies while the clocks are being set up.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
