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

My Subscriptions

Loading

Knowledge Base

Determining why a single virtual machine is inaccessible on an ESXi host or vCenter Server system (1018834)

Last Updated: 10/9/2020Categories: TroubleshootingTotal Views: 201562Language:
Chinese (Simplified)JapaneseSpanishEnglish

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Clients connected to services running in a virtual machine are no longer accessible.

Applications dependent on services running in a virtual machine are reporting errors.

A virtual machine no longer responds to network connections.

A virtual machine no longer responds to user interaction at the console.

Purpose

This article provides troubleshooting steps to help determine why a virtual machine appears unresponsive.

Resolution

Validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking 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.

To determine why a virtual machine is unresponsive:

Determine if there are multiple virtual machines experiencing these symptoms. If so, see Determining why multiple virtual machines are inaccessible (1019000).

Determine if the virtual machine is currently powered off:

Open the vSphere Client and connect to the vCenter Server.

Provide administrative credentials when prompted.

Ensure that you are in the Hosts & Clusters view.

Select the virtual machine that is currently exhibiting the symptoms in the Inventory.

Click the Summary tab.

In the General dialog, confirm that the State: shows as Powered Off. If so, see Determining why a virtual machine was powered off or restarted (1019064).

Determine if there are any tasks that are currently running that may affect the virtual machine. Open the vSphere Client and look for the Recent Tasks pane at the bottom of the client screen. If you do not see the Recent Tasks pane, click View and ensure that Status Bar is selected. You may also notice that certain options are grayed out for managing the virtual machine. If a task on a virtual machine is in progress, depending on circumstances, it may have an adverse effect on your virtual machine.

The task and percentage may provide details on the progress of the operation. The additional information section of this article includes a list of tasks that are known to cause a virtual machine to appear unresponsive. If your virtual machine is in this state, you may also want to search for the task and the percentage within the knowledge base. If the error has not been documented within the knowledge base, submit a support request. For more information, see How to submit a support request.

Verify the functionality of the virtual machine's remote console:

Open the vSphere Client and connect to the vCenter Server.

Provide administrative credentials when prompted.

Ensure that you are in the Hosts & Clusters view.

Select the virtual machine that is currently exhibiting the symptoms in the Inventory.

Click the Console tab:

If the guest operating system displays a kernel based error such as a blue screen or a kernel panic, see Verifying if software is causing your virtual machine to fail (1003999).

If the virtual machine remote console does not respond to user interaction via mouse or keyboard, see Determining why a virtual machine does not respond to user interaction at the console (1017926).

Verify that the virtual machine responds to network traffic or ping requests:

Note: For more information on how to use the ping command, see Testing network connectivity with the Ping command (1003486). Other tools such as SSH for linux based machines or Remote Desktop for Microsoft Windows based machines can also be used to test the functionality of the host.

Open a console from your current desktop.

Ping the virtual machine using the IP address.

Ping the virtual machine using the DNS address.

Optionally, attempt to connect to the virtual machine through a remote connection such as RDP or SSH.

Repeat steps 1 and 2 from the console of the user who is reporting the issue.

If any of the ping tests fail, see Troubleshooting virtual machine network connection issues (1003893).

Determine if the virtual machine has been recently rebooted:

Open the vSphere Client and connect to the vCenter Server.

Provide administrative credentials when prompted.

Ensure that you are in the Hosts & Clusters view.

Select the virtual machine that is currently exhibiting the symptoms in the Inventory.

Click the Console tab.

Log into your guest operating system using administrative credentials.

Determine the uptime of your guest operating system.

For Linux based operating systems, the command uptime displays the current uptime.

Note: The preceding link was correct as of July 26, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

If your virtual machine was off or has rebooted abruptly, see Determining why a virtual machine was powered off or restarted (1019064).

For additional troubleshooting steps for a non responding virtual machine, see Troubleshooting a virtual machine that has stopped responding (1007819).

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

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.

Gather VMware Support Script Data.

Related Information

For related information, see these articles about tasks that may cause a virtual machine to stop responding at the console:

A snapshot removal can hang a virtual machine for a long time (1002836)

Virtual machine stops responding during backup (1002025)

Ensuring a virtual machine is not inaccessible due to a VMware VirtualCenter issue (1007808)

Troubleshooting a virtual machine that has stopped responding
Determinar por qué una sola máquina virtual no puede acceder a un host ESX/ESXi o a un sistema de vCenter Server
ESX/ESXi ホストまたは vCenter Server システム上の特定の仮想マシンがアクセス不能になっている原因を特定する
确定无法在 ESX/ESXi 主机或 vCenter Server 系统中访问单个虚拟机的原因

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

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 vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

Take Our Survey

Support Assistant