Brian Mathis wrote:
On Sat, Jun 26, 2010 at 9:26 AM, Les Mikesell lesmikesell@gmail.com wrote:
Emmanuel Noobadmin wrote:
The creeping CPU problem happens slowly over the course of a week or so, so if you're seeing acute freeze-ups, then that's probably not it. However, if all machines have been running for a while, try to suspend/resume all of them, then see if the problem goes away.
That is pretty much what we see. Sometimes we leave the machine on through several days if there was no changes to what we are doing on it and sometimes the VM freezes after a few days. Had appeared random because anyone of us could have restarted the VM during the week so those lock up probably happened when none of us did.
Is this with VMware Server 2.x? I have machines with the 1.x version (some one Centos3, some on Centos5) that run more or less forever without issues. Also, the ESXi version is even better if you are only using it to host VMs.
Yes, this problem is with Server 2.x only.
It is still probably reasonable to install the latest 1.x you can find - you just have to have the matching client to access the console remotely. But, I normally only use the client to get to the point where the network is up and I can go to the guest directly with ssh/freenx/vnc. The only problem I ever see on those VMs is instability in the clock - but the real fix is to use ESXi instead with everything running as guests.