Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

When using Guest Introspection and/or 3rd party SVA, VMs power on task from vCenter hang at 0%, 19% or 35% (51578)

Last Updated: 12/14/2017Categories: TroubleshootingTotal Views: 6760Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

VMs powered on from vCenter hang at 0%, 19% or 35%.

VMs can be powered on from the ESXi host directly.

DRS is enabled on the cluster.

After disabling DRS on the cluster, VMs power on successfully.

You may see the message "Invoking Prechecks" in the Power On task details.

Restarting EAM may unblock the hung task and the VM power on successfully but newly Powered On VMs hang at 0% or 19%.

With vCenter Trivia log enabled, in the vxpd.log file, you see entries repeated every 30 seconds similar to:

2017-10-24T13:22:31.056+04:00 [12552 verbose 'vmmoVm' opID=D8F8CFAD-0000F632-87-8a-12] [VmMo::PowerOnInt] Client VM /vpx/vm/#10361/ polling for ESX agent VMs ready

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article provides information on troubleshooting when a VM fails to power on and Guest Introspection and/or 3rd party SVA is used.

Cause

This issue occurs if DRS is enabled and one of the Agent VM is not marked as ready. If VMware Tools is installed but not running on an Agent VM, vCenter does not receive the heartbeat and does not mark the agent VM as ready which prevent the regular/business VM to power on.

Impact / Risks

VMs fail to power on.

Resolution

To resolve the issue, investigate why the VMware Tools in the Agent VM is not running.

Restart VMware Tools on the Agent VM not marked as ready.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

Take Our Survey

Support Assistant