Re: 6.0 on VMWare 5.0: `calcru: negative runtime of -12728437 usec for pid 28 (irq17: lnc0)'

Adjusted cc: to remove private list. On Wed, 9 Nov 2005, Lev Serebryakov wrote: Hello freebsd-stable, FreeBSD 6.0 on VMWare 5.0 prints such messages every 3-4 minute. Also, messages like calcru: runtime went backwards from 40644816 to 40005944 usec for pid 3 (g_up) is shown

Re: 6.0 on VMWare 5.0: `calcru: negative runtime of -12728437 usec for pid 28 (irq17: lnc0)'

Lev Serebryakov wrote this message on Wed, Nov 09, 2005 at 10:53 +0300: Hello freebsd-stable, FreeBSD 6.0 on VMWare 5.0 prints such messages every 3-4 minute. Also, messages like calcru: runtime went backwards from 40644816 to 40005944 usec for pid 3 (g_up) is shown routinely.

Re: 6.0 on VMWare 5.0: `calcru: negative runtime of -12728437 usec for pid 28 (irq17: lnc0)'

Lev Serebryakov wrote: Hello freebsd-stable, FreeBSD 6.0 on VMWare 5.0 prints such messages every 3-4 minute. Also, messages like calcru: runtime went backwards from 40644816 to 40005944 usec for pid 3 (g_up) is shown routinely. timecounter is ACPI-safe, kernel is GENERIC one.

Re: 6.0 on VMWare 5.0: `calcru: negative runtime of -12728437 usec for pid 28 (irq17: lnc0)'

On Wednesday 09 November 2005 10:13, Nate Lawson wrote: Try using TSC or i8254: sysctl kern.MUMBLE.timecounter=TSC (developers@ removed from cc:) Also, consider setting host.useFastclock = FALSE in your server's .vmx file. This makes all the difference for a Linux guest OS, along

6.0 on VMWare 5.0: `calcru: negative runtime of -12728437 usec for pid 28 (irq17: lnc0)'

Hello freebsd-stable, FreeBSD 6.0 on VMWare 5.0 prints such messages every 3-4 minute. Also, messages like calcru: runtime went backwards from 40644816 to 40005944 usec for pid 3 (g_up) is shown routinely. timecounter is ACPI-safe, kernel is GENERIC one. 5.4-STABLE on some virtual