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] Clock jumped 50 minutes in dom0 caused incorrect 2008R2

To: "Mark Adams" <mark@xxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Clock jumped 50 minutes in dom0 caused incorrect 2008R2 domU time
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Wed, 6 Oct 2010 23:20:37 +1100
Delivery-date: Wed, 06 Oct 2010 05:22:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101006111618.GA31233@xxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101006111618.GA31233@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActlSH2C3xIQI9VdQRWiBEXSo0oBhwACEkjQ
Thread-topic: [Xen-devel] Clock jumped 50 minutes in dom0 caused incorrect 2008R2 domU time
> Hi Xen-Devel's
> Please see my note below regarding a serious issue where my clock
> in dom0. I'm sending this through to the devel list as I haven't
> to glean any clear help from xen-users and the debian bug team are
> unsure what could have caused this.
> Can you confirm if the kernel or xen controls the clock in dom0? I
> understand that this could be an underlying hardware issue but I have
> another system on exactly the same hardware which hasn't had this
> Any advice on how to investigate further or ensure better clock
> stability across dom0 and domU would be appreciated.
> Also is it correct behaviour for Xen to reboot an 2008 R2 HVM domU if
> the time moves this much? My guess is that the domU crashed when the
> time changed, and was thus rebooted automatically. Strangely the
> 2003 server didn't get rebooted.
> If you need any more info to help please let me know.

Does DomU have more than one CPU? And if so, is viridian=1 specified in
the config? That relates to the crash, not the time jump though.


Xen-devel mailing list