Date: Wed, 21 Jan 2009 14:23:39 -0800 From: Jeffrey Williams <jeff@sailorfej.net> To: Andrew Thompson <thompsa@freebsd.org>, dimitry@andric.com Cc: killing@multiplay.co.uk, freebsd-stable@freebsd.org Subject: Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server Message-ID: <4977A06B.7060605@sailorfej.net> In-Reply-To: <20090121203654.GB84399@citylink.fud.org.nz> References: <49777A7E.30904@sailorfej.net> <26ddd1750901211209k83250d7re8bb82dc2965ccd0@mail.gmail.com> <497785E2.5040007@sailorfej.net> <20090121203654.GB84399@citylink.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
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" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4977A06B.7060605>