What IS the right NTP behaviour ?

[Brian Reichert]

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 at 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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"

-- 
Brian Reichert				<reichert at numachi.com>
BSD admin/developer at large