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: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Clock jumped 50 minutes in dom0 caused incorrect 2008R2 domU time
From: Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Date: Wed, 6 Oct 2010 14:04:24 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 06 Oct 2010 06:05:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01A93264@trantor>
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> <AEC6C66638C05B468B556EA548C1A77D01A93264@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
Hi James,

It hasn't been clock change time here in the UK yet. I know what you
mean though, I have also had issues in the past around this time.
In this instance though it only changed 50 minutes?

I don't have viridian=1 set in the hosts, I do have localhost=1 to keep
the time the same as the dom0. The 2008 R2 domU seem to be operating fine
without this setting until this clock issue, what does the viridian
setting achieve?


On Wed, Oct 06, 2010 at 11:24:27PM +1100, James Harper wrote:
> > > > Oct  2 18:50:33 havhost1 kernel: [623480.977748] Clocksource tsc
> unstable
> > (delta = -2999660303788 ns)
> This is a longshot, but it's daylight savings time of year. We just
> moved from +10 to +11 hours at around 2am on Oct 3. I'm sure it's just a
> coincidence as I can't see how changing a timezone offset could cause
> such a problem but I've seen a few strange things this week with clocks
> getting out of whack.
> James

Xen-devel mailing list