On 10/02/2011 02:45 AM, Robin Lee Powell wrote:
I'm afraid clocksource=hpet didn't help much; after about 24 hours up, tcpdump hung the machine for for about 10 seconds. That may or may not be better than usual; I haven't been timing things precisely. My suspicion is that it's slightly better, but it's still not great. Also: rlpowell@vrici> dmesg | grep -i clock [ 0.000000] Command line: ro root=/dev/vda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=ttyS0,115200 clocksource=hpet [ 0.000000] kvm-clock: Using msrs 12 and 11 [ 0.000000] kvm-clock: cpu 0, msr 0:1b567c1, boot clock [ 0.000000] kvm-clock: cpu 0, msr 0:5fc137c1, primary cpu clock [ 0.000000] Kernel command line: ro root=/dev/vda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=ttyS0,115200 clocksource=hpet [ 0.000000] hpet clockevent registered [ 0.260136] Switching to clocksource hpet [ 1.009393] rtc_cmos 00:01: setting system clock to 2011-10-01 07:49:50 UTC (1317455390) [ 1.821905] Refined TSC clocksource calibration: 2394.030 MHz. [60555.473797] Clocksource tsc unstable (delta = -42950328292 ns) (note the last line)
Do you get a similar error with kvmclock? -- error compiling committee.c: too many arguments to function -- 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
