I've discovered an inconsistent behavior with the V2V Converter CLI (version 772) when converting VMs with multiple disks from VMware ESXi to Hyper-V.
Problem Description:
When converting a VM with multiple disks using out_file_type=ft_vhdx_growable, the conversion creates inconsistent disk allocation types:
Boot disk (first disk): Created as thin/dynamic VHD
Additional disks (data disks): Created as thick/fixed VHDX
Test Results:
I've confirmed that single file conversions work correctly:
out_file_type=ft_vhdx_growable → Creates thin disk ✓
out_file_type=ft_vhdx_pre_allocated → Creates thick disk ✓
However, VM conversions (using in_vm_name=) show this mixed behavior.
Additional Observations:
- The boot disk is also created with different characteristics:
Data disks: VHDX format on SCSI controllers
- These are VMs running Windows server OS
- V2V converter is creating a VM with multiple disks on the Hyper-V node perfectly. It boots up just fine. The disks are in the correct order and have the correct drive letters too.
Questions:V2V_ConverterConsole.exe convert
in_host_type=esx
in_host_address=[ESXi_HOST]
in_host_username=root
in_host_password=[PASSWORD]
in_vm_name=[VM_NAME]
out_host_type=win
out_host_address=[HYPER-V_HOST]
out_vm_name=[VM_NAME]
out_vm_path=[PATH]
out_file_type=ft_vhdx_growable
- Is this the expected behavior for multi-disk VM conversions?
- Is there a parameter to ensure all disks follow the same allocation type?
I noticed from previous forum discussions that the CLI may have limitations with multi-disk scenarios, but the parameter documentation suggests out_file_type should apply to all converted disks. This inconsistency creates storage efficiency issues in our environment where we specifically need thin provisioning for all disks.
Any guidance would be appreciated.
Thanks,
Raj
PS: The documentation page may need to be corrected. The file types seem to be wrong/deprecated.
https://www.starwindsoftware.com/v2v-he ... rface.html