From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, Jan Beulich <JBeulich@suse.com>,
keir.xen@gmail.com,
Niall Fleming <niall.fleming@webanywhere.co.uk>,
pbonzini@redhat.com, lersek@redhat.com
Subject: Re: Time Change Issue Xen 4.1
Date: Mon, 14 Nov 2011 11:31:51 -0800 [thread overview]
Message-ID: <4EC16CA7.70901@goop.org> (raw)
In-Reply-To: <20111114180045.GA14517@phenom.dumpdata.com>
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
next prev parent reply other threads:[~2011-11-14 19:31 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 [this message]
2011-11-16 14:26 ` Konrad Rzeszutek Wilk
2011-11-17 12:47 ` Niall Fleming
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=4EC16CA7.70901@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=lersek@redhat.com \
--cc=niall.fleming@webanywhere.co.uk \
--cc=pbonzini@redhat.com \
--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.