From mboxrd@z Thu Jan 1 00:00:00 1970 From: Niall Fleming Subject: Re: Time Change Issue Xen 4.1 Date: Thu, 17 Nov 2011 12:47:39 +0000 Message-ID: <4EC5026B.6030800@webanywhere.co.uk> References: <4EBD5AA0.3090906@webanywhere.co.uk> <20111111183913.GA9283@phenom.dumpdata.com> <4EC0F20D0200007800060B7D@nat28.tlf.novell.com> <20111114180045.GA14517@phenom.dumpdata.com> <4EC16CA7.70901@goop.org> <20111116142604.GA7476@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1242919255==" Return-path: In-Reply-To: <20111116142604.GA7476@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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1242919255== Content-Type: multipart/alternative; boundary="------------070502040800000603080906" This is a multi-part message in MIME format. --------------070502040800000603080906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit OK, what's the lead time on getting that patched? *Niall Fleming BSc. (Hons)* Systems Administrator Webanywhere Limited Phone: 0800 862 0131 Ext: 203 Web: http://www.webanywhere.co.uk Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB Registered in England with company number 4881346 On 16/11/2011 14:26, Konrad Rzeszutek Wilk wrote: > On Mon, Nov 14, 2011 at 11:31:51AM -0800, Jeremy Fitzhardinge wrote: >> 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. > That is what I think is happening here. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel --------------070502040800000603080906 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit OK, what's the lead time on getting that patched?

Niall Fleming BSc. (Hons)
Systems Administrator
Webanywhere Limited

Phone: 0800 862 0131 Ext: 203
Web: http://www.webanywhere.co.uk

Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB
Registered in England with company number 4881346

On 16/11/2011 14:26, Konrad Rzeszutek Wilk wrote: 
On Mon, Nov 14, 2011 at 11:31:51AM -0800, Jeremy Fitzhardinge wrote:

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.

<nods> That is what I think is happening here.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
--------------070502040800000603080906-- --===============1242919255== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1242919255==--