2,187
edits
Difference between revisions of "Virtual Machines"
Jump to navigation
Jump to search
→Troubleshooting: Added "Can't Stop / Power-Off a VM"
(→Could not power on VM: No swap file. Failed to power on VM: Further update) |
(→Troubleshooting: Added "Can't Stop / Power-Off a VM") |
||
| Line 298: | Line 298: | ||
For further info see - [http://kb.vmware.com/kb/10051 VMware KB10051 - Virtual machine does not power on because of missing or locked files] | For further info see - [http://kb.vmware.com/kb/10051 VMware KB10051 - Virtual machine does not power on because of missing or locked files] | ||
=== Can't Stop / Power-Off a VM === | |||
This normally occurs because you've lost management (VI Client) access to the ESX, or the ESX doesn't appear to be aware that its running the VM, but it is (so appears ''Inaccessible'' via the VI Client). If you have access to the VM via the VI Client but can't power off, it'll probably be a permissioning issue. There is no way to gracefully shutdown a VM without access via the VI Client (or direct access to the VM via RDP, VNC, etc). | |||
# SSH to the ESX you believe the VM is running on | |||
# Find the path to the VM's config file | |||
#* EG <code> vmware-cmd -l | grep VM_Name </code> | |||
#* If the VM is not listed, the VM isn't registered to that ESX | |||
# Instruct the ESX to power off the VM using the VMX path already found | |||
#* EG <code> vmware-cmd /path/to/VM_Name.vmx stop </code> | |||
If the above fails, you'll need to get a bit more forceful... | |||
# Find the PID of the VM | |||
#* EG <code> ps -auxwww | grep VM_Name </code> | |||
# Kill the VM using the PID found ''(make sure you've got the right PID, you could kill the ESX by mistake!)'' | |||
#* EG <code> kill -9 1234 </code> | |||
=== Can't VMotion a VM === | === Can't VMotion a VM === | ||