[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen 3.1.2 domU clock goes out of sync
On Tue, 20 Nov 2007, Keir Fraser wrote: I wonder if dom0 has remembered some ntp-derived adjustment values despite ntpd no longer running. That would explain why it continues to keep good time while all others drift. Well... in the example in my first letter dom0 was booted without ntpd and after 2+ days its clock offset was only -0.438055 while domU had drifted far away. In that case there was no adjustment values to remember. So... running ntpd in dom0 is a good idea. :-) I don't question that. But I wonder, isn't domU clock supposed to be always in sync with dom0, with or without ntpd? Or how exactly does ntpd in dom0 affect domU clock? -- 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |