I've got a virtual machine running on a server that I can't stop or reboot - I can't log onto it anymore and I can't stop it using the VMware server console. There are other VM's running so rebooting the host is out of the question. Is there any other way of forcing one machine to stop?
+4
A:
The virtual machine should have it's own process that is visible in task manager. Use sysinternals Process Explorer to find the right one and then kill it from there.
Espo
2008-09-17 10:17:40
+2
A:
If you're on linux then you can grab the guest processes with
ps axuw | grep vmware-vmx
Not sure how you go from here to work out which pid relates to you errant guest.
iAn
2008-09-17 10:20:06
+1
A:
Here's what I did based on
a) @Espo 's comments and
b) the fact that I only had Windows Task Manager to play with....
I logged onto the host machine, opened Task Manager and used the view menu to add the PID column to the Processes tab.
I wrote down (yes, with paper and a pen) the PID's for each and every instance of the vmware-wmx.exe process that was running on the box.
Using the VMWare console, I suspended the errant virtual machine.
When I resumed it, I could then identify the vmware-vmx process that corresponded to my machine and could kill it.
There doesn't seem to have been any ill effects so far.
Rik Garner
2008-09-17 10:58:40
There won't bee any ill effects. VMWare handles processes separately for each VM. In fact it handles the VM Engine and the VM Graphics separately too. So your graphic could crash but your VM will keep working.
Martín Marconcini
2008-09-17 11:00:39
Espo
2008-09-17 11:03:37