From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: system time Date: Thu, 27 Sep 2007 12:45:21 +0200 Message-ID: <46FB89C1.6000205@qumranet.com> References: <46FA5CB2.70206@bppiac.hu> <46FB7B0B.5050907@qumranet.com> <46FB7AA6.5050708@bppiac.hu> <46FB7DFF.6020102@qumranet.com> <46FB7CFB.7020607@bppiac.hu> <46FB80D8.7060308@qumranet.com> <46FB823F.5000300@bppiac.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: kvm-devel To: Farkas Levente Return-path: In-Reply-To: <46FB823F.5000300-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Farkas Levente wrote: > Avi Kivity wrote: > = >>> this means it's better to run ntpd on all guests even if it's running on >>> the host:-(( >>> = >>> = >> I think there are issues with running ntp on the guest due to tsc being >> very inaccurate on virtualized guests. >> = > > does this means it=E1s not possible to run a guest with accurate time? > > = Time should be mostly accurate. Running ntpdate every hour or so should make it even better. For exact timekeeping a paravirtualized device (or a mainframe) is necessary. -- = Do not meddle in the internals of kernels, for they are subtle and quick to= panic. ------------------------------------------------------------------------- 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/