2,187
edits
Difference between revisions of "Virtual Machines"
Jump to navigation
Jump to search
→Can't Start VM: Added a couple of oldies
m (→Can't VMotion a VM: Typo) |
(→Can't Start VM: Added a couple of oldies) |
||
| Line 127: | Line 127: | ||
** Increase cluster capacity | ** Increase cluster capacity | ||
** Reduce the cluster's failover capacity, or allow constraints violations | ** Reduce the cluster's failover capacity, or allow constraints violations | ||
* If no VM's have been recently added to the cluster, its likely that the HA agent on one of the ESX's has stopped functioning, in which case, within the cluster, one of the ESX's will have a red warning/exclamation triangle. If so you can restart HA on that ESX; | |||
*# Highlight this VM, on the Summary tab you should see a notice regarding HA problems | |||
*# 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 | |||
** Reattempt to power on machine | |||
** Manually migrate to a less loaded ESX and reattempt power on | |||
'''Access to VMFS storage''' | '''Access to VMFS storage''' | ||
| Line 139: | Line 147: | ||
'''Waiting for question to be answered''' | '''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 your 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's files have been corrupted | |||
* If the ESX the virtual is/was on has ''failed'' then its likely that only the ESX's network connections have failed, 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 br reachable again | |||
* If there are no ESX failures, then the VM's files are probably corrupted. The VM needs to be re-registered by removing and re-adding it to the inventory. | |||
=== Can't VMotion a VM === | === Can't VMotion a VM === | ||