From: Glauber Costa <glommer@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: dlaor@redhat.com, "Thomas Løcke" <thomas.granvej6@gmail.com>,
kvm@vger.kernel.org, "Glauber Costa" <gcosta@redhat.com>,
"Jan Kiszka" <jan.kiszka@web.de>
Subject: Re: Time and KVM - best practices
Date: Mon, 22 Mar 2010 10:38:43 -0300 [thread overview]
Message-ID: <20100322133843.GC783@mothafucka.localdomain> (raw)
In-Reply-To: <E03907D1-7070-459B-9BA3-74C8B8B8BB5E@suse.de>
On Mon, Mar 22, 2010 at 10:55:18AM +0100, Alexander Graf wrote:
>
> On 22.03.2010, at 10:15, Dor Laor wrote:
>
> > On 03/21/2010 01:29 PM, Thomas Løcke wrote:
> >> Hey,
> >>
> >> What is considered "best practice" when running a KVM host with a
> >> mixture of Linux and Windows guests?
> >>
> >> Currently I have ntpd running on the host, and I start my guests using
> >> "-rtc base=localhost,clock=host", with an extra "-tdf" added for
> >> Windows guests, just to keep their clock from drifting madly during
> >> load.
> >>
> >> But with this setup, all my guests are constantly 1-2 seconds behind
> >> the host. I can live with that for the Windows guests, as they are not
> >
> > Is it just during boot time? If you run ntpdate after the boot inside the guest, does the time is 100% in sync with the host from that moment on?
> >
> > Glauber once analyzed it and blames hwclock call in rc.sysinit
>
> In fact, my kvm-clock based guests lag about 1 second behind as well. I suppose there's some compensation code that doesn't work correctly.
The problem I found, is that we read wallclock information from kvm host, but later on boot,
we call the hwclock binary, which adjusts things as it sees fit. So in this scenario, kvmclock wallclock
time is just not being used at all.
next prev parent reply other threads:[~2010-03-22 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 11:29 Time and KVM - best practices Thomas Løcke
2010-03-22 9:15 ` Dor Laor
2010-03-22 9:55 ` Alexander Graf
2010-03-22 13:38 ` Glauber Costa [this message]
2010-03-22 10:36 ` Jan Kiszka
2010-03-22 12:41 ` Thomas Løcke
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=20100322133843.GC783@mothafucka.localdomain \
--to=glommer@redhat.com \
--cc=agraf@suse.de \
--cc=dlaor@redhat.com \
--cc=gcosta@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=thomas.granvej6@gmail.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