This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] 2.6.27 domU clock drift

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] 2.6.27 domU clock drift
From: Brad Plant <bplant@xxxxxxxxxxxx>
Date: Fri, 5 Dec 2008 16:51:07 +1100
Delivery-date: Thu, 04 Dec 2008 21:51:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I recently upgraded from xen 3.2 running a 2.6.18 domU to xen 3.3 running a 
2.6.27 pvops domU. Dom0, domU and hypervisor is 64-bit.

In the old configuration, the time on the domU's were in sync with the dom0. 
This made keeping the correct time easy by running a single instance of ntp on 
the dom0 and all the domU's would follow. In the new configuration though, the 
domU's seem to have their own time which drifts relative to the dom0 and the 
other domU's. The behaviour in the 2.6.18 kernel could be changed via 
/proc/sys/xen/independent_wallclock, but the 2.6.27 kernel seems to have no 
such option. Is there a kernel option (maybe for an RTC driver?) that I need to 
compile in to restore the old behaviour or do I now need to run ntp in every 



Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>