Date: Tue, 20 Mar 2007 11:35:09 +0900 From: "Adrian Chadd" <adrian@freebsd.org> To: "Michael Proto" <mike@jellydonut.org> Cc: Frank Behrens <frank@pinky.sax.de>, Mark Dotson <mark@dmglobal.net>, freebsd-stable@freebsd.org Subject: Re: time goes slow in VmWare Message-ID: <d763ac660703191935v6a4a6360y5b7ee3acb425ff9a@mail.gmail.com> In-Reply-To: <45FEE2BE.8090607@jellydonut.org> References: <200703191609.l2JG9ql8060947@pinky.frank-behrens.de> <200703191845.l2JIjuWN064035@pinky.frank-behrens.de> <45FEE2BE.8090607@jellydonut.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is the most often asked question with virtualisation of PC hardware. The question was finally answered, but here's the reasoning: * The operating system expects the clock/timer hardware to be consistent * The timer hardware in a VM isn't that consistent as the virtualisation environment is actively scheduling available timeslices to VMs; so * timers (and, therefore, your clock) gets screwed up. The solution is to install the VMware or VirtualPC supplied drivers for your environment. They'll include, amongst other things, fixes for the RTC and timer drivers which will fix your clock skew issues (and if you've noticed, things like "sleep" acting oddly.) 2c, Adrian -- Adrian Chadd - adrian@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660703191935v6a4a6360y5b7ee3acb425ff9a>