DRS initiated vMotion shows error even when migration is successful

Products

• VMware vSphere ESXi

Issue/Introduction

During DRS operation you get following error 

"Alarm 'Migration error' on #### triggered by event ##### 'Cannot migrate ##### from ESXI-FQDN,Cluster-Name in ### to ESXI-FQDN, Cluster-Name in ###'"

 

In VPXD logs on vCenter you see this error

(in below example you can follow same opID trough all logs "opID=m7g6jaiy-5321720-auto-3629l-h5")

 

error vpxd[07217] [Originator@6876 sub=VmProv opID=m7g6jaiy-5321720-auto-3629l-h5:70338057-2-02-13-01] Local-VC Host Migrate failed at vpx.vmprov.InitiateSource 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 4837023606750812997 with fault vim.fault.GenericVmConfigFault:  as Operation: Local-VC_DRS_MM_ComputevMotion

 

In ESXi logs you see successful migration

Source host logs 
hostd.log

 In(166) Hostd[2099780]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/####/####/####.vmx opID=m7g6jaiy-5321720-auto-3629l-h5:70338057-2-02-13-01-ba-befd sid=52dce872 user=vpxuser:<no user>] State Transition (VM_STATE_ON -> VM_STATE_EMIGRATING)

Target host logs 

hostd.log
In(166) Hostd[2099687] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=m7g6jaiy-5321720-auto-3629l-h5:70338057-2-02-13-01-e0-daae sid=521d81a3 user=vpxuser:<no user>] Event 63409 : Registered #### on #### in ha-datacenter

 

In FDM logs on source host we see this 

 

Fdm[2102563]: [Originator@6876 sub=Cluster opID=WorkQueue-70f09325] Duplicate VM lock owner identified; path: /vmfs/volumes/####/###/####.vmx.lck, owner: host-###

 

Environment

vSphere 8.x

Cause

Instead of the vMotion stack destroying the VMX, HA interrupted it and killed the VMX because it deemed it duplicate. This HA action was unwarranted, the vMotion task shows as error, but there is no impact on VM.

This is rare scenario when HA interact with vMotion and doesn't happen every time when vMotion in progress.

 

Resolution

Currently there is no resolution or impact on virtual machines.