-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-03-20 at 07:22 +0100, Anders Norrbring wrote:
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?
Neither. For NTP to work on the guest the environment has to virtualize a full clock, instead of just using the host timepiece. It can work, but it is not optimal. An NTP server, even less. It is better to use NTP on the host, and configure vmware to sync the guest to the host.
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.
Not really. Watching a movie could be affected, though.
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.
Then you may have an issue on the host, and it is affecting the clocks in the guest, too. About the "vmware tools not available" I have no idea, but try searching on the vmware site, their documentation is good. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknE6bYACgkQtTMYHG2NR9VU6ACfZZd4KYslOBsXNBqP3S6ltRoi S3EAnjsyA+MPLipTjfsHTSLGWbPBPV7s =YA9g -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org