Date: Wed, 23 Sep 2015 15:27:29 -0400 From: Brian Reichert <reichert@numachi.com> To: Brandon Vincent <Brandon.Vincent@asu.edu> Cc: Tim Kientzle <tim@kientzle.com>, hackers@freebsd.org, Poul-Henning Kamp <phk@freebsd.org> Subject: Re: What IS the right NTP behaviour ? Message-ID: <20150923192729.GB78209@numachi.com> In-Reply-To: <CAJm4238%2BJCfg7Xb2vMJ4--4uLPXrjn6EJzuc8xJdAeA-aXr7-A@mail.gmail.com> References: <39337.1442999127@critter.freebsd.dk> <F6AF299A-17B1-44DF-B025-B8FA0BC833D4@kientzle.com> <CAJm4238%2BJCfg7Xb2vMJ4--4uLPXrjn6EJzuc8xJdAeA-aXr7-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: > On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle <tim@kientzle.com> wrote: > > One concern I keep running into: Using NTP in VMs that are frequently suspended/resumed. Though I suppose this may be covered by your 'workstation' scenario (just step it after VM resume when you see the large skew). > > I would assume your hypervisor would sync the clock upon VM events. Does it not? In my VMs that run an NTP client, I keep the hypervisor out of the loop, and let the guest's NTP client to it's work. E.g.: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427 NTP Recommendations VMware recommends using NTP instead of VMware Tools periodic time synchronization. NTP is an industry standard and ensures accurate timekeeping in your guest. It may be necessary to open the firewall (UDP 123) to allow NTP traffic. > > Brandon Vincent > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Brian Reichert <reichert@numachi.com> BSD admin/developer at large
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150923192729.GB78209>