vmotion fails with no meaningful err msg

[shanekennedy]

help me to understand how to start troubleshooting this issue.  other vm's vmotion without issue to all servers in the cluster.

This email is to notify you that an alarm has been triggered in your vCenter:
Alarm alarm.MigrationErrorAlarm on VM win2019.ad
because Cannot migrate win2019.ad from esx06, FC-PureFlash-VVol in Datacenter1 to esx07, FC-PureFlash-VVol in Datacenter1

# from vsphere events list:

Description:

Alarm 'Migration error' on win2019.ad triggered by event 3161670 'Cannot migrate win2019.ad from esx06, FC-PureFlash-VVol in Datacenter1 to esx07, FC-PureFlash-VVol in Datacenter1'

Related events:

There are no related events.

[Brisk]

There's a number of things that could cause this issue. If I understand correctly, other VMs from that host can vMotion to other nodes in the cluster without issues?

Has this VM been able to vMotion in the past? Is the VM located on shared storage that other hosts can access? You're sure that there's no local device mapped to the VM? Is there an ISO connected to the VM that is only reachable from that specific host?

[shanekennedy]

thank you for your response

other vm's do vmotion w/o issue

i don't recall needing to vmotion this troubled vm in the past

the vm is located on a vvol same as all other vm's in this cluster

cd/dvd is mapped to non-existent client-device & is not connected 

vmotion compatibility checks always succeed

[shanekennedy]

issue resolved by rebooting vm

don't understand why