Hi There,
We've always had working vMotion in our cluster and suddenly it stopped working.
There is supposed to be a reason for that, but we just seem can't find it.
What happens is as follows: some machines cannot be vMotioned. Cold migration works always..
All ESXI hosts are in the same cluster. Logs do not provide any details. The error message is just generic:
"Timed out waiting for migration start request. The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct."
Here is what we've checked:
1. All settings: (kernel / IPs / switches, jumbo frames)
2. We checked all logs and there is nothing there that would indicate why migration fails.
3. We turned VAAI off and tested Vmotion
For some reason some VMs can be vMotioned and some cannot. All windows 7 VDI machines vMotion across hosts with no problem. However majority of VMs with Windows 2008 R2 or windows 2012 cannot be vMOtioned.This is something new.
Any ideas / suggestions are appreciated.
Thank you