Date: Tue, 11 Apr 2000 09:01:04 -0700 From: "Sam Leffler" <sam@errno.com> To: <emulation@FreeBSD.ORG>, "Dag-Erling Smorgrav" <des@flood.ping.uio.no> Subject: Re: Clock drift in VMWare Message-ID: <110501bfa3cf$24316d40$24a6d4d1@melange> References: <xzppurwlnn2.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
This usually happens because the vm doesn't get enough timer interrupts (it
happens on Linux and Windows hosts too). The 2.0 toolbox has a time
synchronization mechanism that talks to the host via a backdoor, but it
requires an X server be running in the virtual machine.
In case you're not aware there's vmware news site at news.vmware.com; this
sort of question comes up a lot.
Sam
----- Original Message -----
From: "Dag-Erling Smorgrav" <des@flood.ping.uio.no>
To: <emulation@FreeBSD.ORG>
Sent: Tuesday, April 11, 2000 7:26 AM
Subject: Clock drift in VMWare
> Does anyone have any idea why the clock in a VMWare virtual machine
> runs something like 30% slower than realtime? Is there any way to fix
> that? xntpd just gives up; I'm down to running ntpdate from cron every
> minute...
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?110501bfa3cf$24316d40$24a6d4d1>