Cannot migrate powered on VM

[RX40]

On vSphere v7.0.3 I'm having an issue with migrating a powered on VM from one host to another, when its suspended it will migrate over fine. Other VM's migrate when powered on.

On vSphere I get an event error immediately after initiating the migration: (VM Name and IP addresses have been removed)

 Cannot migrate (VM_NAME) from 10.***.**.**, EMC_Datastore1 in Broadcast DC to 10.***.**.**, EMC_Datastore1 in Broadcast DC Error05/20/2022, 4:13:19 PM (VM_NAME)VSPHERE.LOCAL\Administratorvim.event.VmFailedMigrateEvent

Beginning of Expandable row content Screen reader table commands may not work for viewing expanded content, please use your screen reader's browse mode to read the content exposed by this button

Date Time:

 05/20/2022, 4:13:19 PM

Type:

 Error

User:

 VSPHERE.LOCAL\Administrator

Target:

(VM_NAME)

Description:

Cannot migrate (VM_NAME) from 10.***.**.**, EMC_Datastore1 in Broadcast_DC to 10.***.**.**, EMC_Datastore1 in Broadcast_DC

Event Type Description:

Failed to migrate the virtual machine for reasons described in the event message

Possible Causes:

• The virtual machine did not migrate. This condition can occur if vMotion IPs are not configured, the source and destination hosts are not accessible, and so on. Action: Check the reason in the event message to find the cause of the failure. Ensure that the vMotion IPs are configured on source and destination hosts, the hosts are accessible, and so on.

Related events:

Date Time Description

05/20/2022, 4:13:19 PM	Hot migrating VM_NAME from 10.***.**.**, EMC_Datastore1 in Broadcast DC to 10.***.**.**, EMC_Datastore1 in Broadcast DC with encryption
05/20/2022, 4:13:19 PM	Task: Relocate virtual machine

In the hostd.log I get this error:

2022-05-20T05:50:00.546Z info hostd[1050994] [Originator@6876 sub=Vcsvc.VMotionSrc.8655175433452394658 opID=l3cgeqc2-6445-auto-4z2-h5:70003116-1b-01-01-a3-3c41] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "msg.vigor.operationCancelled",
--> message = "The operation was cancelled by the user.",
--> }
--> ],
--> reason = "The operation was cancelled by the user.",
--> msg = "The operation was cancelled by the user.
--> "
--> }


In the vpxa.log I get this error:
2022-05-20T06:13:19.918Z info vpxa[1052518] [Originator@6876 sub=Default opID=l3cgeqc2-9929-auto-7nu-h5:70005470-cf-01-75] [VpxLRO] -- ERROR lro-23427 -- vmotionManager -- vim.host.VMotionManager.initiateDestination: vmodl.fault.SystemError:
--> Result:
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> reason = "Invalid fault"
--> msg = "Received SOAP response fault from [<<io_obj p:0x0000000d3757cb58, h:24, <TCP '127.0.0.1 : 61211'>, <TCP '127.0.0.1 : 8307'>>, /sdk>]: initiateDestination
--> vim.fault.GenericVmConfigFault"
--> }
--> Args:
-->
--> Arg migrationId:
--> 8655175434851822558
--> Arg dstConfigPath:
--> "ds:///vmfs/volumes/627b6499-0de5c79b-e216-0892049f83c4/VM_NAME/VM_NAME.vmx"

If anyone is able to assist resolve this issue it would be much appreciated. 

[Oscar Capon Mouriz]

Hi;

Verify that the VM does not have enabled Encrypted vMotion.

Enable or Disable Encrypted vMotion

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-E50591C6-30DB-4191-934E-A1E890C07FB1.html

vSphere vMotion always uses encryption when migrating encrypted virtual machines. For virtual machines that are not encrypted, you can select one of the encrypted vSphere vMotion options.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-6865D84A-C286-49C4-A4D4-D62145150242.html

I Hope that helps.

[Akin Akalan]

Can you please check if the vMotion enabled on both hosts?

 

[mbufkin]

Is this a new cluster? Have you been able to move this vm before? Can you vmotion other vms? What’s the EVC mode and is the vm encrypted?

[Oscar Capon Mouriz]

Hi  

Were you able to migrate?
Curiosity, what was the problem?

Thanks in advance.

[allan trambouze]

Did you set some policy on the VM that cannot comply with the migration (storage policy or encryption).

[zwy123]

Hello, have you solved this problem yet Is how to solve can you provide next train of thought

[jojo22]

Did you found a way to fix it? ...have similar issue too

[allan trambouze]

Verify that the virtual machine does not have orphaned or invalid snapshots, which can cause conflicts during vMotion. You can use the vim-cmd vmsvc/snapshot.get command to list existing snapshots, and the vim-cmd vmsvc/snapshot.remove command to delete them

Verify that the virtual machine does not have locked virtual disks, which can prevent vMotion from accessing files. You can use the vmkfstools -D command to identify locked disks, and the vmkvsitools lsof command to find the process that is locking them

Verify that the virtual machine does not have invalid advanced settings, which may interfere with vMotion. You can use the vSphere client to review and modify advanced virtual machine settings, or use the vim-cmd vmsvc/get.config command to view them on the command line4