From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Time Change Issue Xen 4.1 Date: Mon, 14 Nov 2011 11:31:51 -0800 Message-ID: <4EC16CA7.70901@goop.org> References: <4EBD5AA0.3090906@webanywhere.co.uk> <20111111183913.GA9283@phenom.dumpdata.com> <4EC0F20D0200007800060B7D@nat28.tlf.novell.com> <20111114180045.GA14517@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111114180045.GA14517@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com, Jan Beulich , keir.xen@gmail.com, Niall Fleming , pbonzini@redhat.com, lersek@redhat.com List-Id: xen-devel@lists.xenproject.org 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