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.
I suppose you mean not ntp as server, but I guess it would be okay to use ntp for syncing the guest clock to the real world? After all, I have a VM running MySQL and many queries are time related.. Another VM is working as a media streaming server, but I doubt time would affect that much.
No interrupt function at all.. Currently I boot the host o/s with 'hpet=disable nohpet clocksource=acpi_pm'
Why? :-?
Just stumbling around in the dark...
But that may be why you are getting the no irq message in the host. That setting is intented for the guest, not the host. You have to play mainly with vmware settings and guest settings.
Nope, the interrupt issues was long before that change, I just tested everything. Setting the host.useFastclock to false seems to have helped a lot, but now I see that heartbeat often is "gone" and management interface reports "vmware tools not available" in some of the guests. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org