2,187
edits
Difference between revisions of "Virtual Machines"
Jump to navigation
Jump to search
→Could not power on VM: No swap file. Failed to power on VM: Updated
(→Can't Start VM: Reworked) |
|||
| Line 281: | Line 281: | ||
** The VM's files have been corrupted / locked | ** The VM's files have been corrupted / locked | ||
If the ESX the virtual is/was on has ''failed'' and HA's isolation response is set to leave powered-on then its possible that only the ESX's network connections have failed, and the virtual machines are still running on the ESX, but are isolated from the network. | |||
If the ESX the virtual is/was on has ''failed'' then its possible that only the ESX's network connections have failed, and the virtual machines are still running on the ESX, but are isolated from the network. | |||
* To cause a full HA failover, pull the power cables out of the ESX to kill it completely | * To cause a full HA failover, pull the power cables out of the ESX to kill it completely | ||
* Alternatively, attempt to restore network connectivity to allow the VM's to be reachable again | * Alternatively, attempt to restore network connectivity to allow the VM's to be reachable again | ||
If there have been no ESX failures, then the VM's files may be corrupted. The VM can be re-registered by removing and re-adding it to the inventory, but the re-add may fail if the wrong files are corrupted. To investigate corruption further... | |||
* To test whether the ESX should be able to lock the VM's files use <code> touch </code>. Within the VM's directory, do <code> touch *.vswp </code> | |||
** If success, retry power on | |||
** If <code> device or resource busy </code> then the VM is probably owned by another ESX - find that ESX! | |||
** If <code> Invalid argument </code> then the file can't be accessed (eg corrupt or other storage problem) | |||
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] | ||