Thank you, Link. I've checked the Archlinux guest - it's clock ~2 times slower. Setting the "clock=pit" doesn't help. VMware people suggest to set "clock=pit nosmp noapic nolapic", or to recompile the guest kernel with CONFIG_HZ=100 (now Archlinux kernel's config has CONFIG_HZ=250).
The same thing with FreeBSD, setting "kern.hz=100" in /boot/loader.conf solves the problem. Cheers, Sergey On Mon, 24 Jul 2006 21:14:02 -0700 Link Dupont <[EMAIL PROTECTED]> wrote: > Are there any other guests that run with a slower clock? There's a > known issue with Linux 2.6 kernels running with a really slow clock. > If I recall correctly, you need to use clock=pic on Linux to run a > clock that doesn't go all wacky. > Not sure how to do it on FreeBSD though. > > Hope this helps. > > -Link > > On Jul 24, 2006, at 6:55 AM, Sergey Manucharyan wrote: > > > Hi folks, > > > > This problem may not be directly related to Archlinux, but I > > believe it > > never happen before. > > A few days ago I've did a system update and now have a problem > > running VMware-server-1.0.0-28343: one of the guests, FreeBSD 6.1, > > is now running with very slow clock, ~10 times slower than the real > > time clock. > > However, another one - Win2003 is running with normal clock and has > > no problems. > > > > Do you have any ideas? > > Any help is appreciated. > > > > Sergey. > > > > _______________________________________________ > > arch mailing list > > [email protected] > > http://www.archlinux.org/mailman/listinfo/arch > > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
