To look for events related to the virtual machine in vCenter Server:
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
/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
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: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 虚拟机监控事件是否导致虚拟机重新引导