I found the solution by myself
you have to change the security settings of your virtual switch, to Accept Promiscuous Mode.
I don't think that is required, in fact, on our setup promiscuous mode is set to reject and VMotion works fine.
We also have our Gateway address set to a virtual[/i] one; there is no machine associated with it (it is unpingable). Though, from what I can tell fromt he documentation that shouldn't work but it does.
I had the same problem with VMotion on ESX 3.0 i.e. "A general system error occured: Timed out waiting for migration data."
I tried changing the Promiscuous Mode to "Accept" and VMotion worked (yippee!) but the joy was short lived and after a reboot of the ESX servers VMotion failed. Sometimes changing the Promiscuous Mode would work, other times it wouldn't. Very erratic.
I then tried removing from both ESX servers the virtual switch being used by VMotion, and then recreated them, following the usual advice:
- Using the same network label on each VMotion virtual switch
- Setting the gateway address for each VMotion virtual switch to the same e.g. 192.168.1.1
- Setting the VMotion IPs in the same subnet as the gateway but unique e.g. 192.168.1.2 on ESX1, 192.168.1.3 on ESX2.
- Left Promiscuous Mode at its default "Reject"
Result - working 100% now which is strange because the virtual switches were configured fine when it wasn't working.
Bottom line - try recreating the VMotion virtual switches if you have this error.
I have got the same problem, VMotion stopped working and got the same error. When I tried recreating the VMotion virtual switches, it did not resolve the problem.
After this I have restarted the 2 ESX3 hosts having the problem and VMotion began working.
While the problem is now fixed, it may recur later and not be resolved as we do not know the main cause.
Is this a bug which VMware is going to provide a fix for or someone knows some settings which would fix this problem?
I am getting the same problem again, any ideas?
That doesnt seem to affect ours..?
Probably an obvious question but is all your hardware on the HCL (especially your NICs)? If you are getting unreliable VMotion capability, IE: doesn't work, restart server, reconfigure switch, then it works for a while, then stops...could be hardware related. Also, check duplex settings are fixed at the same speeds on yr NICs and switches.