WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Clock jumped 50 minutes in dom0 caused incorrect 2008 R2

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] Clock jumped 50 minutes in dom0 caused incorrect 2008 R2 domU time
From: Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Date: Tue, 4 Jan 2011 17:00:27 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 04 Jan 2011 09:04:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3b1cf8d3-0aec-4976-8368-74eb46229b95@default>
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> <4CAC98BF.9010902@xxxxxxxx> <5e238400-51d4-4ed7-8f8b-1f3f44486d45@default> <3b1cf8d3-0aec-4976-8368-74eb46229b95@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
This has just occurred again on another machine. Is anyone else seeing
this?

On Wed, Oct 27, 2010 at 01:29:55PM -0700, Dan Magenheimer wrote:
> > > Unfortunately these kinds of time problems can be notoriously hard to
> > > pin down and diagnose.
> > 
> > This seems to occur when one -- or possibly all -- vcpus
> > are "spinning" for an unexpectedly long period of time.  If so
> > it may be possible to synthesize some kind of long-but-non-infinite
> > deadlock in a domU kernel which might reproduce the problem.
> 
> Saw this on LKML:
> http://lkml.org/lkml/2010/10/27/366 
> 
> The solution refers to a recent git commit so is unlikely to
> be the specific cause for the problem we've seen.  But the
> analysis sounds very familiar and also corresponds to my
> observation above:  In short, SOMEthing (in the guest kernel
> or in Xen) is causing the guest to "go out to lunch" for some
> extended period of time, which confuses the watchdog timer,
> which disables TSC as a clocksource.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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