On Thursday, 2009-03-19 at 17:02 +0100, Anders Norrbring wrote:
Try having a look around here: http://www.vmware.com/info?id=34
What I did is configure vmware "host.useFastclock = FALSE".
That is a setting for the guest's vmx file as it looks..
Correct, it is. I have:
tools.syncTime = "FALSE" host.useFastclock = "FALSE"
The document also states a custom built kernel with a higher HZ setting, are you using that as well, or only the vmx setting?
No, the standard kernel on both host and guest (host is 11.0). Too high a clock frequency makes your machine too busy. If things go well, you might get a faster response to the user, but it expends more time handling interrupts, and may lose some. That PDF explains it all.
The changes above make the guest be less demanding of the clock, and it works. As long as you do not need to use functions that need an accurate and fast clock, it works better. Of course, do not use NTP on the guest, nor multimedia.
Well, my VMs all drift about 15 seconds per minute now, which is totally unacceptable, so for now I've set: tools.syncTime = "true" tools.syncTime.period = "10" host.useFastclock = "FALSE" which makes clocks, not accurate, but at least fairly okay for the time being. I have no idea if this would work better if I scrapped the VMware Server and go ESXi instead, I'll see if I can set up a test rig to experiment a little. That would of course force me into some major rethinking about how things are run, but what the heck.. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org