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] S3 sleep in dom0 breaks dom0<->domU wallclock synchroniz

To: Rafal Wojtczuk <rafal@xxxxxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 1 Jul 2010 15:50:32 +0100
Cc:
Delivery-date: Thu, 01 Jul 2010 07:51:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100701030431.GB1431@email>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsZKh0TrftlpuB2S7up0zWaVnk8lgAAqQRM
Thread-topic: [Xen-devel] S3 sleep in dom0 breaks dom0<->domU wallclock synchronization
User-agent: Microsoft-Entourage/12.24.0.100205
On 01/07/2010 04:04, "Rafal Wojtczuk" <rafal@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Hello,
> xen-3.4.3 x86_64, dom0 2.6.34-9.xenlinux as dom0,
> 2.6.32.14-1.2.105.pvops0 in PV domU. /proc/sys/xen/independent_wallclock is
> 0.
> After resume from S3 sleep in dom0, the wall clock in domU is
> desynchronized from dom0's one (the delta is the length of S3 sleep). It
> does not seem that adj_timex is in progress (the delta is constant in time).
> 
> Is it a known issue ? If so, could someone point me to a solution ?

I think that pv_ops domU kernels pick up Xen's wallclock at boot time, but
won't listen for updates thereafter. So if you ran a non-pv_ops domU, you'd
probably find that its wallclock would be correctly updated after S3. Cc'ing
Jeremy as he'll be able to confirm this. I think his answer will be that you
should run ntp in every guest, but I'm not sure how that will react to
unexpected warps in time.

 -- Keir

> Regards,
> Rafal Wojtczuk
> 
> _______________________________________________
> 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