From: Jan Kiszka <jan.kiszka@siemens.com>
To: al pat <alps.oss@gmail.com>
Cc: qemu-devel@nongnu.org, Philipp Hahn <hahn@univention.de>
Subject: Re: [Qemu-devel] Question on kvm_clock working ...
Date: Tue, 13 Sep 2011 15:08:35 +0200 [thread overview]
Message-ID: <4E6F55D3.1070501@siemens.com> (raw)
In-Reply-To: <CAF9p443R5bntppp9Nf_Ea_3KDLJiJAtfm8sBpeagKT3U-k06RQ@mail.gmail.com>
On 2011-09-13 13:38, al pat wrote:
> Thanks Phillip.
>
> My current source is "kvm-clock".
>
> WHen I start my guest, it is in sync with the host clock.
>
> Then, I chance the time on my host - using "date --set ...". I don't see the
> guest update its time.
> I was expecting that the guest will detect host time change and change it?
That's not what kvmclock is supposed to provide. Besides a monotonic
clock source, it basically offers an alternative persistent clock, to
some degree replacing the emulated RTC. So updates of the host system
time are only recognized by the guest kernel when it reboots or
suspends/resumes.
>
> So, when the host is exporting its system time and TSC values, does it go
> into the "emulated RTC" of the guest and the guest checks it only once? Or
> does the guest resync its clock with the host's value periodically?
>
> I can try to do: "hwclock --hctosys --utc" --- this is just to check. (I
> have kvm-clock as my clock source though).
Re-reading the RTC is a brute-force approach to re-synchronize with the
host. If potential clock jumps are OK for your use case, you can go that
way.
Alternatives are using NTP against a time server or writing a RTC plugin
for NTP to synchronize against that local source (a colleague once wrote
such a plugin for a special guest, but it never made it into public AFAIK).
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-09-13 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 15:28 Question on kvm_clock working al pat
2011-09-09 15:28 ` [Qemu-devel] " al pat
2011-09-12 13:21 ` al pat
2011-09-13 6:49 ` Philipp Hahn
2011-09-13 11:38 ` al pat
2011-09-13 13:08 ` Jan Kiszka [this message]
2011-09-15 13:48 ` al pat
2011-09-26 17:47 ` Ronen Hod
2011-09-26 17:47 ` [Qemu-devel] " Ronen Hod
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=4E6F55D3.1070501@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alps.oss@gmail.com \
--cc=hahn@univention.de \
--cc=qemu-devel@nongnu.org \
/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.