Re: [Xen-devel] Xen 3.1.2 domU clock goes out of sync

[Tõnu Raitviir <jussuf@xxxxxxxx>]

On Tue, 20 Nov 2007, Keir Fraser wrote:

> Could it not be a drift? e.g., Perhaps you ran ntpdate in dom0 but not the
> domUs?
That's possible, probably ntpdate was executed automatically on dom0. Now 
I did a new test, rebooted dom0 and made sure that no ntp* commands are
run. Results are somewhat different:
# uptime
 14:21:41 up 12:31,  1 user,  load average: 0.00, 0.00, 0.00

dom0    offset -7.190458
domU #1 offset -4.380381
domU #2 offset -4.380430
domU #3 offset -4.380401

So without any ntp interaction dom0 clock is running faster than domU 
clock and all domU clocks are in sync with each other, but still not 
with dom0.
Now I'm going to start ntpd again and make sure that it never stops :-)

--
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