From: Philipp Hahn <hahn@univention.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
John Levon <john.levon@sun.com>
Subject: Re: [libvirt] [Xen-devel] [BUG, PATCH-RFC] libvirt localtime and rtc_timeoffset handling in xen-sexpr/sxpr/sxp
Date: Wed, 11 Jan 2012 13:26:31 +0100 [thread overview]
Message-ID: <201201111326.36514.hahn@univention.de> (raw)
In-Reply-To: <1326282844.17210.190.camel@zakaz.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1984 bytes --]
Hello Ian,
Am Mittwoch 11 Januar 2012 12:54:04 schrieb Ian Campbell:
> On Wed, 2012-01-11 at 10:20 +0000, Philipp Hahn wrote:
> > I'm currently tracking a problem in libvirt regarding Xens handling of
> > localtime and rtc_timeoffset. My current understanding (Xen-3.4.3 and
> > Xen-4.1.2 under Linux) of Xend (the depcrecated Python one still used by
> > libvirt) is as this:
> > - for HV domains, the RTC gets setup to either UTC or localtime depending
> > on "/domain/image/hvm/localtime" ± "/domain/image/hvm/rtc_offset".
>
> Are those xenstore paths or a reference to a config file/sxp var?
Those are XenStore paths.
> I don't see the string "rtc_offset" anywhere under tools in
> xen-unstable.
I missed the "time", it's "rtc_timeoffset". Best search for RegExp
rtc.timeoffset, since so you'll find 'rtc/timeoffset' as well.
...
> They get PV time direct from the hypervisor which exposes the
> hypervisor's wallclock to guests via the shared info. It is always UTC.
> See
> http://xenbits.xen.org/docs/unstable/hypercall/include,public,xen.h.html#St
>ruct_shared_info in particular the wc_* fields.
Yes, I figured that out as well, but thanks for the link.
> Classic-Xen kernels by default will take wallclock time from the shared
> info for each gettimeofday but can be configured to be free-running
> (that is the "independent_wallclock" mode).
A lot of documentation still talks about /proc/xen/independent_wallclock,
which doesn't exist in 2.6.32 any more. I wish they would mention the Xen
version and Linux kerbel version they were using ...
Thank you for your fast feedback.
Sincerely
Philipp Hahn
--
Philipp Hahn Open Source Software Engineer hahn@univention.de
Univention GmbH Linux for Your Business fon: +49 421 22 232- 0
Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99
http://www.univention.de/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-01-11 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 10:20 [libvirt] [BUG, PATCH-RFC] libvirt localtime and rtc_timeoffset handling in xen-sexpr/sxpr/sxp Philipp Hahn
2012-01-11 11:54 ` Ian Campbell
2012-01-11 12:26 ` Philipp Hahn [this message]
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=201201111326.36514.hahn@univention.de \
--to=hahn@univention.de \
--cc=Ian.Campbell@citrix.com \
--cc=john.levon@sun.com \
--cc=libvir-list@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).