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 if a High Availability Virtual Machine Monitoring event caused a virtual machine to reboot (1027734)

Last Updated: 4/13/2015Categories: How toTotal Views: 90775Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Virtual machine running on an ESX/ESXi host is rebooted unexpectedly

The ESX/ESXi host where the virtual machine is registered is a part of an VMware High Availability (HA) cluster in vCenter Server and Virtual Machine Monitoring is enabled on the HA cluster

Purpose

This article provides information about the logs and events to determine if the reboot was caused by HA Virtual Machine Monitoring.

Resolution

To look for events related to the virtual machine in vCenter Server:

Select the virtual machine in vCenter Server.

Click the Tasks & Events tab.

Click the Events button.

Enter the word reset in the search field.

If HA Virtual Machine Monitoring was responsible for resetting the virtual machine, you see an Event similar to:

This virtual machine reset by HA. Reason: VMware Tools heartbeat failure. A screenshot is saved at /vmfs/volumes/4c4850e4-0dcce710-28d9-00215-a5d36b8/wdcsmdc2/wdcsmdc2-screenshot-0.png

Example:

Note: The reason in the Description field may differ slightly, but it always states that the virtual machine was reset by HA if Virtual Machine Monitoring is involved.

On the ESX/ESXi host, two logs can help identify Virtual Machine Monitoring as the source of the virtual machine reboot. If Virtual Machine Monitoring is the cause:

In the /var/log/vmware/hostd.log file, you see entries similar to:

T F5760B90 verbose 'vm:/vmfs/volumes/4c4850e4-0dcce710-28d9-00215a5d36b8/wdcsmdc2/wdcsmdc2.vmx'] Updating current heartbeatStatus: red
T F5B73B90 verbose 'vm:/vmfs/volumes/4c4850e4-0dcce710-28d9-00215a5d36b8/wdcsmdc2/wdcsmdc2.vmx' opID=task-internal-977-4429b01] Reset request received

In the /vmfs/volumes///vmware.log file of the affected virtual machine, you see entries similar to:

T: vmx| Vix: [104333 vmxCommands.c:392]: VMAutomation_Reset
T: vmx| Vix: [104333 vmxCommands.c:457]: VMAutomation_Reset. Trying hard reset
T: vmx|
T: vmx|
T: vmx| VMXRequestReset
T: vmx| Stopping VCPU threads...

Note: Knowing the time of the unexpected reboot helps in searching the log files, as you can look for the time stamp.

If any of the relevant log entries or the vCenter Server event are present, HA Virtual Machine Monitoring restarted the virtual machine as it was not receiving virtual machine heartbeats (via VMware Tools) and there was no I/O on the virtual machine.

Examine the logs within the guest operating system to help determine the cause of the event. If multiple virtual machines are affected, review the vmkernel, messages, and hostd logs on the ESX host where the virtual machines are registered to look for a system wide problem.
To workaround this issue, disable Virtual Machine Monitoring:

Log in to the vCenter Server using the vSphere Client.

Right-click on VMware HA Cluster and select Edit Settings

In the Cluster Settings dialog box, Select VM Monitoring

VM Monitoring Status: VM Monitoring drop down box, select Disabled

Click OK

Note: This feature can also be disabled on the VMware HA page of the New Cluster Wizard by deselecting Enable Host Monitoring.

Related Information

For more information about Virtual Machine Monitoring, see the vSphere Availability Guide for ESX 4.0.

For more information about a Guest OS Crash, see Verifying if software is causing your virtual machine to fail (1003999).
确定 High Availability 虚拟机监控事件是否导致虚拟机重新引导
仮想マシンの再起動の原因が High Availability の仮想マシンの監視イベントであるかどうかを判断する

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

VMware ESX Server

Related Versions:

Take Our Survey

Support Assistant