From: Niall Fleming <niall.fleming@webanywhere.co.uk>
To: xen-devel@lists.xensource.com
Subject: Re: Time Change Issue Xen 4.1
Date: Thu, 17 Nov 2011 12:47:39 +0000 [thread overview]
Message-ID: <4EC5026B.6030800@webanywhere.co.uk> (raw)
In-Reply-To: <20111116142604.GA7476@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 1368 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 2221 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-11-17 12:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 17:25 Time Change Issue Xen 4.1 Niall Fleming
2011-11-11 18:39 ` Konrad Rzeszutek Wilk
2011-11-14 9:48 ` Jan Beulich
2011-11-14 18:00 ` Konrad Rzeszutek Wilk
2011-11-14 19:31 ` Jeremy Fitzhardinge
2011-11-16 14:26 ` Konrad Rzeszutek Wilk
2011-11-17 12:47 ` Niall Fleming [this message]
2011-11-22 10:23 ` Niall Fleming
2011-11-30 17:06 ` Niall Fleming
2011-11-30 22:26 ` Konrad Rzeszutek Wilk
2011-12-01 8:55 ` Niall Fleming
2011-12-01 9:53 ` Ian Campbell
2011-12-01 10:28 ` Laszlo Ersek
2011-12-01 18:16 ` Niall Fleming
2011-11-14 10:15 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EC5026B.6030800@webanywhere.co.uk \
--to=niall.fleming@webanywhere.co.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.