What you may check is whether the VM for which the alarm was triggered has VMware Tools installed (i.e. VM heartbeat is working) and/or whether the VM stops responding (e.g. BSOD in case of Windows, panic in case of Linux, Sleep Mode/Power Saving enabled in the VM, ...) for any reason.
André
Hi,
I have checked the vm , thats working fine and vmware tools also running . no problem related to vm , any other reason for that , expecting your valuable comments.
Maybe the VM's vmware.log as well as the host's log files (see e.g. http://kb.vmware.com/kb/1027734) contain information!?
André
We had also enabled this parameter in our environment and we started getting too many alerts however the vm's were just fine.
We then disabled it
any slight change in the vm can trigger it. Not necessary the vm has to be down. This is just a warning.
Enable the error setting and talk/discuss to colleagues to disable it