The reason could be high network/IO intensive operations are going on your VC VM . When we trigger vMotion, vMotion keeps the track of changed memory pages in order to be consistent at destination host. If amount of memory getting changed is very frequently & greater than the available network bandwidth. vMotion will not get enough bandwidth to copy the changed memory pages at the destination host. Hence, vMotion fails.
--------------------------------------------------------------------------------------------------------------------------------
Award points if you it is useful.
----------------------------------------------------------------
Thanks & Regards
Vikas, VCP70, MCTS on AD, SCJP6.0, VCF, vSphere with Tanzu specialist.
https://vThinkBeyondVM.com/about
-----------------------------------------------------------------
Disclaimer: Any views or opinions expressed here are strictly my own. I am solely responsible for all content published here. Content published here is not read, reviewed or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware.