VMware Cloud Community
JedB
Contributor
Contributor

Cluster Error: vMotion not supported by host

Hi!

I have a strange error:

When I try to vmotion a running VM from one cluster to another (Compute and Storage vMotion) the following errors are displayed:

The "Destination" host 'hostname' does not support vMotion.

com.vmware.vim.vpxd.vmcheck.vmotionNotSupportedByHost

The "Source" host 'hostname' does not support vMotion.

com.vmware.vim.vpxd.vmcheck.vmotionNotSupportedByHost

If the VM is powered off, it can be migrated.

Between the hosts of a cluster, a live migration is working well.

I'm sure that I have migrated VMs in the past sucessfully. The only thing I have done in the past was the update from VCSA 5.5 U3b to VCSA 6.0 U3.

I have tried all the suggestions from KB1003734 but nothing seems to be wrong. VMotion and DRS work perfectly, only to another cluster fails.

Understanding and troubleshooting vMotion (1003734) | VMware KB

Does anyone has an idea?

Otherwise I will have to open an official support request.

0 Kudos
6 Replies
JedB
Contributor
Contributor

Some words to the environment:

vSphere web client: Version 6.0.0 Build 5112533

Most ESXi servers: VMware ESXi, 5.5.0, 4345813

One new ESXi cluster with two hosts: VMware ESXi, 6.0.0, 5224934 (this host only reports one error, destination or source, depending on the vmotion direction)

Maybe this is a ESXi version confict?

0 Kudos
mallikarjun31
Contributor
Contributor

How are you going to migrate.. It means you connected Vcenter server through Vsphere client.. If yes, then it won't support both .. I would suggest you to perform this via Vsphere web client.

0 Kudos
JedB
Contributor
Contributor

Hi!
I am using the vSphere Web Client and when the Migration tool checks source and destination, I am getting this error. The vMotion isn't started!

0 Kudos
arunjkum
Contributor
Contributor

Im facing similar issue.  Did anyone got a solution for this issue

0 Kudos
szafa
Enthusiast
Enthusiast

Hi All

Sounds like you are trying Cross vSwitch vMotion? If this is the case it was introduced in vSphere 6.0 so update 5.5 host to 6.0 to fix that issue.

https://kb.vmware.com/s/article/2109507

Next question is if you have same EVC in both clusters?

0 Kudos
arunjkum
Contributor
Contributor

  • The EVC is of the same version on the both the clusters
  • Im doing a vmotion from a standard switch to a standard switch
  • The source cluster is 5.5 & the target cluster is 6.0
  • Both the clusters are configured as two different DCs
0 Kudos