| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] time synchronization problem (using NTP)
On 11 Oct 2006 at 19:02, Christoph Purrucker wrote:
> Hi Thomas,
>
> > As far as my experience shows, none of the ntp / independent_wallclock
> > combinations work. We got the same problem here with xen 3.0.2 and
> > kernel 2.6.16. It looks like ntpd can't set the time in DomUs with
> > independent_wallclock set to 1 but the DomUs aren't using the exact time
> > of Dom0 with independent_wallclock set to 0.
>
> I'm running 2.6.16-2-xen-k7 with XEN 3.0 on both Dom0 and DomUs. A cron
> job on Dom0 runs "ntpdate ptbtime1.ptb.de" every night (shifting the
> time some milliseconds). All DomUs are perfectly in sync.
> /proc/sys/xen/independent_wallclock = 0 in all DomUs.
>
A plain "ntpd" also does the job once XEN's own synchronization (wich must be
buggy) is disabled (sysctl -w xen.independent_wallclock=1):
(2 DomUs):
rksapas01:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*rkdvmso1.dvm.kl 192.168.0.11 5 u 60 128 377 0.081 0.004 0.431
rksapas01:~ # ntpq -p rkdvmsod
remote refid st t when poll reach delay offset jitter
==============================================================================
*rkdvmso1.dvm.kl 192.168.0.11 5 u 233 256 377 0.088 0.038 0.010
+rkdvmas01.dvm.k 192.168.0.61 6 u 10 256 377 0.117 0.033 0.248
(Dom0):
rksapas01:~ # ntpq -p rkdvmso1
remote refid st t when poll reach delay offset jitter
==============================================================================
+pctick1a.dvm.kl 132.199.176.153 4 u 731 1024 377 0.164 -0.840 0.772
*rkdvmhp2.dvm.kl 192.168.0.16 4 u 712 1024 377 0.338 1.489 0.034
(All offsets are milliseconds, Configuration not complete yet)
Regards,
Ulrich
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home