2,187
edits
Difference between revisions of "Virtual Machines"
Jump to navigation
Jump to search
→Can't Start VM: Reworked
m (→Files Information: typo) |
(→Can't Start VM: Reworked) |
||
| Line 250: | Line 250: | ||
=== Can't Start VM === | === Can't Start VM === | ||
==== HA Admission Control ==== | |||
* Can't start VM as doing so wouldn't leave enough failover capacity in order to be able to restart failed VM's should an ESX fail. Options are to | * Can't start VM as doing so wouldn't leave enough failover capacity in order to be able to restart failed VM's should an ESX fail. Options are to | ||
** Reduce resource usage of VM's that are already running | ** Reduce resource usage of VM's that are already running | ||
| Line 259: | Line 259: | ||
*# Run the '''Reconfigure for HA''' command, this will re-install the HA agent on the ESX | *# Run the '''Reconfigure for HA''' command, this will re-install the HA agent on the ESX | ||
==== Failed to relocate virtual machine ==== | |||
* DRS is attempting to relocate a VM at power up, and this relocation failing | * DRS is attempting to relocate a VM at power up, and this relocation failing | ||
** Reattempt to power on machine | ** Reattempt to power on machine | ||
** Manually migrate to a less loaded ESX and reattempt power on | ** Manually migrate to a less loaded ESX and reattempt power on | ||
==== Access to VMFS storage ==== | |||
* ESX may have lost connectivity to VMFS partition on which VM resides | * ESX may have lost connectivity to VMFS partition on which VM resides | ||
==== VMFS full ==== | |||
* If VMFS is full, the ESX won't be able to write to the VM's logs when it starts it up, causing VM start-up to fail | * If VMFS is full, the ESX won't be able to write to the VM's logs when it starts it up, causing VM start-up to fail | ||
==== ESX licensing ==== | |||
* Either ESX isn't licensed, or has lost contact with the license server (VI3) for a long period of time | * Either ESX isn't licensed, or has lost contact with the license server (VI3) for a long period of time | ||
==== Waiting for question to be answered ==== | |||
* Generally after changes (such as cold migrations or new deployments), a VM may need to have a question answered before it can continue to power on | * Generally after changes (such as cold migrations or new deployments), a VM may need to have a question answered before it can continue to power on | ||
==== Could not power on VM: No swap file. Failed to power on VM ==== | |||
* The ESX | * The ESX you're starting the VM up on can't get proper access the VM's files, either because | ||
** The VM is already powered up on another ESX | ** The VM is already powered up on another ESX | ||
** The VM's files have been corrupted | ** The VM's files have been corrupted / locked | ||
* | If there have been no ESX failures, then the VM's files are probably corrupted. The VM can be re-registered by removing and re-adding it to the inventory. | ||
* | |||
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 | |||
* Alternatively, attempt to restore network connectivity to allow the VM's to be reachable again | |||
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 VMotion a VM === | === Can't VMotion a VM === | ||