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


Re: [Xen-devel] Dom0 <> DomU clock sync

To: Sébastien RICCIO <sr@xxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Dom0 <> DomU clock sync
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 03 Sep 2007 14:47:07 +0100
Delivery-date: Mon, 03 Sep 2007 06:47:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46DBBBAD.6070001@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfuMOrjKXsXYFokEdyxegAX8io7RQ==
Thread-topic: [Xen-devel] Dom0 <> DomU clock sync
User-agent: Microsoft-Entourage/
You're not running ntpd in the domU as well, right? Just worth checking...
Apart from that I don't think you can be doing anything wrong. Any weirdness
after long uptime is of course interesting, as it's something that's hard
for developers to test.

If you create a new domU (doesn't need to be from scratch installation -
e.g., just restarting a domU, or starting an existing dormant domU, would
do) then is its time behind dom0, or in sync?

 -- Keir

On 3/9/07 08:45, "Sébastien RICCIO" <sr@xxxxxxxxxxxxxxx> wrote:

> Hello !
> Just a quick question about time synchronization between xen dom0 and
> domUs...
> We're running Xen 3.1 64-bit, with 32 and 64 bits linux guests.
> It's up since 89 days and the domU's time is around 5 minutes behind the
> dom0,
> which is updated via ntpdate...
> Any idea why it doesn't sync the guests even that
> /proc/sys/xen/independent_wallclock is 0 ?
> Could it be an option that I missed in dom0/domU kernel ?
> Thanks for your help !

Xen-devel mailing list

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