From mboxrd@z Thu Jan 1 00:00:00 1970 From: Niall Fleming Subject: Re: Time Change Issue Xen 4.1 Date: Wed, 30 Nov 2011 17:06:56 +0000 Message-ID: <4ED662B0.8060105@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="------------090409030509090602080107" 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 Cc: Jeremy Fitzhardinge , Konrad Rzeszutek Wilk , keir.xen@gmail.com, Jan Beulich , pbonzini@redhat.com, lersek@redhat.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------090409030509090602080107 Content-Type: multipart/alternative; boundary="------------040106090902070402050703" --------------040106090902070402050703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Another week, and no response? ping? Please? *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 --------------040106090902070402050703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Another week, and no response?

ping?

Please?

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
--------------040106090902070402050703-- --------------090409030509090602080107 Content-Type: text/plain; name="Attached Message Part" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Attached Message Part" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --------------090409030509090602080107 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 --------------090409030509090602080107--