Page 1 of 1

Support for QCOW3

Posted: Mon Dec 02, 2019 2:48 pm
by nano94
I've tried to covert qcow to ESXi and got the message that qcow v3 is not supported...

Re: Support for QCOW3

Posted: Tue Dec 03, 2019 12:52 pm
by Boris (staff)
https://www.starwindsoftware.com/starwind-v2v-converter states the formats StarWind V2V supports, and it lists only QCOW2 as supported, but no QCOW3.

Re: Support for QCOW3

Posted: Wed Dec 11, 2019 10:02 pm
by nano94
My mistake, it is a qcow 2 file. But the converter still shows the QCOW3 error.

Image
Image

Re: Support for QCOW3

Posted: Thu Dec 12, 2019 8:59 am
by Boris (staff)
It would be great to have a look at the logs.

Re: Support for QCOW3

Posted: Thu Dec 12, 2019 6:59 pm
by nano94
Hi Boris,

attached you find the logs. The file is located on a network-share in case of the size.

Code: Select all

The log file name: 'logs\V2V_Log-20191202-153203.log' (PID 2832)
12/2 15:32:03.457 10d0 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Image Converter\lib
12/2 15:32:03.460 10d0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
12/2 15:32:03.461 10d0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_RUSSIAN
12/2 15:32:03.461 10d0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
12/2 15:32:03.461 10d0 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 6, MinorVersion 1, BuildNumber 7601
12/2 15:32:03.475 10d0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - f7aa0000
12/2 15:32:03.476 10d0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - f7aa0000
12/2 15:32:07.462 10d0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputFile
12/2 15:32:35.635 10d0 Facility ???INFO: CPPInputFile::checkFile: Select file: Z:\vm-100-disk-1.qcow2
12/2 15:32:35.703 10d0 Facility ???INFO: CPPInputFile::checkFile: ParseFile: 19

Re: Support for QCOW3

Posted: Mon Dec 16, 2019 12:50 pm
by Boris (staff)
Is this the whole output that you see there?

Re: Support for QCOW3

Posted: Mon Feb 01, 2021 4:37 pm
by jbo_mar
Hello,

I'm also having the same issue with the latest version of V2 Converter. See log below.

The log file name: 'logs\V2V_Log-20210201-171428.log' (PID 16748)
2/1 17:14:28.380 34ec Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
2/1 17:14:28.380 34ec Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.0.202
2/1 17:14:28.380 34ec Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
2/1 17:14:28.380 34ec Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_RUSSIAN
2/1 17:14:28.380 34ec Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
2/1 17:14:28.380 34ec Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 19041
2/1 17:14:28.380 34ec Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - c1e70000
2/1 17:14:28.380 34ec Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - c1e70000
2/1 17:14:34.255 34ec Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputFile
2/1 17:14:39.684 34ec Facility ???INFO: CPPInputFile::checkFile: Select file: D:\tmp\OM_2030.qcow2
2/1 17:14:39.700 34ec Facility ???INFO: CPPInputFile::checkFile: ParseFile: 19

Reminder on qcow2 v3 (from qemu wiki : https://wiki.qemu.org/Features/Qcow3#In ... egotiation):
The QCOW image format includes a version number to allow introducing new features that change the format in an incompatible way, so that older qemu versions can't read the image any more.
When this version number was changed from QCOW1 to QCOW2, the format was radically changed. QCOW1 and QCOW2 have two completely different driver implementations and the two versions actually are exposed as two different image formats ("qcow" and "qcow2") to the user.
The proposal for QCOW3 is different: It includes a version number increase in order to introduce some incompatible features, however it's strictly an extension of QCOW2 and keeps the fundamental structure unchanged, so that a single codebase will be enough for working with both QCOW2 and QCOW3 images.
Internally, QEMU will have a single driver for both QCOW2 and QCOW3 images, so it's an option to continue letting users know the format as "qcow2", just with an additional flag that can be set on image creation and specifies which version number should be used (and therefore, which features should be available).

What do you suggest?

Regards
Jerome

Re: Support for QCOW3

Posted: Mon Feb 08, 2021 4:12 am
by yaroslav (staff)
Hi,

Could you please provide us with the whole log?

Re: Support for QCOW3

Posted: Mon Jan 03, 2022 3:47 pm
by 1mn0tjack
so the log files pasted above i can vouch are complete.

here is my ENTIRE LOG for that session. I'm running into the same issue.


The log file name: 'logs\V2V_Log-20220103-092739.log' (PID 16800)
1/3 9:27:39.956 36dc Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
1/3 9:27:39.972 36dc Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.243
1/3 9:27:39.977 36dc Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
1/3 9:27:39.977 36dc Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
1/3 9:27:39.988 36dc Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 20348
1/3 9:27:39.988 36dc Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 4b310000
1/3 9:27:39.988 36dc Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 4b310000
1/3 9:29:34.445 36dc Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputFile
1/3 9:29:44.602 36dc Facility ???INFO: CPPInputFile::checkFile: Select file: D:\Share\new\moved\MeshCentral.qcow2
1/3 9:29:44.602 36dc Facility ???INFO: CPPInputFile::checkFile: ParseFile: 19


again. there is nothing else in the log file at "C:\Program Files\StarWind Software\StarWind V2V Converter\logs". this is the ENTIRE thing.

If there is another log file in existence, please let us know what the path to it is.

I'm unable to attach the screenshot as evidence that this is all thats in the log file.

Re: Support for QCOW3

Posted: Tue Jan 04, 2022 5:59 am
by yaroslav (staff)
Hi,

do you convert qcow3 or qcow2?

Re: Support for QCOW3

Posted: Tue Aug 02, 2022 7:07 pm
by promo
Seeing the same error. Converting qcow2 image. File on the qcow2 image shows the following:
QEMU QCOW2 Image (v3), xxxxxxxxxx bytes

Re: Support for QCOW3

Posted: Tue Aug 02, 2022 9:59 pm
by yaroslav (staff)
Welcome to StarWind Forum. Could you please share the log files' contents with us here?

Re: Support for QCOW3

Posted: Sat Jan 06, 2024 10:36 pm
by danswartz
I ran into the same issue. Trying to go from proxmox/raw to hyperv/vhdx. On proxmox converted raw to qcow2, uploaded to hyperv and tried v2v, but it choked the same way (complaining that version 3 is not supported.). Ended up converting from raw => vmdk, uploading that, then v2v convert to vhdx.

Re: Support for QCOW3

Posted: Sat Jan 06, 2024 11:01 pm
by yaroslav (staff)
Thanks for sharing the workaround!