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-users] clocksource/0: Time went backwards

To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Subject: Re: [Xen-users] clocksource/0: Time went backwards
From: Bart Verwilst <lists@xxxxxxxxxxx>
Date: Thu, 11 Oct 2007 10:07:55 +0200 (CEST)
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 11 Oct 2007 01:08:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071010233644.GA15154@implementation>
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Does ntpd allow the time to go backwards?
However, i've found that the domU where i have been having most troubles with, 
doesn't run ntpd. ( I set independent_wallclock in every domU anyways ), 
I've just enabled ntpd, and going to see what happens!

Thanks Samuel!

Kind regards,


----- Original Message -----
From: "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxx>
To: "Shane D. Johnson" <SDJ@xxxxxxxxxxxxxxxxxxxxxx>
Cc: "Bart Verwilst" <lists@xxxxxxxxxxx>, Xen-users@xxxxxxxxxxxxxxxxxxx
Sent: Thursday, October 11, 2007 1:36:44 AM (GMT+0100) Europe/Berlin
Subject: Re: [Xen-users] clocksource/0: Time went backwards

Shane D. Johnson, le Wed 10 Oct 2007 17:05:39 -0600, a écrit :
>    I haven't had this happen but I  have seen a lot of references to 
> similar problems on the mailing list archive.  I would start there and 
> see if you can find your fix there.

I also had this issue with Mach as domU.
It looked to me like this is due to the NTP daemon running in dom0 that
makes the time backward so as to align to NTP servers.


Xen-users mailing list