From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 19:08:45 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 01C3B1065674; Thu, 22 Jan 2009 19:08:45 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [66.93.72.123]) by mx1.freebsd.org (Postfix) with ESMTP id A7BFE8FC1C; Thu, 22 Jan 2009 19:08:44 +0000 (UTC) (envelope-from jeff@sailorfej.net) Received: from [10.3.3.117] (65-122-120-98.dia.static.qwest.net [65.122.120.98]) (authenticated bits=0) by mail.sailorfej.net (8.13.8/8.13.8) with ESMTP id n0MJ8Zsk008178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jan 2009 11:08:36 -0800 (PST) (envelope-from jeff@sailorfej.net) Message-ID: <4978C42E.5050500@sailorfej.net> Date: Thu, 22 Jan 2009 11:08:30 -0800 From: Jeffrey Williams User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> <20090121203654.GB84399@citylink.fud.org.nz> <4977A06B.7060605@sailorfej.net> In-Reply-To: <4977A06B.7060605@sailorfej.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.2 required=6.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.sailorfej.net Cc: mike@jellydonut.org, dimitry@andric.com, killing@multiplay.co.uk, Andrew Thompson 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: Thu, 22 Jan 2009 19:08:45 -0000 Hi Guys, Well this helped sort of, the clocks are running only a little fast at this point (roughly seven minutes gained over 12 hours), but now for some reason, ntpd is not resetting the clocks at all, despite multiple good time sources, it was working fine before the kern.hz change. Any reason why that would break ntpd? Thanks, Jeff Jeffrey Williams wrote: > Hi Guys, > > Ok it is set, it does seem a little better, the clocks are still > running ahead by an average of about 30-40 seconds, but they seem to > have slowed down enough for ntpd to maintain the time by slewing, > instead of stepping. I did get a fresh batch of calcru errors from > one of the servers right after reboot (possibly because I am setting > kern.timecounter.hardware in sysctl.conf instead of loader.conf). I > will let you know how it looks after it has run for an hour or two. > > I tried TSC instead of i8254 on a third server, it was better than > ACPI-safe, but much worse than i8254. > > Thanks, > Jeff > > Andrew Thompson wrote: >> On Wed, Jan 21, 2009 at 12:30:26PM -0800, Jeffrey Williams wrote: >> >>> Hi Guys, >>> >>> Thanks for kern.hz suggestion, but according loader.conf in the >>> /boot/defaults directory, kern.hz is already set to 100, is this >>> overridden somewhere else? >>> >>> >> >> Thats a bit misleading, the commented out value isnt actually the >> default. Set it in the loader.conf, can verify this with 'sysctl >> kern.hz' >> >> >> Andrew >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >