P2V failing with physical to vmware

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
spabramenko
Posts: 1
Joined: Fri Mar 27, 2020 5:54 pm

Fri Mar 27, 2020 6:27 pm

When attempting to convert a windows 2016 server to esxi 6.5 i receive an error. The program shows that a snapshot was successful and the vmdk was successful, however it instantly fails on the conversion step. I receive a popup that says "error, retry or cancel". Retry just makes the box come back up over and over again. Here are the log files:

Code: Select all

The log file name: 'logs\V2V_Log-20200327-110604.log' (PID 572)
3/27 11:06:04.538 164c Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
3/27 11:06:04.538 164c Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.0.202
3/27 11:06:04.538 164c Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
3/27 11:06:04.538 164c Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_RUSSIAN
3/27 11:06:04.538 164c Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
3/27 11:06:04.538 164c Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 14393
3/27 11:06:04.538 164c Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 84bd0000
3/27 11:06:04.538 164c Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 84bd0000
3/27 11:06:07.898 164c Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eTypeP2V
3/27 11:06:11.679 164c Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVolumeSelectVM
3/27 11:06:19.054 164c Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
3/27 11:06:21.101 164c Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnectionTo
3/27 11:06:43.913 164c Facility ???INFO: WrapperESXI::connect: m_url - https://192.168.254.252/sdk
3/27 11:06:43.976 164c Facility ???INFO: WrapperESXI::connect: fullName - Administrator, key - 5236b163-2fe1-7b7c-0d87-9263c085103e
3/27 11:06:43.992 164c Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsESX
3/27 11:07:01.132 164c Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 6.7.0
3/27 11:07:01.179 164c Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
3/27 11:07:01.195 264c Facility ???INFO: CPPConverting::Convert: InConvertType: 3, OutConvertType: 6
3/27 11:07:01.195 264c Facility ???INFO: CheckFileESX::CheckFileExistance: /folder/ISO/MyPC/HDD0.vmdk?dcPath=ha-datacenter&dsName=Local-9TB-RAID5
3/27 11:07:01.242 264c Facility ???INFO: CheckFileESX::CheckFileExistance: state - 404
3/27 11:07:01.242 264c Facility ???INFO: CheckFileESX::CheckFileExistance: /folder/ISO/MyPC/HDD1.vmdk?dcPath=ha-datacenter&dsName=Local-9TB-RAID5
3/27 11:07:01.273 264c Facility ???INFO: CheckFileESX::CheckFileExistance: state - 404
3/27 11:07:01.476 264c Facility ???INFO: VMConverter::ESXIConverter::CreateVM: createVM is true, 15
3/27 11:07:01.476 264c Facility ???INFO: CPPConverting::ConverterESX: Create VM 15
3/27 11:07:01.601 264c Facility ???INFO: CPPConverting::ConvertImage: pathInput: 0, pathOutput: [Local-9TB-RAID5] ISO/MyPC/HDD0.vmdk
3/27 11:07:01.601 264c Facility ???INFO: P2V::CreateInputImage: path 0
3/27 11:07:01.601 264c Facility ???INFO: P2V::CreateInputImage: Size 0 - 214748364800, BytesPerSector - 4096
3/27 11:07:28.211 264c Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 0
3/27 11:07:28.273 264c Facility ???INFO: ESXVmdk::ParseFile: sFilename - [Local-9TB-RAID5] ISO/MyPC/HDD0.vmdk
3/27 11:07:28.273 264c Facility ???INFO: ESXVmdk::ParseFile: m_cSSLThumbprint - BF:86:9C:8E:DA:C0:88:86:5B:A9:B9:5C:47:06:B7:73:E2:8B:3E:DF
3/27 11:07:28.273 264c Facility ???INFO: ESXVmdk::ParseFile: m_cvmxSpec - [Local-9TB-RAID5] ISO/MyPC/MyPC.vmx
3/27 11:07:28.945 264c Facility ???INFO: CPPConverting::ConvertImage: CreateOutputImage: 0
3/27 11:07:28.961 264c Facility ???INFO: P2V::getSectorsNext: countClusters - 14416, dwCountBytes - 14416
3/27 11:07:29.070 264c Facility ???WARNING: P2V::getBuffer: ReadFile - 998. Invalid access to memory location.
3/27 11:07:29.070 264c Facility ???ERROR: CPPConverting::ConvertImage: Read 3
3/27 11:07:51.680 264c Facility ???ERROR: CPPConverting::Convert: FAILED
yaroslav (staff)
Staff
Posts: 2277
Joined: Mon Nov 18, 2019 11:11 am

Mon Mar 30, 2020 12:14 pm

Greetings,

R&D team is looking into the logs. We'll keep you posted.
yaroslav (staff)
Staff
Posts: 2277
Joined: Mon Nov 18, 2019 11:11 am

Mon Mar 30, 2020 12:28 pm

I'd like to draw your attention to this line

Code: Select all

Size 0 - 214748364800, BytesPerSector - 4096
This means that disk sector size is 4K. Unfortunately, V2V Converter supports only 512 B sector size.
4K sector size support is going to be introduced in the upcoming release.
Stay tuned!
asavchenko
Posts: 11
Joined: Fri Mar 11, 2022 4:18 pm

Tue Sep 27, 2022 7:00 pm

Same error
When come 4K sector size support?
yaroslav (staff)
Staff
Posts: 2277
Joined: Mon Nov 18, 2019 11:11 am

Sun Oct 02, 2022 10:28 pm

The feature is on the road map. Please stay tuned.
Post Reply