“No guest OS heartbeats” when attempting vMotion

When attempting to vMotion a couple of my virtual machines I received the “No guest OS heartbeats” error with many of them. Googling resulted in a number of possible reasons like

  • ensure that the VMware Tools are installed in the virtual machine before performing a migration
  • ensure that the virtual machine has been running long enough for the operating system to be completely started before performing a migration
  • if VMware Tools are already installed, reinstall the VMware Tools to ensure that you are on the latest version and that there is no corruption in the configuration

but I just could not beleave this was going on all my VMs.

Then I found out this was related to a recent reboot of my vCenter server and there are a number of fixes:

  1. Just ignore the warning, vMotion will run just fine and the warning behavior will disappear at some point
  2. Quickly open the console view of the virtual machine
  3. Restart the vmware tools services process(could be scripted if you have many)

One Response to “No guest OS heartbeats” when attempting vMotion

  1. Shelly says:

    Awesome! Its truly amazing article, I have got
    much clear idea regarding from this article.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: