Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
convert xml doesn't support qcow,qcow2,cow format
Version-Release number of selected component (if applicable):
-libvirt-0.8.1-13.el6.x86_64
-qemu-kvm-0.12.1.2-2.90.el6.x86_64
-qemu-img-0.12.1.2-2.90.el6.x86_64
-kernel-2.6.32-42.el6.x86_64
-libvirt-python-0.8.1-13.el6.x86_64
How reproducible:
5/5
Steps to Reproduce:
1.
# cat virt_image.xml
<image>
<name>demo</name>
<domain>
<boot type="hvm">
<guest>
<arch>x86_64</arch>
</guest>
<os>
<loader dev="hd"/>
</os>
<drive disk="mydisk" target="hda"/>
</boot>
<devices>
<vcpu>1</vcpu>
<memory>262144</memory>
<interface/>
<graphics/>
</devices>
</domain>
<storage>
<disk id="mydisk" file="RHEL-Server-6-64-virtio.qcow2" use="system" format="qcow2"/>
</storage>
</image>
2.
# qemu-img info RHEL-Server-6-64-virtio.qcow2
image: RHEL-Server-6-64-virtio.qcow2
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 971M
cluster_size: 4096
3.
# virt-convert -i virt-image -o vmx virt_image.xml
ERROR Couldn't import file "virt_image.xml": Unable to determine disk format
Actual results:
I tried the 'qcow2' and 'qcow' format and get the same result:
ERROR Couldn't import file "virt_image.xml": Unable to determine disk format
Expected results:
virt-convert command support virt-image format convert to other format.
Additional info:
I try to change the format in the xml file use that:
"<disk id="mydisk" file="RHEL-Server-6-64-virtio.qcow2" use="system" format="raw"/>" and <disk id="mydisk" file="test.qcow" use="system" format="raw"/>.
Setps
1.
# virt-convert -i virt-image -o vmx virt_image.xml
Generating output in 'vmx' format to demo/
Converting disk 'RHEL-Server-6-64-virtio.qcow2' to type vmdk...
Done.
# virt-convert -i virt-image -o vmx virt_image.xml
Generating output in 'vmx' format to demo/
Converting disk 'test.qcow' to type vmdk...
Done.
For the above steps, virt-convert can support qcow2/raw/qcow convert to vmdk. xml format = ?,maybe need to add some options support qcow2/qcow format.
Comment 2RHEL Program Management
2010-07-15 14:54:30 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
* virt-convert now includes support for qcow, qcow2, and cow formats. (BZ#612842)
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-* virt-convert now includes support for qcow, qcow2, and cow formats. (BZ#612842)+virt-convert now includes support for qcow, qcow2, and cow formats.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0636.html
Description of problem: convert xml doesn't support qcow,qcow2,cow format Version-Release number of selected component (if applicable): -libvirt-0.8.1-13.el6.x86_64 -qemu-kvm-0.12.1.2-2.90.el6.x86_64 -qemu-img-0.12.1.2-2.90.el6.x86_64 -kernel-2.6.32-42.el6.x86_64 -libvirt-python-0.8.1-13.el6.x86_64 How reproducible: 5/5 Steps to Reproduce: 1. # cat virt_image.xml <image> <name>demo</name> <domain> <boot type="hvm"> <guest> <arch>x86_64</arch> </guest> <os> <loader dev="hd"/> </os> <drive disk="mydisk" target="hda"/> </boot> <devices> <vcpu>1</vcpu> <memory>262144</memory> <interface/> <graphics/> </devices> </domain> <storage> <disk id="mydisk" file="RHEL-Server-6-64-virtio.qcow2" use="system" format="qcow2"/> </storage> </image> 2. # qemu-img info RHEL-Server-6-64-virtio.qcow2 image: RHEL-Server-6-64-virtio.qcow2 file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 971M cluster_size: 4096 3. # virt-convert -i virt-image -o vmx virt_image.xml ERROR Couldn't import file "virt_image.xml": Unable to determine disk format Actual results: I tried the 'qcow2' and 'qcow' format and get the same result: ERROR Couldn't import file "virt_image.xml": Unable to determine disk format Expected results: virt-convert command support virt-image format convert to other format. Additional info: I try to change the format in the xml file use that: "<disk id="mydisk" file="RHEL-Server-6-64-virtio.qcow2" use="system" format="raw"/>" and <disk id="mydisk" file="test.qcow" use="system" format="raw"/>. Setps 1. # virt-convert -i virt-image -o vmx virt_image.xml Generating output in 'vmx' format to demo/ Converting disk 'RHEL-Server-6-64-virtio.qcow2' to type vmdk... Done. # virt-convert -i virt-image -o vmx virt_image.xml Generating output in 'vmx' format to demo/ Converting disk 'test.qcow' to type vmdk... Done. For the above steps, virt-convert can support qcow2/raw/qcow convert to vmdk. xml format = ?,maybe need to add some options support qcow2/qcow format.