Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Troubleshooting a non-responsive virtual machine
Symptoms
- The virtual machine stops responding and cannot be controlled
-
The virtual machine experiences a core dump
-
The virtual machine suffers from performance problems
-
The virtual machine experiences network connectivity issues
-
Any task done shows "In Progress" in Virtual Infrastructure tasks and never completes
-
You see the error:
Not enough resources to Power On the virtual machine
Purpose
The article discusses the common things that needs to be checked for troubleshooting a non-responsive virtual machine.
Resolution
Please 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. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
-
Verify that the virtual machine is not in an unresponsive state.
In a non-responsive system, the operating system seems to be paralyzed, no error messages are displayed, and the screen freezes or the application does not respond to users' actions. Keyboard input or mouse clicking has no effect, regardless of where the cursor is placed, but the operating system is still running. Unlike a failure, sometimes a non-responsive system resolves itself, and the application resumes its normal execution without your involvement.
A failure is a situation where the operating system has terminated and is no longer running. There may be a purple diagnostics screen or error message visible in it's place.
Note: There is a difference between a virtual machine failing and the guest operating system failing. If the virtual machine fails, it powers off and vmware-core files are created in the virtual machines host directory. In the vmware.log file, you may see an entry similar to:
Sep 13 19:58:46: vcpu-1| MONITOR PANIC: ASSERT failed
Sep 13 19:58:46: vcpu-1| Core dump with build build-10104
Sep 13 19:58:46: vcpu-1| Writing monitor corefile
"/root/vmware/vm1/vmware-core0.gz"
In some cases VirtualCenter and the ESX hosts get into a state where they are not reporting a virtual machines state properly. For more information, see Virtual machine stops responding in a Power On state in VirtualCenter (1002687). -
Ensure you do not have missing or locked files. Often, you receive the following error when there are missing or locked files:
Error:"unable to locate vm swap file. failed to power on vm"
For more information, see Virtual machine does not power on because of missing or locked files (10051). -
Ensure you have enough resources available to run your virtual machine. For more information, see Investigating ESX/ESXi virtual machine resources (1003745).
Note: If your problem still exists after trying the steps in this article, please file a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request.
Additional Information
Tags
See Also
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.
Actions
- KB Article:
- Updated:
- Categories:
- Product Family:
- Products:
- Product Versions:

