Physical Win 2012 convert to Hyper-V 2019 fails

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

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

Post Reply
Molotov
Posts: 4
Joined: Wed Dec 11, 2019 10:10 am

Wed Dec 11, 2019 10:18 am

We're trying to convert a physical Windows Server 2012R2 machine to Hyper-V.

New VM is created on the Hyper-V 2019 server, snapshot is taken with success on the physical machine but the conversion fails with error message in the GUI:

Creating output image file
Error creating image
Convertation failed

This is the log:

The log file name: 'logs\V2V_Log-20191211-083431.log' (PID 12540)
12/11 8:34:31.217 3b64 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Image Converter\lib
12/11 8:34:31.229 3b64 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
12/11 8:34:31.232 3b64 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_RUSSIAN
12/11 8:34:31.232 3b64 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
12/11 8:34:31.234 3b64 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 6, MinorVersion 3, BuildNumber 9600
12/11 8:34:31.239 3b64 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 2d450000
12/11 8:34:31.241 3b64 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 2d450000
12/11 8:34:43.496 3b64 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eTypeP2V
12/11 8:34:47.279 3b64 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVolumeSelectVM
12/11 8:34:49.614 3b64 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
12/11 8:34:54.136 3b64 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnectionTo
12/11 8:35:22.385 3b64 Facility ???INFO: WrapperHyperV::connect: Host - \\VMHOST\root\virtualization\v2
12/11 8:35:24.695 3b64 Facility ???INFO: WrapperHyperV::connect: user: VMHOST\administrator
12/11 8:35:24.713 3b64 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettings
12/11 8:35:37.387 3b64 Facility ???INFO: WrapperHyperV::connectToCIMV2: user: VMHOST\administrator
12/11 8:35:48.320 3b64 Facility ???INFO: WrapperHyperV::connectToCIMV2: user: VMHOST\administrator
12/11 8:35:48.339 3b64 Facility ???INFO: VMConverter::HyperVConverter::GetHostListInfo: HyperV version: 10.0.17763
12/11 8:35:48.339 3b64 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
12/11 8:35:48.350 1f88 Facility ???INFO: CPPConverting::Convert: InConvertType: 3, OutConvertType: 8
12/11 8:35:48.508 1f88 Facility ???INFO: WrapperHyperV::modify_cpu_and_memory: MaxCPU - 4
12/11 8:35:48.528 1f88 Facility ???INFO: WrapperHyperV::getMaxMemory: MaxRAM - 14064
12/11 8:35:48.618 1f88 Facility ???INFO: VMConverter::HyperVConverter::CreateVM: add_ethernet_connection is 1
12/11 8:35:48.618 1f88 Facility ???INFO: CPPConverting::ConverterHyperV: Create VM 6C2D7D9E-0B82-4F26-8026-EA4440424D1A
12/11 8:35:48.629 1f88 Facility ???INFO: CPPConverting::ConvertImage: pathInput: 0, pathOutput: C:\VMHDD\ShaunV2\Virtual Hard Disks\HDD0.vhdx
12/11 8:35:48.629 1f88 Facility ???INFO: P2V::CreateInputImage: path 0
12/11 8:35:48.629 1f88 Facility ???INFO: P2V::CreateInputImage: Size 0 - 1999844147200, BytesPerSector - 512
12/11 8:38:13.057 1f88 Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 0
12/11 8:38:13.064 1f88 Facility ???INFO: MicrosoftFile::NewFile: sFilename - \\VMHOST\C$\VMHDD\ShaunV2\Virtual Hard Disks\HDD0.vhdx, nMaxSize - 3905945600, fileType - 1
12/11 8:38:13.087 1f88 Facility ???ERROR: MicrosoftFile::NewFile: CreateVirtualDisk is fail - -1069940716
12/11 8:38:13.088 1f88 Facility ???INFO: CPPConverting::ConvertImage: CreateOutputImage: 1
12/11 8:38:13.089 1f88 Facility ???ERROR: CPPConverting::Convert: FAILED

While going through the wizard we get to choose the location of the new VM files, credentials get accepted fine ... but somehow it cannot create the file. We cannot see where this goes wrong.

Rgds,
K
Molotov
Posts: 4
Joined: Wed Dec 11, 2019 10:10 am

Wed Dec 11, 2019 10:40 am

extra info, I tried converting using 2 methods:

- entire machine
- physical disk

both end with the same error: CreateVirtualDisk is fail - -1069940716
Molotov
Posts: 4
Joined: Wed Dec 11, 2019 10:10 am

Wed Dec 11, 2019 10:59 am

and to make things complete: I tried converting the physical disk to a local file on the Server 2012 R2 machine and this fails, too. Same error!

seems to be an issue on the physical side, not on the Hyper-V machine

I'm lost ...
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Wed Dec 11, 2019 3:25 pm

Hi. Sorry for delayed response.
It looks like vhdx disks are unsupported on Windows Server 2012R2 in your case, which is quite weird as they should! Just try P2V conversion to a vhd file and mount it to a Generation 1 VM afterward.
Molotov
Posts: 4
Joined: Wed Dec 11, 2019 10:10 am

Thu Dec 12, 2019 4:12 pm

i tried that but same error
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Fri Dec 13, 2019 9:28 am

I spoke to our R&D team on your problem.
Apparently, there is an issue with Windows Server 2012R2 libraries. StarWind V2V converter should work well on WS 2012R2. As a workaround, they are going to provide you with the custom build of the V2V Converter where conversion is done avoiding the libraries that they suspect to mess things up. Stay tuned!
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Fri Dec 13, 2019 10:17 am

Here is the custom build fit for your case. Any feedback is appreciated.
Attachments
StarV2V.9.0.0.Setup.183_.rar
(37.57 MiB) Downloaded 416 times
PC01
Posts: 1
Joined: Fri Apr 29, 2022 10:06 pm

Fri Apr 29, 2022 11:40 pm

In case it helps anyone else; had the same issue migrating to a non domain joined Server 2022 Hyper-V host. All I had to do was enable SMB1/CIFs on the target Hyper-V host, restart, do the migration, turn it back off, restart, everything working ok.

I did shut down the VMs on the host at the time of migration just as a precaution, but don't think this is really necessary.
clariceaupry
Posts: 1
Joined: Mon Aug 01, 2022 1:16 pm
Location: London, UK

Mon Aug 01, 2022 1:18 pm

PC01 wrote:In case it helps anyone else; had the same issue migrating to a non domain joined Server 2022 Hyper-V host. All I had to do was enable SMB1/CIFs on the target Hyper-V host, restart, do the migration, turn it back off, restart, everything working ok.

I did shut down the VMs on the host at the time of migration just as a precaution, but don't think this is really necessary.
Thanks, works for me well
yaroslav (staff)
Staff
Posts: 2279
Joined: Mon Nov 18, 2019 11:11 am

Mon Aug 01, 2022 1:47 pm

PC01 wrote:In case it helps anyone else; had the same issue migrating to a non domain joined Server 2022 Hyper-V host. All I had to do was enable SMB1/CIFs on the target Hyper-V host, restart, do the migration, turn it back off, restart, everything working ok.

I did shut down the VMs on the host at the time of migration just as a precaution, but don't think this is really necessary.
Thanks for your hint!
Post Reply