On 12/17/09 16:40, Steve Polyack wrote:
On 12/17/09 16:23, Chuck Swiger wrote:
The "kern.hz=100" recommendation I can certainly agree with, but
there is mostly no point in running ntpd or variants anywhere except
on the host machine ("host ESX" for VMware, or Dom0 for Xen). For
VMware, the vmtools stuff should provide a mechanism to sync time in
VMs to the host clock.
I haven't used Xen, but for ESX: I may be wrong, but I'm pretty sure
that the vmtools available for FreeBSD do not support synchronizing
the host time to the guest OS. I know it is supported (and works) for
Linux, but by what mechanism I do not know. On OpenBSD the kernel can
be built to present a device which will use the "synchronize time with
guest" feature of VMware to provide a clock source which can be
specified in ntpd.conf.
Perhaps you're right and all it takes is the switch in ESX. I've
disabled ntpd on one of my VMs and I'll see if it drifts any by tomorrow.
FYI the system has started to drift on the order of 100ms every 6
hours. This leads me to believe that the "synchronize time with guest"
feature of ESXi is not sufficient in FreeBSD with VMware tools. While
using NTP, the system would reliably keep in sync within 30ms of local
NTP relays.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
