On Mon, Feb 28, 2011 at 10:17:24AM -0500, Zachary Amsden wrote:
On 02/28/2011 09:32 AM, Nikola Ciprich wrote:
Does the bug you are hitting manifest on both Intel and AMD platforms?
I don't have any AMD box here, I'll try this out at my home box.
Further, do the systems you are hitting this on have stable or unstable
TSCs?
how do I find this out? I don't see any warning about TSC in guest, but I've
just started it..
n.
Before worrying about the guest, is the host TSC stable? What is the
host clocksource?
not sure, I'm not setting anything specifically, is this snippet of dmesg relevant:
[ 1.148829] HPET: 8 timers in total, 5 timers will be used for per-cpu timer
[ 1.148934] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 40, 41, 42, 43, 44, 0
[ 1.149331] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 1.151831] hpet: hpet2 irq 40 for MSI
[ 1.151962] hpet: hpet3 irq 41 for MSI
[ 1.155930] hpet: hpet4 irq 42 for MSI
[ 1.159937] hpet: hpet5 irq 43 for MSI
[ 1.163943] hpet: hpet6 irq 44 for MSI
[ 1.175955] Switching to clocksource tsc
so I guess I'm using hpet?
n.
Looks like you are using tsc based on the last line. Can you tell us
please
cat /proc/cpuinfo
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
and grep -i dmesg for these keywords: TSC, clock, hpet, stable, khz, kvm
--
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
