SCIENTIFIC-LINUX-USERS Archives

May 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: clock drift under Hyper-V
From:
Akemi Yagi <[log in to unmask]>
Reply To:
Akemi Yagi <[log in to unmask]>
Date:
Tue, 31 May 2011 00:49:34 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines) 
On Tue, May 31, 2011 at 12:36 AM, Werf, C.G. van der (Carel)
<[log in to unmask]> wrote:
> In my opinion you should NEVER use NTPD in a virtual machine…..
>
> Check out how NTPD works… it tries to adjust “software cycles”to “hardware
> cycles”.
>
> “Hardware cycles” are a bit undefined in a virtual machine.
>
> Best way, in my opinion, is:
>
> -          Adjust clock of host using NTPD.
>
> -          Adjust clock of virtual machine to clock of host using the
> appropriate Vritual tools.
> (Vmware Tools etc).

VMware used to recommend use of vmware tools, but not any more.  The
latest info is always available in this knowledgebase article:

http://kb.vmware.com/kb/1006427

Detailed description can be found in the section NTP Recommendations:

"Note: In all cases use NTP instead of VMware Tools periodic time
synchronization."

Akemi

ATOM RSS1 RSS2