public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Hayen <kayhayen-Mmb7MZpHnFY@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Guest Time Question
Date: Tue, 16 Oct 2007 16:37:29 +0200	[thread overview]
Message-ID: <200710161637.29774.kayhayen@gmx.de> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A023A6DD7-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>


Hello Eddie,

Am Montag 15 Oktober 2007 06:13:44 schrieb Dong, Eddie:
> >That 0.1% kills me though. do you mean, that every 1 second, 1
> >will be 1ms
> >off? And for every second thereafter, leaving me with 1 second
> >drift after
> >only 1000 seconds?
>
> Oh, that is not my intension :-(
> I just put a rought estimation here. In old Xen
> time, I know there are ~10-30 seconds shift after ~10 hours.

That's about the same, isn't it? That's 30 seconds shift after 36000 seconds 
and really a lot.

> >I am looking for an absolute value for time difference between
> >guest and host
> >that is supposed to be small over longer periods. Is that not
> >achievable for
> >a paravirtual guest?! I really need gettimeofday() calls to be
> >near exactly
> >the same value for applications in guest and host even after months.
>
> Except adding a hypercall to get host time (i.e. pv timer), or
> using network time, I think cetain amount of shift will be always there.

Do you consider that NTP between guest and host is acceptable? I found this 
btw: http://support.ntp.org/bin/view/Support/KnownOsIssues

Quote:  "It appears that Xen just passes time-related system calls to the 
underlying master domain, and does not require any additional changes to 
support time sync into the guest domains."

When I today told my manager (technical background) about this, it was met 
with utter surprise, because "that should be really simple". Incidentally, I 
recently claimed in a meeting that with modern Linux and paravirtualization, 
this problem should no longer exist.

Is this a design problem for KVM (the hypercall missing yet) or just something 
that the KVM community didn't yet have/find the time to get around to?

Best regards,
Kay

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-16 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 15:58 Guest Time Question Kay Hayen
     [not found] ` <200710041758.56234.kayhayen-Mmb7MZpHnFY@public.gmane.org>
2007-10-05  6:35   ` Izik Eidus
     [not found]     ` <4705DB40.6000603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-06 10:18       ` Kay Hayen
     [not found]         ` <200710061218.19123.kayhayen-Mmb7MZpHnFY@public.gmane.org>
2007-10-06 12:38           ` Izik Eidus
2007-10-08 23:55   ` Dong, Eddie
     [not found]     ` <10EA09EFD8728347A513008B6B0DA77A014E8AFE-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-11 14:54       ` Kay Hayen
     [not found]         ` <200710111654.43659.kayhayen-Mmb7MZpHnFY@public.gmane.org>
2007-10-12  1:11           ` Dong, Eddie
2007-10-13  9:51       ` Kay Hayen
     [not found]         ` <200710131151.15856.kayhayen-Mmb7MZpHnFY@public.gmane.org>
2007-10-15  4:13           ` Dong, Eddie
     [not found]             ` <10EA09EFD8728347A513008B6B0DA77A023A6DD7-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-16 14:37               ` Kay Hayen [this message]
     [not found]                 ` <200710161637.29774.kayhayen-Mmb7MZpHnFY@public.gmane.org>
2007-10-17  2:14                   ` 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=200710161637.29774.kayhayen@gmx.de \
    --to=kayhayen-mmb7mzphnfy@public.gmane.org \
    --cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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