I am running SLES 10 servers in a XEN environment.

No matter what I set the time to using the 'date' command on one of the servers, it will always jump back to about 6 minutes ahead of time. I disabled NTP to make sure that wasn't scrweing anything up. Originally NTP was enabled and the clock was still 5 minutes ahead of time. Below is the output of a few commands that will show the problem...

99lv01-a:/etc/sysconfig # rcntp status
Checking for network time protocol daemon (NTPD): unused <-- NTP is off
99lv01-a:/etc/sysconfig # date <-- Time is 12:47:51
Fri Dec 7 12:47:51 CST 2007
99lv01-a:/etc/sysconfig # date 12071242 <--- Setting time to 12:42:00
Fri Dec 7 12:42:00 CST 2007
99lv01-a:/etc/sysconfig # date
Fri Dec 7 12:48:00 CST 2007 <--- It goes back to 12:48
99lv01-a:/etc/sysconfig # hwclock <--- No luck w/ the hwclock command
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
99lv01-a:/etc/sysconfig #

99lv01-b, 99lv01-c and 99lv01-d are all SLES VMs on 99lv01 but the clock works on those fine.

Any ideas?

Hi -

You might want to look at your NTP "drift"

EXAMPLE:
/var/lib/ntp/drift/ntp.drift

Just a thought .. pSM

I actually tried deleting that and starting over with no luck.

I found that if I put 'xen.independent_wallclock = 1' in /etc/sysctl.conf it won't take the time setting of the master host (99lv01). This worked even though the time on 99lv01 was set properly.

Very strange.