2,187
edits
Difference between revisions of "Virtual Machines"
Jump to navigation
Jump to search
→Troubleshooting: Added "Can't VMotion a VM"
(→Troubleshooting: Added "Can't connect to VM Console") |
(→Troubleshooting: Added "Can't VMotion a VM") |
||
| Line 120: | Line 120: | ||
'''A general system error occurred: Failed to create journal file provider''' | '''A general system error occurred: Failed to create journal file provider''' | ||
* Check ESX disks are not full | * Check ESX disks are not full | ||
=== 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 | |||
** Reduce resource usage of VM's that are already running | |||
** Increase cluster capacity | |||
** Reduce the cluster's failover capacity, or allow constraints violations | |||
'''Access to VMFS storage''' | |||
* 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 | |||
'''ESX licensing''' | |||
* 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 | |||
=== Can't VMotion a VM === | |||
'''VM network doesn't exist at destination''' | |||
* VM is using a particular port group which doesn’t exist on the destination ESX | |||
'''ESX / network too busy''' | |||
* VMotion can’t copy across VMs memory contents/changes quickly enough. An alternative is to use a Low Priory VMotion, which is more likely to succeed, but may result in the VM experiencing temporary freezes (avoids full OS downtime, but not without impact to hosted applications) | |||
''ESXs can't communicate''' | |||
* ESXs need to be able to communicate via VMotion network. DNS problems and FQDN inaccuracies can also cause problems | |||
'''VM is connect to CD-ROM/ISO''' | |||
* VMs CD-ROM is connecting to an ISO file via the host ESX, tying it to that ESX | |||