Migration from Hyper-V to vCenter / ESX fails

frederich · Mon Jul 01, 2024 2:46 pm

Hi,
I am trying to migrate a VM (shut down) from Hyper-V (Server 2022) to vCenter.
Version 9.0.1.509
Source: Hyper-V VM (OS Type: Windows)
Destination: Remote vCenter (VXRail vSAN)

The log file name: 'logs\V2V_Log-20240701-163609.log' (PID 11444)
Delete log file 'logs\V2V_Log-20240701-124308.log'.
7/1 16:36:09.655 4810 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
7/1 16:36:09.656 4810 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.509
7/1 16:36:09.660 4810 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
7/1 16:36:09.660 4810 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
7/1 16:36:09.665 4810 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 20348
7/1 16:36:09.668 4810 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 1b9f0000
7/1 16:36:09.668 4810 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 1b9f0000
7/1 16:36:23.843 4810 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnection
7/1 16:36:28.731 4810 Facility ???INFO: WrapperHyperV::connect: Host - \\localhost\root\virtualization\v2
7/1 16:36:28.778 4810 Facility ???INFO: WrapperHyperV::init_version: HyperV version: 10.0.20348
7/1 16:36:28.778 4810 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputVM
7/1 16:36:36.360 4810 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
7/1 16:36:53.918 4810 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnectionTo
7/1 16:37:26.090 4810 Facility ???INFO: WrapperESXI::connect: m_url - https://10.10.201.3/sdk
7/1 16:37:26.261 4810 Facility ???INFO: WrapperESXI::connect: fullName - , key - 52ace95e-d6bd-e9b2-f0e2-4cad919915cd
7/1 16:37:26.261 4810 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsESX
7/1 16:37:26.636 4810 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
7/1 16:37:26.636 4810 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
7/1 16:37:26.636 4810 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
7/1 16:37:26.636 4810 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
7/1 16:37:51.053 4810 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
7/1 16:37:51.058 5e3c Facility ???INFO: CPPConverting::Convert: InConvertType: 8, OutConvertType: 6
7/1 16:37:51.437 5e3c Facility ???INFO: CheckFileESX::CheckFileExistance: GetBrowser fail - File [vSAN-DCS] AMALANSWEEPER was not found
7/1 16:37:51.612 5e3c Facility ???INFO: WrapperESXI::Wait: Progress - 5
7/1 16:37:51.631 5e3c Facility ???INFO: WrapperESXI::Wait: Progress - 6
7/1 16:37:51.783 5e3c Facility ???INFO: WrapperESXI::Wait: Progress - 10
7/1 16:37:51.803 5e3c Facility ???INFO: WrapperESXI::Wait: Progress - 15
7/1 16:37:51.822 5e3c Facility ???INFO: WrapperESXI::Wait: Progress - 25
7/1 16:37:51.903 5e3c Facility ???INFO: WrapperESXI::Wait: Progress - 99
7/1 16:37:52.150 5e3c Facility ???INFO: VMConverter::ESXIConverter::CreateVM: createVM is true, vm-867815
7/1 16:37:52.150 5e3c Facility ???INFO: CPPConverting::ConverterESX: Create VM vm-867815
7/1 16:37:59.527 5e3c Facility ???INFO: CPPConverting::ConvertDisks: pathInput: C:\ClusterStorage\Volume1\AMALANSWEEPER\Virtual Hard Disks\AMALANSWEEPER.vhdx, pathOutput: [vSAN-DCS] AMALANSWEEPER/AMALANSWEEPER.vmdk
7/1 16:37:59.673 5e3c Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 1.
7/1 16:37:59.673 5e3c Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 2.
7/1 16:37:59.673 5e3c Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 1.
7/1 16:37:59.673 5e3c Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 2.
7/1 16:37:59.674 5e3c Facility ???INFO: CVHDXFile::ParseFile: Log is empty.
7/1 16:37:59.674 5e3c Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
7/1 16:37:59.674 5e3c Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
7/1 16:37:59.674 5e3c Facility ???INFO: CPPConverting::ConvertDisks: CreateInputImage: 0
7/1 16:37:59.764 5e3c Facility ???INFO: ESXVmdk::ParseFile: sFilename - [vSAN-DCS] AMALANSWEEPER/AMALANSWEEPER.vmdk
7/1 16:37:59.764 5e3c Facility ???INFO: ESXVmdk::ParseFile: m_cvmxSpec - moref=vm-867815
7/1 16:37:59.820 5e3c Facility ???INFO: ESXVmdk::ParseFile: sslThumbprint - 9E:9B:85:19:45:62:C2:54:85:BA:F0:E2:F8:EF:32:55:BB:9A:88:90
7/1 16:38:00.343 5e3c Facility ???ERROR: ESXVmdk::ParseFile: m_VixDiskLib_Open is fail - 4, A file was not found
7/1 16:38:00.343 5e3c Facility ???ERROR: ESXIDisk::CreateOutputImage: ParseFile is fail
7/1 16:38:00.343 5e3c Facility ???INFO: CPPConverting::ConvertDisks: CreateOutputImage: 1
7/1 16:38:00.343 5e3c Facility ???ERROR: CPPConverting::Convert: FAILED
----

I found some posts suggesting, that vSAN is unsupported, is that why this error occurs? I also tried to convert a vhdx to vmdk (stream-optimizied), but it fails to upload to vCenter as well

Is there another way to get a Hyper-V VM migrated into vCenter on VXRail vSAN?

Thank you

asshley675 · Sat Jul 06, 2024 4:59 am

Hey there!
You should try using VMware vCenter Converter for a direct migration, or convert the VHDX to VMDK with a tool like StarWind V2V Converter, then upload it to the vSAN datastore and create a new VM. Alternatively, export the VM as an OVF/OVA from Hyper-V and import it into vCenter.

Sat Jul 06, 2024 6:22 am

Hi,

Try migrating the files locally or convert the VM to OVF (non-V2V Method).

frederich · Mon Jul 08, 2024 8:51 am

Thanks for the replies.

I tried converting the files locally from vhdx to vmdk, but I had no luck uploading them to vCenter. I am using the VMware vCenter Converter and it does work for direct migration to vSAN.

Mon Jul 08, 2024 9:24 am

On one hand, I am glad to read that you found the workaround on the other hand, I am sorry to read that you have stumbled into the auth provlems. You can import the files directly to the datastore using GUI and create the VM then using it.
Another workaround is converting the VM to OVA.