I have heard back. According to my support person, the issue we are having is related to the default disabling of SSLv3 on 5.5 U3b. Engineering is aware of the issue. We downgraded to 5.5 U3a build 3316895 and all is well.
Still doesn't work for us, we tried downgrading a host but we still have the issue. Only workaround is to power the VM off and migrate it.
VMware state the issue has been raised to their engineering team and all we can do is wait So frustrating!
Here is the KB. We downgraded to 5.1 and will wait the fix out. Bad timing, we had 2500 VMs to move...
For me there was a workaround, I have used it at least on 5 different cluster, and worked every time.
For example, I had a 4 node cluster, 3 host was upgraded to 5.5u3b, one was still on 5.1
I reinstalled one host on 5.5 U2, then I upgraded it with patches till Sept. 2015. (Sept. patches should be included!) - this was my intermediate host. (build id: 3029944)
Edit: as I see 3029944 - was the simple 5.5u3 build.
Once this was completed, I could migrate all VM server from 5.1 to the intermediate host. Upgrade now the 5.1 to 5.5u3b
Once that was done, I could move everything from intermediate host to 5.5u3b, and upgrade the intermediate as well.
Was there a solution to this? I'm going from 5.1 to 5.5 (3248547) and have the same issues.
Migration to host <192.168.20.11> failed with error Already disconnected (195887150).
vMotion migration [-1407417943:1515664108242719] failed writing stream completion: Already disconnected
vMotion migration [-1407417943:1515664108242719] failed to flush stream buffer: Already disconnected
vMotion migration [-1407417943:1515664108242719] socket connected returned: Already disconnected