Re: [Xen-users] domU time out of sync, ntpdate won't update it

[Iustin Pop <iusty@xxxxxxxxx>]

On Tue, Dec 08, 2009 at 01:43:16PM -0500, Madison Kelly wrote:
> Tait Clarridge wrote:
> >On Tue, 2009-12-08 at 13:03 -0500, Madison Kelly wrote:
> >>Hi all,
> >>
> >>   For some reason probably obvious that I am missing, my domU's
> >>aren't updating their time properly. On dom0 I can run 'ntpdate
> >>tick.redhat.com' and it properly changes the clock:
> >>
> >>root@vsh02:~# ntpdate tick.redhat.com
> >>  8 Dec 12:59:44 ntpdate[27362]: step time server 66.187.233.4
> >>offset -186.959214 sec
> >>root@vsh02:~# ntpdate tick.redhat.com
> >>  8 Dec 12:59:51 ntpdate[27365]: adjust time server 66.187.233.4
> >>offset 0.000176 sec
> >>
> >>   When I run the same on a given domU though, it *looks* like
> >>it's updating, but doesn't actually:
> >>
> >>root@sql01:~# ntpdate tick.redhat.com
> >>  8 Dec 13:10:08 ntpdate[1148]: step time server 66.187.233.4
> >>offset -655.452750 sec
> >>root@sql01:~# ntpdate tick.redhat.com
> >>  8 Dec 13:10:43 ntpdate[1373]: step time server 66.187.233.4
> >>offset -655.457543 sec
> >>
> >>   Notice that it doesn't seem to relate to dom0's skew.
> >>
> >>   Any tips?
> >>
> >>Thanks!!
> >>
> >>Madi
> >
> >I ran into this problem as well. Once I updated dom0 and
> >shutdown/started the domU it worked again.
> 
> Hrm, I need a way to keep the domUs update without a reboot... Did
> you come across any clues as to what/where the problem was?

Are you using xen.independent_wallclock = 1 here?

regards,
iustin

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users