Cross vCenter Migration of Encrypted VM Fails with Error "The request refers to an unexpected or unknown type"

Products

• VMware vCenter Server

Issue/Introduction

• A cross vCenter migration (vMotion) of an encrypted Virtual Machine from an old vCenter to a new vCenter fails.

• The failure occurs with the following error message displayed in the vSphere Client:

"The request refers to an unexpected or unknown type."

• From var/log/vmware/vpxd/vpxd.log We could see XVC failing due unknow type

YYYY-MM-DDT15:22:26.831+11:00 error vpxd[112479] [Originator@6876_sub=VmProv opID=mhx4a79a-1416565-auto-ud12-h5:70077414-67-01] xVC Migrate failed atvpx. vmprov. InvokePrechecks for poweredOff VM <VM_Name> (vm-#######, in pool resgroup-####### with ds ds:///vmfs/volumes/ to (DstLocation null) with migId 2254008622302605431 with fault vmodl.fault. InvalidType:
YYYY-MM-DDT15:22:26.838+11:00 error vpxd[112479] [Originator@6876 sub=vpxLro opID=mhx4a79a-1416565-auto-ud12-h5:70077414-67-01] [VpxLRO] Unexpected Exception: N5Vmomi5Fault11InvalidType9ExceptionE(Fault cause: vmodl. fault. InvalidType
-- > )
-- > [context]zKq7AVECAQAAACNbfAEfdnB4ZAAAwuo3bGlidm1hY29yZS5zbwAAWYosANd9LQDf+jIBa5gYbGlidm1vbWkuc28AARN0DAK3X3N2cHhkAIJj+GkBgvZ7NQGCIrw1AYJbwjUBgqUAagGC5gFqAYIUEWoBgnc+aQGCRpdpAYJJDDQBAoeQ/QK6kf2DWfgFAWxpYnZpbS10eXB1cy5zbwCCqv1qAYK1AGoBguYBagGCFBFqAYJ3PmkBgkLoaQEAp1ojADWwIwCAdjcEh38AbGlicHRocmVhZC5zby4wAAX/Nw9saWJjLnNvLjYA[/context]
YYYY-MM-DDT15:22:26.842+11:00 info vpxd[112479] [Originator@6876 sub=vpxLro opID=mhx4a79a-1416565-auto-ud12-h5:70077414-67-01] [VpxLRO] -- FINISH lro-54230315
YYYY-MM-DDT15:22:26.843+11:00 info vpxd[112479] [Originator@6876 sub=Default opID=mhx4a79a-1416565-auto-ud12-h5:70077414-67-01] [VpxLRO] -- ERROR lro-54230315 -- vm-####### -- vim.VirtualMachine.relocate: vmodl.fault. InvalidType:
-- > Result:
-- > (vmodl. fault.InvalidType) {
faultCause = (vmodl.MethodFault) null,
faultMessage = <unset>,
argument = "ManagedObjectReference"
msg = "The request refers to an unexpected or unknown type."

.- >

Environment

vCenter Server 7.x

vCenter Server 8.x

Cause

The issue is caused by an incompatibility or conflict between Storage DRS (Datastore Cluster) and the cross vCenter vMotion process, particularly when dealing with encrypted VMs.

When the VM resides on a Datastore Cluster where Storage DRS is enabled, the cross vCenter migration operation encounters an object type mismatch, which results in an InvalidType exception. Storage or Datastore Clusters are not supported for the storage selection when performing a cross vCenter migration.

Resolution

To successfully perform the cross vCenter migration, you must temporarily disable Storage DRS for the specific Virtual Machine during the migration process.

Steps to Resolve:

1. Open the vSphere Client and navigate to the Virtual Machine you intend to migrate.

2. Right-click the virtual machine and select Migrate.

3. In the vMotion wizard, select your desired migration type and destination vCenter/Host.

4. When you reach the Select storage step: a. Locate and expand the Advanced options section. b. Check the box labeled "Disable Storage DRS for this virtual machine".

5. Complete the remaining steps in the migration wizard.

6. Verify the migration completes successfully.