Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Cannot power on an ESX/ESXi virtual machine (1003647)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 28704Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

You cannot power on a virtual machine

The Power on button is grayed out

You receive one or more of the following errors:

Your host's BIOS does not have valid NUMA information. Please update the host's BIOS or associate the virtual machine with the processors in a single NUMA node (CEC).

Error connecting: You need execute access in order to connect with the VMware console. Access denied for config file

Purpose

This article guides you through the process of troubleshooting being unable to power on a virtual machine that has been migrated to an ESX host. It helps you eliminate common causes for your problem by verifying that the virtual machine was migrated correctly and is healthy, that there are sufficient resources and permissions to power it on, and that it is compatible with the new host.

Note: In this article, a "migration" includes having migrated a virtual machine from one ESX host to another in vCenter Server, having manually copied or restored a virtual machine to an ESX host, and having used VMware Converter to end up with a virtual machine on an ESX host.

Resolution

Validate that each troubleshooting step below is true for your environment. Each step will provide 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.

Confirm that the virtual machine hardware version is compatible with the new host. For more information, see Virtual machine hardware versions (1003746).

Confirm that the virtual machine is compatible with the new host architecture. For more information, see Troubleshooting host architecture incompatibility (1003747).

Verify that all of the virtual machine's .vmx settings are valid on the new host. For more information, see Validating the .vmx settings of a virtual machine (1003748).

Confirm that the virtual machines are not powered on. In some cases, a virtual machine may be powered on, but may appear as powered off or orphaned/invalid in the vSphere Client. For more information, see Determine the power status of a virtual machine on an ESX or ESXi host (1003737).

Additionally, there are times when one method of powering on a virtual machine does not work but another method does. For more information, see Powering on an ESX/ESXi host's virtual machine (1003738).

Note: If you perform a corrective action in any of the following steps, attempt powering on the virtual machine again.

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 in a vSphere environment (1006737).

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).

Confirm that the virtual machine is valid. For more information, see Virtual machines appear as invalid or orphaned in vCenter Server (1003742).

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

Confirm that there are sufficient resources. For more information, see Investigating ESX/ESXi virtual machine resources (1003745).

Check the integrity of any snapshots. For more information, see Verifying the integrity of the parent disks for an ESX/ESXi virtual machine (1003759).

In some cases, vCenter Server and ESX hosts get to a state where they do not report the state of a virtual machines properly and, therefore, do not report the correct result of vMotion. To resolve this you may have to restart the management agents on ESXi/ESX host and the VMware vCenter Server service on vCenter Server. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490) and Stopping, starting, or restarting vCenter services (1003895).

Note: If your problem still exists after trying the steps in this article:

Gather the VMware Support Script Data. For more information, see Collecting diagnostic information in a VMware Virtual Infrastructure Environment (1003689).

File a support request with VMware Support and note this KB Article ID (1003647) in the problem description. For more information, see How to Submit a Support Request.

Related Information

Restarting the Management agents in ESXi
Collecting diagnostic information in a VMware Virtual Infrastructure Environment
Determine the power status of a virtual machine on an ESX or ESXi host
Powering on an ESX/ESXi host's virtual machine
Investigating power on permissions for ESX/ESXi virtual machines
Virtual machines appear as invalid or orphaned in vCenter Server
Verifying ESX/ESXi virtual machine file integrity
Investigating ESX/ESXi virtual machine resources
Virtual machine hardware versions
Troubleshooting host architecture incompatibility
Validating the .vmx settings of a virtual machine
Verifying the integrity of the parent disks for an ESX/ESXi virtual machine
How to stop, start, or restart vCenter Server services
Identifying the location of virtual machine files in a vSphere environment

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Compreendendo o vSphere Auto Deploy (2005131)

KB
•
Comprensión de vSphere Auto Deploy (2005131)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware vCenter Lab Manager

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware VirtualCenter 2.5.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware vCenter Lab Manager 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant