What steps should I follow to troubleshoot vMotion failures in vSphere 8.x

[tonybonde]

I am facing a vMotion issue in my vSphere 8.x environment. When I try to migrate a virtual machine between two ESXi hosts, the task fails during the migration process. The message shows “A general system error occurred: migration failed.” The virtual machine stays powered on, but the move never completes. Both hosts are on the same build and connected to the same shared datastore. Storage access looks fine, and the virtual machine files are visible from both hosts. The management network and vMotion network are configured on separate port groups. Ping tests between the hosts work without loss, so basic connectivity seems normal. I have already checked CPU and memory resources on the destination host. There is no shortage of capacity. Both hosts belong to the same cluster, and DRS is enabled. Still, the vMotion task keeps failing randomly.

 

In the logs, I see some timeout-related entries under hostd.log, but nothing specific that explains the failure. Sometimes the task runs for a few seconds before it stops, and other times it fails immediately.

To understand the problem better, I reviewed some VMware vSphere 8.x Professional  questions from Pass4Future. They helped me recall a few common misconfigurations, such as mismatched NIC settings and datastore access issues. I went through those points, but everything seems consistent in my setup. I have also tried restarting the management agents and re-enabling vMotion on both hosts, but the issue remains. I have not made any recent changes in the environment, so I am not sure where to look next.

 

If anyone in the community has seen this kind of behavior in vSphere 8.x, please share what else I can check. I want to narrow down the cause of these random vMotion failures and confirm whether it could be network-related or configuration-related.