We have a few vms with Windows 2003 and Microsoft SQL 2005 sp3 and sp4.
We are using Ubuntu 8.04 as the host (2.6.24-23).
Time keeping in the vms is not right, the clock is fast, then slow, then it pauses, then its fast, its all over the place.
In the Linux side hwclock fails only if SQL is running.
When SQL is not running hwclock says:
hwclock from util-linux-ng 2.13.1
Using /dev interface to clock.
Last drift adjustment done at 1295541014 seconds after 1969
Last calibration done at 1295541014 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2011/01/20 22:12:11
Hw clock time : 2011/01/20 22:12:11 = 1295561531 seconds since 1969
Thu 20 Jan 2011 04:12:11 PM CST -0.866003 seconds
But when SQL is running it says:
hwclock from util-linux-ng 2.13.1
hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
I also get messages in dmesg like:
[33364.463975] /dev/vmmon[7233]: host clock rate change request 83 -> 1043
[33380.252939] rtc: lost 24 interrupts
I am pretty sure my hardware has hpet enabled, acpi enabled. I have tried changing the /proc/sys/dev/hpet/max-user-freq and a few other sysctl settings, none have helped. We've also tried two virtual cpus, as well as /usemptimer in Windows.
Has anyone else seen this problem?
Thank you,
--Carlos