Hello!
I have understood that when /proc/sys/xen/independent_wallclock is 0, then
domU clock stays in sync with dom0 clock. Now I have a case with Xen 3.1.2
(also occured with 3.1.1, but I haven't documented it) where domU clock
runs significantly faster - after 65 hours domU clock is 20 seconds ahead
of dom0 clock.
In this case dom0 is not running ntpd. When ntpd is running on dom0, domU
clock also stays correct. Is this normal behaviour?
Some examples to show clock differences:
domU# uptime
14:54:09 up 2 days, 17:05, 1 user, load average: 0.75, 0.49, 0.43
domU# ntpdate -q ntp.eenet.ee
server 193.40.133.142, stratum 1, offset -20.856732, delay 0.02579
19 Nov 14:54:13 ntpdate[8467]: step time server 193.40.133.142 offset
-20.856732 sec
dom0# uptime
14:55:02 up 2 days, 17:06, 1 user, load average: 0.07, 0.02, 0.00
dom0# ntpdate -q ntp.eenet.ee
server 193.40.133.142, stratum 1, offset -0.438055, delay 0.02589
19 Nov 14:55:17 ntpdate[32284]: adjust time server 193.40.133.142 offset
-0.438055 sec
Xen version used:
Xen version 3.1.2 (jussuf@localdomain) (gcc version 4.1.2 20061115 (prerelease)
(Debian 4.1.1-21)) Fri Nov 16 17:52:59 EET 2007
Latest ChangeSet: Wed Nov 14 23:35:43 2007 +0000 15502:c6776b6da8ee
Linux xen-2 2.6.18.8-xen0 #1 SMP Fri Nov 16 17:39:31 EET 2007 x86_64 GNU/Linux
--
Tõnu Raitviir tonu.raitviir@xxxxxxxx
EENet http://www.eenet.ee/
BalticGrid Project http://www.balticgrid.org/ _______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home