Networknet.nl

At some point the VMWare Server  host run out of diskspace on which the virtual guest machines were stored. Windows started to complain about low disk space and only 32KB was left. I tried to open VMWare Server console and I got the error message below "511 vmware-serverd service is not running." All virtual machines were running except the one which consumed the remaining diskspace of the physical SAS drives.

To resolve this issue I shutdown one of the virtual machines with a RDP session and moved the directory to another VMWare Server host; next step I did I tried to bring other virtual machines down by a RDP session and at some point I was left with two other virtual machines which both were not accessible by RDP nor by SSH for the linux one.

I opened Task Manager and located the remaining processes for the virtual machines.

vmware-vmx.exe is individual process for each virtual machine. Two were left and I stopped both vmware-vmx.exe processes. Open Services.msc console and restart the "VMware Registration Service" service.

After the service was restarted the initial process of starting the virtual machines started and all virtual machines were up and running. This is how I resolved the problem with VMWare Server, but it brings me back to the root cause of why this happened and one of the import things is to really think how you are going to seize your virtual machines and their disk space. I am going to implement thresholds and notifications with CactiEZ appliance soon and hopefully something which can help you also.