calcru: runtime went backwards

[Bob Johnson]

On 12/1/05, J. W. Ballantine <jwb at homer.att.com> wrote:
>
> I running 6-RELEASE as a guest under vmware 5.5 and I'm having
> problems with the clock going backwards.  I'm getting the message (sample):
>
> calcru: runtime went backwards from 10542602 usec to 10542600 usec for pid
> 13924
>  (vmware-guestd)
[etc.]
>
> Is this bsd or vmware related, and any way to fix it?
>

I don't have direct experience with this, but the reports I've seen
indicate that vmware has clock problems with both FreeBSD and Linux. 
One suggestion is that in vmware, set

  host.useFastclock = "FALSE"

in the .vmx file.  Another suggestion  is that in FreeBSD 6.0 you can
try setting

  sysctl  kern.MUMBLE.timecounter=TSC

except I don't know what "MUMBLE" is in 6.0.

  sysctl -a | grep timecounter

should reveal it, though.  And if it is already "TSC", try "i8254",
I've seen both recommended.  There are probably other possibilities
(e.g. "ACPI-safe" seems to be the default these days) but as I said, I
have no direct experience with vmware.

It has also been recommended to set "options HZ=1000" in your kernel
configuration.

Hope that helps, and if I got any of that wrong, someone please correct me!

- Bob

--
Spammers: please send mail to bobo1009 at mailtest1.eng.ufl.edu and help
me tune my spam filters!