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: Further update
(→Could not power on VM: No swap file. Failed to power on VM: Further update) |
|||
| Line 291: | Line 291: | ||
** If <code> device or resource busy </code> then the VM is probably owned by another ESX - find that ESX! | ** 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) | ** If <code> Invalid argument </code> then the file can't be accessed (eg corrupt or other storage problem) | ||
* Its also worth doing a <code> touch </code> on the following files, if they are not inaccessible then the VM may be recoverable. To work-around the <code> .vswp </code> issue, remove the reference to the file in the <code> .vmx </code> config file | |||
** <code> touch *.vmx </code> | |||
** <code> touch *flat.vmdk </code> | |||
** <code> touch *delta.vmdk </code> | |||
** <code> touch vmware.log </code> | |||
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] | ||