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
On Thu, Jan 22, 2009 at 11:08:30AM -0800, Jeffrey Williams wrote:
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
On Fri, Jan 23, 2009 at 03:01:51AM +, Adrian Wontroba wrote:
I'm afraid that most of the salient details are inaccessible at work,
but I found this necessary to get sort of acceptable[*] time keeping in
FreeBSD guests under VMware on Windows.
Sorry, I've got VMware on the brain at present,
Hi Folks,
I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2,
Windows Server 2003, on a Dell 2950.
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
On Wed, Jan 21, 2009 at 2:41 PM, Jeffrey Williams j...@sailorfej.net wrote:
Hi Folks,
I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2, Windows
Server 2003, on a Dell 2950.
I am having a problem with the system clock running excessively fast, I
initially tried installing 7.1
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:
On Wed, Jan 21, 2009 at 2:41 PM, Jeffrey Williams j...@sailorfej.net wrote:
Hi Folks,
I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2, Windows
Server 2003, on a Dell 2950.
I am having a problem with the system clock running excessively fast, I
initially tried installing 7.1
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?
Thanks,
Jeff
Maxim Khitrov wrote:
On Wed, Jan 21, 2009 at 2:41 PM, Jeffrey Williams j...@sailorfej.net wrote:
Hi Folks,
On 2009-01-21 09:10:16PM +0100, Dimitry Andric wrote:
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.
Actually I have encountered such problems in mixed-bit environments
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
On 2009-01-21 21:30, Jeffrey Williams wrote:
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?
Look closer, it is commented out in /boot/defaults/loader.conf. :)
Not read all the thread but if you haven't already just set the timer to TSC
fixes things here.
Regards
Steve
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event
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
13 matches
Mail list logo
