Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Cannot power on an ESX/ESXi virtual machine when nothing changed

Symptoms

  • Cannot power on an ESX/ESXi virtual machine
  • Power on button grayed out
  • Error messages
  • Virtual machine crashes

boot-guest-os power-on-option-greyed-out

Purpose

This article guides you through the process of troubleshooting being unable to power on a virtual machine that you were able to power on previously, and where you are not aware of any changes having been made to your environment since the last successful power on. The article provides steps that assist you in eliminating common causes for your problem by verifying that the virtual machine is healthy, that there are sufficient resources and permissions to power it on, and that there is nothing wrong with the storage system on which it is located.

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. These steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

Note: If you perform a corrective action in any of the following steps, attempt powering on the virtual machine again.
  1. Confirm that the virtual machine cannot power on. In some cases, a virtual machine may be powered on, but may not be obvious. For more information, see Investigating if an ESX/ESXi virtual machine is powered on (1003737).

    Also, there may be a situation when one method to power on a virtual machine may fail, but another works. For more information, see Methods of powering on an ESX/ESXi virtual machine (1003738).

  2. Confirm that you are trying to power on the correct virtual machine. You may be powering on a virtual machine that does not actually correspond to the virtual machine that you are trying to work with. For more information, see Identifying the location of virtual machine files (1006737).

  3. Confirm that the virtual machine is valid. For more information, see Determining if a virtual machine is orphaned (1003742).

  4. Confirm that the virtual machine files and directory are accessible. For more information, see Verifying that ESX/ESXi virtual machine storage is accessible (1003751).

  5. Confirm that there is sufficient free disk space. For more information, see:

  6. Confirm that there is no virtual machine file corruption.For more information, see Verifying ESX/ESXi virtual machine file integrity (1003743).

  7. Confirm that there are sufficient permissions for you to power on the virtual machine. For more information, see Investigating power on permissions for ESX/ESXi virtual machines (1003739).

  8. Confirm that there are sufficient resources . For more information, see:

  9. If you have configured a cluster, verify that the virtual machine is not powered on for any of the hosts in the cluster. For each host in the cluster, see Investigating if an ESX/ESXi virtual machine is powered on (1003737).

  10. Verify that none of the virtual machine's resources are showing as busy. For more information, see Investigating busy ESX/ESXi virtual machine resources(1003756).

  11. Confirm that no more than 32,000 files exist on the virtual machine's datastore. For more information, see Investigating an out of resources error for a datastore (1003762).

If the issue continues to exist after trying the steps in this article:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback


Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
Actions