HCX OSAM - RHEL8.10 & 9.x fails during fix up with error "A specified parameter was not correct: fileType"

Products

• VMware HCX

Issue/Introduction

• OSAM migrations failing for RHEL 8.10 and 9.x KVM VMs hosted in OpenStack, during the fix-up phase with a "A specified parameter was not correct: fileType" error.
  
  
• The failure is during fix-up stage with error
  
  ERROR c.v.v.h.s.m.h.OsAssistedMigrationUtil- Task Failed. {"fault":{"@xsi:type":"InvalidArgument","invalidProperty":"fileType"},"localizedMessage":"A specified parameter was not correct: fileType"}
  
  
  
  
• app.log at /common/logs/admin from HCX Manager shows following error
  
  2026-01-25 06:31:09.022 UTC [OsAssistedMigrationService_SvcThread-371, Ent: HybridityAdmin, , TxId: ########-####-####-####-#######] ERROR c.v.v.h.s.m.h.OsAssistedMigrationUtil- Task Failed. {"fault":{"@xsi:type":"InvalidArgument","invalidProperty":"fileType"},"localizedMessage":"A specified parameter was not correct: fileType"}
2026-01-25 06:31:09.039 UTC [OsAssistedMigrationService_SvcThread-371, Ent: HybridityAdmin, , TxId: ########-####-####-####-#######] ERROR c.v.v.h.s.m.jobs.LinuxFixupJob- Failed in executing subworkflow Linux Fixup - A specified parameter was not correct: fileType migrationId: ######-####-####-###-#########
2026-01-25 06:31:09.162 UTC [OsAssistedMigrationService_SvcThread-384, Ent: HybridityAdmin, , TxId: ########-####-####-####-#######] INFO  c.v.v.h.s.m.j.OsAssistedMigrationJob- ----- Job id : ######-####-####-####-######## Running state : PROCESS_FIXUP_TARGET_VM_RESULT migrationId : #####-####-####-###-######### -----
  
  
•  HCX detected a mix of supported XFS and unsupported FAT32 filesystems on the source VM

app.log at /common/logs/admin
  
  "partitioning":"MBR","logicalSectorSize":512,"physicalSectorSize":512}],"linuxStorage":{"mdArrays":[],"diskPaths":[{"diskPath":"/dev/vda","baseBlockdevId":"#####-####-#####-####-###########"}],"filesystems":[{"fsName":"/","fsSize":2530####,"fsType":"XFS",
  ----------
  ----------
  {"fsName":"/boot/efi","fsSize":204580,"fsType":"FAT32","fsUuid":"####-#####","fsUsage":4,"fsAttributes":[{"provider":"__system__","attributes":[{"attrName":"__DISTRO__","attrValue":"redhat"},{"attrName":"__MAJOR__","attrValue":"9"},{"attrName":"__MINOR__","attrValue":"5"}]}],"baseBlockdevId":""#####-####-#####-####-###########""}],"swapDevices":[],"volumeGroups":[],"logicalVolumes":[],"encryptedDevices":o perform fix-up operation on migrated VM. A specified parameter was not correct: fileType","result":{"error":"Failed to perform fix-up operation on migrated VM. A specified parameter was not correct: fileType"}}

Environment

VMware HCX

 

Cause

• Unsupported Filesystem: OSAM only supports ext2/3/4 and XFS. The presence of a FAT partition (or a FAT/XFS mix) causes a failure during the fix-up phase.

• Special Characters : The VM name contains unsupported special characters or spaces (e.g., @, #, $, %, *). 

Resolution

• Confirm the Guest OS is limited to supported types: ext2, ext3, ext4, or XFS. 
• To resolve the filesystem mismatch, back up any existing FAT32 partitions and recreate them using the ext4 format. Once the partitions are converted to a supported Linux filesystem, you may restart the HCX migration
• Remove any special characters (e.g., **@, #, $, %, ***) or spaces from the source VM name.

Additional Information

Guest Operating System Considerations for OSAM