Date: Sun, 6 Sep 2009 20:12:45 -0600 From: Tim Judd <tajudd@gmail.com> To: Hashimoto <hsmtkk@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Clock delays in FreeBSD guest VM on VirtualBox Message-ID: <ade45ae90909061912s77567935te530ad60aa71a612@mail.gmail.com> In-Reply-To: <6bae2c430909060711m3c57adfej33014f84cb23874@mail.gmail.com> References: <6bae2c430909060711m3c57adfej33014f84cb23874@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/6/09, Hashimoto <hsmtkk@gmail.com> wrote: > Hello. > > I am running several FreeBSD(8.0-BETA3) guest VMs > on VirtualBox on OpenSolaris. > On all hosts, I am configuring & running ntpd. > > However, only one host (naming HostX) can sync the clock. > All hosts except for HostX cannot sync the clock. > (The time delays about 10 minutes in an hour.) > What's the cause of this problem? > Regards. > > /etc/rc.conf > ntpd_enable="YES" > ntpd_sync_on_start="YES" > > /etc/ntp.conf (default config file) > server 0.freebsd.pool.ntp.org iburst maxpoll 9 > server 1.freebsd.pool.ntp.org iburst maxpoll 9 > server 2.freebsd.pool.ntp.org iburst maxpoll 9 > > -- > Kouki Hashimoto > hsmtkk@gmail.com Timing problems can be due to kern.hz The older kern.hz was set to 100, and now it's set at 1000 The hardware clock may need adjusting, see sysctl kern.timecounter.choice Only one that seems relatively current is installing the vmtools with vmware hypervisor. Said tools even support guest shutdown and the rest. I would say without tools support, you have slim possible chances to synchronize timings, and timing problems will keep you guessing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae90909061912s77567935te530ad60aa71a612>