ESXi 5.x host becomes unresponsive during vMotion How to solve errors when a VMware vCenter vMotion migration or a configuration change fails

Suddenly somehow we got a virtual machine which couldn’t be powered on, or ESXi 5.x host becomes unresponsive after attempting to migrate a virtual machine from VMware vCenter Server or configuration change fails.

Symptoms

  • VMware ESXi 5.x host becomes unresponsive after attempting to migrate a virtual machine from VMware vCenter Server;
  • Making a configuration change to the ESXi host renders the host unresponsive;
  • Migration fails at 13%;
  • Some of the virtual machines in the inventory become invalid;
  • vpxa fails to start;
  • You are unable to power on a virtual machine.

Resolution

  • Connect to the ESXi host using SSH.
  • Check if SNMP is creating too many .trp files in the /var/spool/snmp directory on the ESXi host by running the command:
    ls /var/spool/snmp | wc -l

Note: If the output indicates that the value is 2000 or more, this may be causing the full inodes.

vmware result_ls root disk full, esxi, host, vmotion, snmp, trap, maintenance
vmware result_ls

To be sure check che disk root usage running this command

vdf -h
vmware disk root_usage
vmware disk root_usage

If the available space is less than 3-4Mb (or usage ‘USE’ over 90%), it could be a problem.

  • Delete the .trp files in the /var/spool/snmp/ directory by running the commands:

# cd /var/spool/snmp
# for i in $(ls | grep trp); do rm -f $i;done

CLEAN_TRP_SNMP results
CLEAN_TRP_SNMP results root disk full problems snmp

Related Articles: VMware KB | Wh33ly’s Blog

No Guest OS Heartbeats are being received error Troubleshooting Migration compatibility warning: No guest OS heartbeats are being received, from local or remotely

Symptoms
When performing a vMotion migration, this compatibility warning is displayed:

Migration from source_server: No guest OS heartbeats are being received. Either the guest OS is not responding or VMware tools is not configured properly.

No guest OS heartbeats are being received
No guest OS heartbeats are being received

Resolution

This warning indicates that the VMware Tools are either not installed or are not running in the virtual machine.

This message is safe to ignore when performing a migration.

Workaround
To workaround the warning, perform one of these options:

  1. Ensure that the VMware Tools are installed in the virtual machine before performing a migration;
  2. Ensure that the virtual machine has been running long enough for the operating system to be completely started before performing a migration.
  3. Restart the VMware Tools service.

For Linux virtual machine, open shell/terminal and run the command:

  • /etc/init.d/vmware-tools restart

or

  • /etc/vmware-tools/services.sh restart

or

  • service vmware-tools {start|stop|status|restart|force-reload}

For Windows virtual machine, frm RDP session or directly on machine:

  1. Click Start > Run, type services.msc, and press OK.
  2. Right-click VMware Tools Service and click Restart.

You can execute a remote restart of the “VMtools” service from remotely using SC command from command prompt:

sc.exe config “[servicename]” obj= “[.\username]” password= “[password]”

SC Syntax

DESCRIPTION:
 SC is a command line program used for communicating with the
 Service Control Manager and services.
USAGE:
 sc <server> [command] [service name] <option1> <option2>...

The option <server> has the form "\\ServerName"
 Further help on commands can be obtained by typing: "sc [command]"
 Commands:
 query-----------Queries the status for a service, or
 enumerates the status for types of services.
 queryex---------Queries the extended status for a service, or
 enumerates the status for types of services.
 start-----------Starts a service.
 pause-----------Sends a PAUSE control request to a service.
 interrogate-----Sends an INTERROGATE control request to a service.
 continue--------Sends a CONTINUE control request to a service.
 stop------------Sends a STOP request to a service.
 config----------Changes the configuration of a service (persistent).
 description-----Changes the description of a service.
 failure---------Changes the actions taken by a service upon failure.
 failureflag-----Changes the failure actions flag of a service.
 sidtype---------Changes the service SID type of a service.
 privs-----------Changes the required privileges of a service.
 qc--------------Queries the configuration information for a service.
 qdescription----Queries the description for a service.
 qfailure--------Queries the actions taken by a service upon failure.
 qfailureflag----Queries the failure actions flag of a service.
 qsidtype--------Queries the service SID type of a service.
 qprivs----------Queries the required privileges of a service.
 qtriggerinfo----Queries the trigger parameters of a service.
 qpreferrednode--Queries the preferred NUMA node of a service.
 delete----------Deletes a service (from the registry).
 create----------Creates a service. (adds it to the registry).
 control---------Sends a control to a service.
 sdshow----------Displays a service's security descriptor.
 sdset-----------Sets a service's security descriptor.
 showsid---------Displays the service SID string corresponding to an ar
bitrary name.
 triggerinfo-----Configures the trigger parameters of a service.
 preferrednode---Sets the preferred NUMA node of a service.
 GetDisplayName--Gets the DisplayName for a service.
 GetKeyName------Gets the ServiceKeyName for a service.
 EnumDepend------Enumerates Service Dependencies.

The following commands don't require a service name:
 sc <server> <command> <option>
 boot------------(ok | bad) Indicates whether the last boot should
 be saved as the last-known-good boot configuration
 Lock------------Locks the Service Database
 QueryLock-------Queries the LockStatus for the SCManager Database
EXAMPLE:
 sc start MyService

example:

(check status of the service)
sc \\you_server_name_or_ip query “vmtools”

(Stop the service)
sc \\you_server_name_or_ip query “vmtools”

(Start the Service)
sc \\you_server_name_or_ip query “vmtools”

From another server on the domain open a command prompt and type the following.
From another server on the domain open a command prompt and type the following.

Results

validation succeed
validation succeed

If your issue continues to exist, reinstall VMware Tools to ensure that you are on the latest version.