public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Yves Dorfsman <yves-Qq95MN99UUsAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: keeping time
Date: Thu, 27 Dec 2007 10:28:52 +0800	[thread overview]
Message-ID: <200712271028.52234.sheng.yang@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712260731390.16717@nyksae>

On Wednesday 26 December 2007 22:35:29 Yves Dorfsman wrote:
> What is the recommended way to keep the time correct on a UNIX KVM machine
> ?
>
> I am using Linux x86_64 (gentoo) both as a host and as a guest, and can't
> keep the time straight on the guest. Ntpd eventually gives up because the
> clock is too wanky.

What's your guest kernel version? 

When I debug my in kernel PIT(not sent yet, though kept for months), I found 
the kernel version have something to do with the timer accuracy. On my 
limited test, the kernel 2.6.18, 2.6.20, 2.6.22 with default kernel 
parameters works well with my PIT patch. But for kernel 2.6.9, I have to 
use "clock=pit", otherwise the timer is much faster.

And for current KVM, I found 2.6.18 is very slow compared to host. 2.6.20 is 
about 1/3 slow. (host: 30s, guest: 40s, using "sleep"), and 2.6.22 is OK.

>
> I run into this problem both with versions 28 and 57.
>
> Thanks.
>
>
> Yves.
>
> PS: I realize this is for kvm developers, but could not find a KVM user
> list - please point me towards the apropriate list if this is the wrong
> choice.
> ----
> Yves Dorfsman                                             yves-Qq95MN99UUsAvxtiuMwx3w@public.gmane.org
>                                                     http://www.SollerS.ca
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel



-- 
Thanks
Yang, Sheng

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

  parent reply	other threads:[~2007-12-27  2:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 14:35 keeping time Yves Dorfsman
2007-12-26 14:39 ` Izik Eidus
2007-12-26 14:51 ` Avi Kivity
     [not found]   ` <47726A7D.1010103-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-26 17:13     ` Yves Dorfsman
2007-12-26 17:10       ` Izik Eidus
     [not found]         ` <47728B01.1090603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-26 17:51           ` Yves Dorfsman
2007-12-27  2:28 ` Yang, Sheng [this message]
     [not found]   ` <200712271028.52234.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2007-12-27  6:51     ` Yves Dorfsman
2007-12-27  7:05       ` Yang, Sheng
2007-12-27  7:19     ` Dong, Eddie

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=200712271028.52234.sheng.yang@intel.com \
    --to=sheng.yang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=yves-Qq95MN99UUsAvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox