In some situations when using veeam or doing manual vmotion migrations, it can happen that the migration gets stuck.
Usually this state occurs when the source esxi and destination esxi are having some kind of communication issue. The fix is the following:
- Start SSH on both source and destination ESXi.
- restart vxpa and hostd on the destination machine:
/etc/init.d/hostd restart /etc/init.d/vpxa restart
If the process continues or errors you are done, if not,
- restart vxpa and hostd on the source machine:
The process will probably error now, but the machine is working again, and can be moved again.