Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 180329

vmware tools heartbeat failure: guest reset but should it have?

$
0
0

I have a linux guest vm that was reset early 1 morning because of the above HA message after coming out of a VDP backup snapshot but I was wondering if it should have been and what if anything I should do to make sure either my HA settings are appropriate for the cluster or vm or whether I need to make other changes to avoid the issue happening when least appropriate

 

Below are the events as listed on vSphere for the vm in question. It is very large and there could have been alot of guest disk i/o during the snap to consolidate

The guest doesn't appear to be showing any ill effects I'm just not sure why it was reset

 

TimeEvent  DescriptionTypeMy Notes
01:23:14 am Task Create virtual machine snapshotinfoWithin VDP backup window
05:31:49 amTask Remove snapshotinfo
06:22:37 amvSphere HA cannot reset this virtual machinewarning
06:22:38 amAlarm vSphere HA virtual machine monitoring error changed from Gray to Redinfo
06.22:38 amAlarm vSphere HA virtual machine monitoring error on GUESTVM triggered an actioninfo
06.22:38 amAlarm vSphere HA virtual machine monitoring error an SNMP trap was sentinfoGUEST VM in DMZ and  on different vlan to vCenter or hosts
06.23:16 amvSphere HA cannot reset this virtual machinewarning
06.23.52 amVirtual machine disks consolidated successdedinfo
06.23.59 amMessage from ESXiHost: Install the VMware tools package inside this virutal machineinfovmware tools was already installed and matches host
06.23.59 amThis virtual machine reset by vSphere HA: VMware Tools heartbeat failure: A screen shot is saved in /datastore/vm/vm-1.pnginfoGuest OS was still running in the image, no screen of death
06.23.59 amAlarm vSphere HA virtual machine monitoring action changed from Green to Yellowinfo

 

Given HA & the vm are set up as follows

  • HA Cluster Settings:
    • cluster default vm restart priority: Medium
    • Guest restart priority: High
    • Datastore heartbeat: 2 datastores (1 hosting the guest vm the other hosting the vdp appliance)
  • VM Settings
    • Linux Guest
    • vmxnet 3 vNic connected to DMZ vlan
    • vm version 7:

 

There was some disk latency warnings before the backup snapshots were created but no loss of paths to either the guest vm datastore or the backup destination was reported

 

Am I right in thinking that HA shouldn't have been triggered due to the disk I/O from the consolidation of the snapshot even if it was taking a long time?


Viewing all articles
Browse latest Browse all 180329

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>