Today we tried to do a storage VMotion. For some reason it failed with the message: "A general system error occurred: Failed waiting for data. Error bad0007. Bad Parameter."

When looking at the '/var/log/vmkernel' log we see:

cpu0:1092)Migrate: vm 1093: 7383: Setting migration info ts = 1266331952655810, src ip = <hidden-ip> dest ip = <hidden-ip> Dest wid = 1812 using SHARED swap
cpu0:1092)World: vm 1587: 901: Starting world migSendHelper-1093 with flags 1
cpu0:1092)World: vm 1588: 901: Starting world migRecvHelper-1093 with flags 1
cpu1:1587)WARNING: MigrateNet: 309: 1266331952655810: 5-0x8021d80:Sent only 4088 of 4096 bytes of message data: Broken pipe
cpu1:1587)WARNING: Migrate: 6820: 1266331952655810: Couldn't send data for 7: Broken pipe
cpu1:1587)WARNING: Migrate: 1243: 1266331952655810: Failed: Broken pipe (0xbad0052) @0x9d5d9f

vmkping worked fine (to it's own ip, but also to another hosts). ping worked fine. Enough free space (vdf -h), no strange things in esxtop. Also enough memory free in Service Console. Even checked the '.vmx' file - no strange things. Then I did something which is easy to do: disable VMotion option on the VMkernel interface, and then enabled it again. Whoohoo - it worked.

I don't know what could cause this, but at least now you now how to solve it.