HCX - OSAM failure: "Invalid Configuration for device"

Products

• VMware HCX

Issue/Introduction

Identify a known issue with invalid Windows GuestOS settings that will cause OSAM failure.

Symptoms:
HCX Operating System Assisted Migration (OSAM) will fail to instantiate the VM on the target vCenter.
The error in the HCX Cloud Manager's app.log will show:

2022-00-00 00:00:06.221 UTC [OsAssistedMigrationService_SvcThread-XXX, Ent: HybridityAdmin, , TxId: TxId: <id>] ERROR c.v.v.h.s.m.h.OsAssistedMigrationUtil- Task Failed. {"fault":{"@xsi:type":"InvalidDeviceSpec","property":"macAddress","deviceIndex":4},"localizedMessage":"Invalid configuration for device '4'."}

2022-00-00 00:00:06.436 UTC [OsAssistedMigrationService_SvcThread-XXX, Ent: HybridityAdmin, , TxId: TxId: <id>] ERROR c.v.v.h.s.migration.jobs.CreateVMJob- Failed in executing subworkflow Instantiate VM workflow - Invalid configuration for device '4'. migrationId: <id>

In a linux migration the migration can fail at the fix-up without a specific configuration called out. There will be no errors in the logs, and the fix-up file will not get created inside of HCX.

Cause

Under certain conditions, a Windows VM will not record a valid MAC address for an interface (NIC), which is required for OSAM. Some Network Backup solutions may create such interfaces.

Some file systems are not supported depending on the OS type of the guest machine. You will need to validate the configuration of the guest os to make sure it doesn't match any of the incompatible criteria.

Resolution

Remove the invalid NIC from the GuestOS prior to migrating the VM with OSAM.
If the vm is using an unsupported file system this will need to be removed or changed into a supported file system.

Workaround:
None.

Additional Information

Impact/Risks:
OSAM will fail for the VM.