HCX OSAM migration is failing with error "Failed to perform fix-up operation on migrated VM. File Upload is unsuccessful" due to a partition with invalid characters.

Products

• VMware HCX

Issue/Introduction

• In /common/logs/admin/app.log file of the HCX Cloud Manager, you can see the following error followed by a full JSON object that contains information about the VM configuration:
  

  <Timestamp> [OsAssistedMigrationService_SvcThread-345, Ent: HybridityAdmin, , TxId: ########-####-####-####-############] ERROR c.v.v.h.s.m.jobs.WindowsFixupJob- doLoadSystemConfiguration() failed to load system configuration in 300000 ms - File Upload is unsuccessful guestInfo: <Large JSON OBJECT>
  
   <Timestamp> [OsAssistedMigrationService_SvcThread-334, Ent: HybridityAdmin, , TxId:########-####-####-####-############] ERROR c.v.v.h.s.m.j.OsAssistedMigrationJob- Failed to perform fix-up operation on migrated VM with jobData <Large JSON OBJECT with details of VM configuration>

• In the <Large JSON OBJECT with details of VM configuration> of the above error you see some unknown characters on the name of virtual devices, like an example of the following disk partition name:
  

                    {
                       "endingLBA":1286143,
                       "attributes":"0x8000000000000000",
                       "blockdevId":"################################\\2",
                       "partNumber":2,
                       "startingLBA":264192,
                       "partitionName":"Basic data partitionM��^?@\u0005��g\u0001��\u0004�g\u0001v\u0012�\u0005�<",
                       "partitionTypeGUID":"########-####-####-####-############",
                       "uniquePartitionGUID":"########-####-####-####-############"
                    },

  
  In general, as per General Operating System Considerations "Guest virtual machines with the locale and the UI language other than English US are not supported." and above looks like the characters used are not from English US Language.
  
  
• You have confirmed that current Locale in the Windows OS is English US: Go to Control Panel -> Language
• You have confirmed that current Language for non-Unicode programs is English US:  Go to Control Panel -> Clock, Language, and Region -> Administrative -> Language for non-Unicode programs
• The source VM is configured with multiple system partitions: Open Commnad Prompt -> type diskpart -> then type list volumes
  
  
  
  
• In C:/ProgramData/VMware/HCX/fixup.log file of the destination VM, you can see the following messages keep repeating:
  

  INFO Rebooting VM as fixup stage not complete
  INFO Progress file opened successfully
  INFO Viware tools is already installed
  Fixup result file: C:\temp\fixup\result.json does not exist
  Verify failed for second stage fixup
  INFO File: C:\temp\fixup\BEGIN not found. Retrying after 10 seconds ...
  INFO File: C:\temp\fixup\BEGIN not found. Retrying after 10 seconds ...
  INFO File: C:\temp\fixup\BEGIN not found. Retrying after 10 seconds ...

 

 

Resolution

Please engage Guest OS vendor to troubleshoot why there are two system partitions or why one of the partitions name has non English US characters.

Additional Information

HCX OSAM Migration Failure: “BEGIN not found” During Windows Stage-2 Fixup

HCX - OSAM - Failed to perform fix-up operation on migrated VM. Failed to prepare for Fixup -- Unable to login with vmuser