All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Vermeer <koen@vermeer.tv>
To: Uri Lublin <uri.lublin@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: Clock off in guest
Date: Thu, 14 Feb 2008 10:10:03 +0100	[thread overview]
Message-ID: <1202980203.5438.8.camel@localhost> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160B5F84F0@ehost011-8.exch011.intermedia.net>

On Wed, 2008-02-13 at 09:58 -0800, Uri Lublin wrote:
> The host kernel or kvm.
> If you choose to upgrade your host kernel (and kvm that comes with
> it), make sure
> you are using recent kvm-userspace too (e.g. kvm-60).

Running 2.6.23 on the host with kvm 60 (userspace) and kvm-source 60
(modules).
> 

> >> Or as an alternative, probably not as good, sometimes (when the
> guest's
> >> clocksource is PIT) adding '-tdf' to the command line helps.
> >I cannot find this in man kvm or man qemu.
> I'm not sure about the man pages, but kvm/qemu's help says:
> bash$ /usr/bin/kvm -h | grep tdf
> -tdf            inject timer interrupts that got lost
> 
It doesn't seem to be mentioned in the man pages, but it is indeed there
when running 'kvm --help'.


> Yes, try adding it to the command line that starts the guest
> (executable name may vary):
>    /usr/bin/kvm [kvm-params] -tdf
> Also tdf (time drift fix) only works when using PIT+PIC (no APIC) so
> sometimes it's helpful
> to also add -no-acpi:
>    /usr/bin/kvm [kvm-params] -tdf -no-acpi
> 
I tried both -tdf and -tdf -no-acpi, but it didn't change anything. I
did notice some lines on the host saying 

time drift is too long, 60 seconds were lost

which weren't there when running without '-tdf'.


You were saying -tdf only works when using PIT+PIC, but, as far as I can
tell, the guest is still using tsc. Should I add a kernel parameter like
clocksource=pit to the guest?

I appreciate the help!

Koen


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-14  9:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 12:52 Clock off in guest koen
2008-02-13 17:58 ` Uri Lublin
2008-02-14  9:10   ` Koen Vermeer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-13 16:13 koen
2008-02-13 13:00 koen
2008-02-13 15:55 ` Dan Kenigsberg
2008-02-13 17:07   ` Koen Vermeer
2008-02-13 18:04     ` Dan Kenigsberg
2008-02-14 12:51       ` Koen Vermeer
2008-02-22 14:38         ` Steven Mooij
2008-02-13  9:41 Koen Vermeer
2008-02-13 11:25 ` Dan Kenigsberg
2008-02-13 12:00   ` Uri Lublin

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=1202980203.5438.8.camel@localhost \
    --to=koen@vermeer.tv \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=uri.lublin@qumranet.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.