Hello
We have a strange behaviour in one of our vCenters (6.0 U3d on Windows 2012R2 server).
When manually starting a vMotion migration, the option "Change host" is greyed out with the mesage "vMotion is not enabled on the host of the Virtual Machine". But vMotion IS enabled on the host... and correctly configured... and licensed... and it works if DRS needs to do a migration!
My workaround is to disable vMotion on the host on the relevant VMKernel interface and enable it again, then it works for some hours or so... until it returns to the above error message.
Someone else described the exact same thing here (without solution, just the same workaround):
Information Sharing: Fixing the error "vMotion is not enabled on the host of the Virtual Machine"
- This happens on all (ca. 😎 clusters in the datacenter
- It affects all VMs on the host
- It only affects a host as "vMotion source" (migrating off the host), the same host works if it is the vMotion target 😉
- A host that was a "target" of a vMotion, suddenly also works for outgoing vMotions... :smileyconfused:
I might be wrong, but I vaguely link the problem to an incident where we accidentally exceeded the Hosts per Cluster Configuration Maximum (64 hosts). The cluster had 66 or 67 hosts before we split it in two clusters... (that Configration Maximum is not a hardcoded limit...! :smileyangry:).
Now I just tried it with the HTML5 Client (Fling) and the phenomenon is not present there! So it's a vSphere Client (C#) only problem? :smileyangry:
