could you share the fdm.log from the host on which the VM got reset.
also the vmware.log of the VM.. a couple of files before reset.. coz once the vm resets a new vmware.log is created which has nothing about why the VM was hung..
If you have VM monitoring enabled there is no other reason why HA should reset the VM
Heartbeat from the guests is red..
2017-10-07T22:04:13.171Z verbose fdm[FFE3BB70] [Originator@6876 sub=Policy opID=SWI-58572bae] [LocalVmMonitoringPolicy::GetQSHeartbeatStatus] Guest heartbeat is lost (red). VM:/vmfs/volumes/57d8b7a8-a8672c62-f759-0cc47a655154/zjglxtht-21.1.1.15/zjglxtht-21.1.1.15.vmx
2017-10-07T22:04:33.172Z verbose fdm[FFDB9B70] [Originator@6876 sub=Policy opID=SWI-6fdc2f95] [VmPendingWorkVisitor::Visit(MonitorHeartbeatState)] red heartbeat detected. Need to recheck
2017-10-07T22:04:33.212Z verbose fdm[FFBB2B70] [Originator@6876 sub=Policy] [VmPendingWorkVisitor::Visit(MonitorHeartbeatState)] red heartbeat detected. Need to recheck
2017-10-07T22:04:36.213Z verbose fdm[FFE3BB70] [Originator@6876 sub=Policy] [MonitorHeartbeatState::MoveToResetStateIfTimersExpired] VM /vmfs/volumes/57d8b7a8-a8672c62-f759-0cc47a655154/zjglxtht-21.1.1.15/zjglxtht-21.1.1.15.vmx is going to reset state because failure timer expired. Reset no: 1 out of Max allowed reset count: 3
from the logs the vm looks to have gone unresponsive.
there should also be a .png file in the vm directory and it will capture if there was a BSOD.
I would suggest you to check guest events for the above mentioned timestamps to find the reason
I can see nothing but black on the picture
vm runs RHEL 6.2
i will check the os logs
thanks for you suggestion