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

Re: [Xen-users] xen time sync problem


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Nadeem Shahbaz" <thrall.mail.list@xxxxxxxxx>
  • Date: Fri, 23 Feb 2007 21:18:00 +0500
  • Delivery-date: Fri, 23 Feb 2007 08:17:22 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Cr/yn18wAm9xkAZWWk87qH7UHiVWAMZoHVXWjrwsmRZj0NY7Al8YdtsIury5T1ozSgJ7XS957yFDd+WrKD0YyeouZedaoDxsPBI4Yw2gtqYrX6WaEesM6hcEG2biFpOgWL0VFPm//ypcLXmVVxeeRav22BZaTitrR5QODLUkgsw=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Okay, this problem is solved. I didn't know that
/proc/sys/xen/independent_wallclock does exist in DomU and it did
effect time sync with Dom0. As /proc/sys/xen/independent_wallclock was
forced set to 1 in DomU and 0 in Dom0 somehow. Now setting this to 0
solved the problem and now DomU are in sync with Dom0. And I really
appreciate for helping and thanks :-)

And sorry Ulrich, I only replied you unintentionally :-)

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


 


Rackspace

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