Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-users

Re: [Xen-users] Problem with timekeeping

To: xen list <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Problem with timekeeping
From: "Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 27 Feb 2007 08:22:52 +0100
Delivery-date: Mon, 26 Feb 2007 23:22:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070226152126.c85eaccc.fbusse@xxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Universitaet Regensburg, Klinikum
Priority: normal
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 26 Feb 2007 at 15:21, Fridtjof Busse wrote:

> Hi,
> 
> I'm running Xen 3.0.4 on an AMD64 server and noticed a weird problem:
> The time in the guest is 2 minutes ahead of the host's time. The dom0 is
> synchronized via NTP and the domU has independent_wallclock=0.
> Any idea what might cause this?
> Or is the only way to fix this to use independent_wallclock=1 and use
> NTP in the guest as well?

Using independent clocks and NTP everywhere fixes the problem, but basically 
running NTP in Dom0 only and slaved clocks SHOULD work (but it doesn't). At 
least 
with SLES10 x86_64 and a 4 CPU Opeteron.

Ulrich


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

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