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

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

> Hi Xen-Devel's
> 
> Please see my note below regarding a serious issue where my clock
jumped
> in dom0. I'm sending this through to the devel list as I haven't
managed
> 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
also
> understand that this could be an underlying hardware issue but I have
> another system on exactly the same hardware which hasn't had this
occur.
> 
> 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
Windows
> 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.

James

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