Migration initiated by the vMotion API fails shortly after destination ESXi host is rebooted and connected to vCenter Server

Products

• VMware vSphere ESXi

Issue/Introduction

vMotion fails with the error vim.fault.InvalidState under the following conditions:

• vMotion is initiated by vMotion API
• vMotion is attempted immediately after destination host is rebooted and connected to vCenter Server
• vpxd.log shows following vim.fault.InvalidState fault for the operation Local-VC_NonDRS_ComputevMotion

YYYY-MM-DDTHH:MM:SS.###+##:## error vpxd[07388] [Originator@6876 sub=VmProv opID=########-#####-auto-###-h5:########-##-##] Local-VC Host Migrate failed at vpx.vmprov.InvokeCallbacks for poweredOn VM '########' (vm-######, ds:///vmfs/volumes/########-########-####-############/########/########.vmx) on host-##### (###.###.###.###) in pool resgroup-##### with ds ds:///vmfs/volumes/########-########-####-############/ to host-###### (###.###.###.###) in pool resgroup-##### with ds ds:///vmfs/volumes/########-########-####-############/ with migId ################### with fault vim.fault.InvalidState:  as Operation: Local-VC_NonDRS_ComputevMotion

Environment

VMware vCenter Server 7.x

VMware vCenter Server 8.x

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

vMotion fails with fault vim.fault.InvalidState because destination host is NOT ready for vMotion though it  is connected to vCenter Server. 

Resolution

After destination host is connected to vCenter Server, allow 5-10 min to start vMotion.