error when converting hyper-v vm to VMWare

swejoos · Tue Apr 16, 2024 7:30 am

We get error when converting (offline) Hyper-v VMs with shared storage.

4/15 19:45:02.180 28f8 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
4/15 19:45:02.180 28f8 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.369
4/15 19:45:02.195 28f8 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
4/15 19:45:02.195 28f8 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
4/15 19:45:02.195 28f8 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 20348
4/15 19:45:02.195 28f8 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 82610000
4/15 19:45:02.195 28f8 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 82610000
4/15 19:45:07.711 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnection
4/15 19:45:55.805 28f8 Facility ???INFO: WrapperHyperV::connect: Host - \\hpv01\root\virtualization\v2
4/15 19:45:55.993 28f8 Facility ???INFO: WrapperHyperV::connect: user: FABRIC\Admin
4/15 19:45:56.024 28f8 Facility ???INFO: WrapperHyperV::connectToCIMV2: user: FABRIC\Admin
4/15 19:45:56.040 28f8 Facility ???INFO: WrapperHyperV::init_version: HyperV version: 10.0.17763
4/15 19:45:56.040 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputVM
4/15 19:46:11.649 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
4/15 19:46:17.228 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsAWS
4/15 19:46:49.384 28f8 Facility ???INFO: WrapperESXI::connect: m_url - https://
4/15 19:46:49.415 28f8 Facility ???INFO: WrapperESXI::connect: fullName - Jonas , key -
4/15 19:46:49.415 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnectionTo
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:46:49.899 28f8 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 8.0.2
4/15 19:47:17.134 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eOptionsESXI
4/15 19:47:26.056 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVolumeSelectVM
4/15 19:47:29.566 28f8 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnectionTo
4/15 19:47:29.581 1650 Facility ???INFO: CPPConverting::Convert: InConvertType: 7, OutConvertType: 5
4/15 19:47:29.581 1650 Facility ???INFO: CPPConverting::ConvertDisks: pathInput: C:\ClusterStorage\csv022\test-db-shareddisks\testdb_data1.vhds, pathOutput: [ESX DC1-CLUSTER1 DISK2] 2133/testdb_data1.vmdk
4/15 19:47:29.587 1650 Facility ???WARNING: HyperVDisk::CreateInputImage: Extension - C:\ClusterStorage\csv022\test-db-shareddisks\testdb_data1.vhds
4/15 19:47:29.587 1650 Facility ???INFO: CPPConverting::ConvertDisks: CreateInputImage: 7
4/15 19:47:29.587 1650 Facility ???ERROR: CPPConverting::Convert: FAILED
4/15 19:47:41.267 1d00 Facility ???INFO: VMConverter::ESXIConverter::Connection::<lambda_8874940e4602bbfc5e7b4b277e23eb86>::operator (): No_timeout ESX connection

bartolomeo · Tue Nov 26, 2024 6:53 pm

It seems like this is a known bug in this version. For now a workaround is manually renaming the disks after conversion to ensure no duplicates occur. Alternatively you could try converting the disks one at a time and verifying the naming during each step.