Re: Dom0 <> DomU clock sync

["Sébastien RICCIO" <sr@swisscenter.com>]

Hi again,

I just tried to use ntpd in dom0. So far nothing changed.
The guests are still a couple of minutes behind the dom0.

Dom0 and DomU's are set to independent_wallclock 0.

Kernels are compiled from the sources included in Xen 3.1.

I don't know where to head next :))

Thanks for your help.

-- 
Sébastien Riccio
SwissCenter / OpenBusiness SA
sr@openbusiness.com



Keir Fraser a écrit :
> On 3/9/07 15:07, "Sébastien RICCIO" <sr@swisscenter.com> wrote:
>
>   
>> Ntpd is not running in dom0. I am updating the dom0 time with ntpdate
>> (crontab every hour).
>> Should ntpd be running on dom0 ?
>>     
>
> So long as ntpdate calls settimeofday(), this should be sufficient to update
> Xen's notion of time too. It seems that isn't happening for some reason.
>
> Do all guests (including dom0) have independent_wallclock equal to 0?
>
> What kernel are you using in dom0 (e.g., vendor kernel?).
>
> Ntpd in dom0 would be an interesting thing to try. That should cause dom0 to
> periodically (every few minutes) push its time down to Xen to be picked up
> by all domUs. But really ntpdate should be doing the right thing...
>
> In our kernels it should be *impossible* for dom0 and domU time to diverge
> when independent_wallclock is set to zero everywhere...
>
>  -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>