From owner-freebsd-stable@FreeBSD.ORG Wed Jan 21 20:10:16 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EA3F1065779 for ; Wed, 21 Jan 2009 20:10:16 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id E41CC8FC18 for ; Wed, 21 Jan 2009 20:10:15 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [IPv6:2001:7b8:3a7:0:1416:e549:1db8:acb8] (unknown [IPv6:2001:7b8:3a7:0:1416:e549:1db8:acb8]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0E67E11F838; Wed, 21 Jan 2009 21:10:15 +0100 (CET) Message-ID: <49778128.1080104@andric.com> Date: Wed, 21 Jan 2009 21:10:16 +0100 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20090116 Shredder/3.0b2pre MIME-Version: 1.0 To: Jeffrey Williams References: <49777A7E.30904@sailorfej.net> In-Reply-To: <49777A7E.30904@sailorfej.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 20:10:17 -0000 On 2009-01-21 20:41, Jeffrey Williams wrote: > I am having a problem with the system clock running excessively fast, I > initially tried installing 7.1 release but received a nearly continuous > stream of the "calcru: runtime went backward errors" Add the following to your /boot/loader.conf file: kern.hz="100" I always use this setting with FreeBSD under VMware, and it solves all these timing problems for me. (But YMMV.) However, I am not sure what is at fault here, VMware or FreeBSD... I'd guess the latter, since neither Linux nor Windows guest OSes seem to have any such timing problems.