[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] NTP time issues DomU's

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Tim Durack <tdurack@xxxxxxxxx>
  • Date: Fri, 13 May 2005 10:26:23 -0400
  • Delivery-date: Fri, 13 May 2005 15:18:57 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ri3Ylj5kPL4dx1K6v3LBgFcsC+tUK27197d0CWHh+ZwUh6UZVW9sZPNiS3ps2gmbf7G4XisaH2Qf6H+dNHq2lUmY1QAr3PKDQMuktC0z2byWK76aWNA5tY7PygTCCmsp0zOLA7GplpKOL7LG8+ierPq3OcQ/Y8lMiP6hfSho9TQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I think it's perfect the way it is.

Run NTP in dom0, all the domU's then have synchronized time.

I can still set timezones on all of these boxes independantly.
Timezone has nothing to do with NTP synchronization.


> yeah, i'm already doing that, I was just saying, it *seemed* 
> like they were getting their time from domain0, and weren't 
> actually changing their own clocks in accordance with syncing 
> with the same ntpd server.
> especially since they're all off by exactly the same amount 
> ... and running ntpdate doesn't seem to have any effect whatsoever?

If you don't run ntp in the domU's, it should just work.

If you want to run ntp in the domU, try:
 echo 1 > /proc/sys/xen/independent_wallclock

I guess we could be smarter about this, and make the wall clock
independent automatically if someone does an adjtimex syscall. Anyone
got any comments on this?


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.