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] Time Change Issue Xen 4.1

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Time Change Issue Xen 4.1
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Mon, 14 Nov 2011 11:31:51 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxx>, keir.xen@xxxxxxxxx, Niall Fleming <niall.fleming@xxxxxxxxxxxxxxxxx>, pbonzini@xxxxxxxxxx, lersek@xxxxxxxxxx
Delivery-date: Mon, 14 Nov 2011 12:37:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20111114180045.GA14517@xxxxxxxxxxxxxxxxxxx>
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: <4EBD5AA0.3090906@xxxxxxxxxxxxxxxxx> <20111111183913.GA9283@xxxxxxxxxxxxxxxxxxx> <4EC0F20D0200007800060B7D@xxxxxxxxxxxxxxxxxxxx> <20111114180045.GA14517@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1
On 11/14/2011 10:00 AM, Konrad Rzeszutek Wilk wrote:
> Right. With those patches too (he used the xen-settime patch set which has 
> it).
> The hypercall is done (and the do_settime gets called) and the results are 
> saved
> in the RTC. And the wc_sec and wc_nsec are updated and propagated.
>
> The problem is that wc_sec and wc_nsec are only propagated to the
> existing guests.
>
> If you launch a new guest after the 'hwclock', the new guests
> retains the old wallclock time.

Existing (pvops) guests shouldn't see updated wallclock time, because
they never look at the hypervisor's wallclock after boot time.

It's surprising that new guests don't see the updated wallclock though. 
That sounds like a Xen issue.

    J

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

<Prev in Thread] Current Thread [Next in Thread>