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.
Cause:
When reading a libvirt guest, virt-v2v uses libvirt metadata to determine the on-disk format used by the guest. However, this data is only meaningful for libvirt pools of type 'dir', 'fs' and 'netfs'. If a guest used a different type of storage pool, virt-v2v would attempt to interpret this meaningless data as a format type.
Consequence:
virt-v2v was unable to convert libvirt guests which used storage pools of types other than 'dir', 'fs' and 'netfs'.
Fix:
virt-v2v now only uses volume format metadata from storage pools of type 'dir', 'fs' and 'netfs'. All other storage pools can only hold raw data, so the format is assumed to be 'raw'.
Result:
virt-v2v can now convert libvirt guests using any supported storage pool type.
Description of problem:
Convert VM with image pointing to host's partition,virt-v2v error:cannot handle volumes of format none
Version-Release number of selected component (if applicable):
virt-v2v-0.8.7-4.el6.x86_64
libvirt-0.9.10-5.el6.x86_64
llibguestfs-1.16.8-1.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Create new partition on host:
#fdisk /dev/sd3
Command (m for help): n
Command (m for help): w
2.Create a pool to include the partition.
# virsh pool-dumpxml dev
<pool type='disk'>
<name>dev</name>
<uuid>27c1cfc7-c3fe-989b-384f-ca4c7f06e2c0</uuid>
<capacity unit='bytes'>500105249280</capacity>
<allocation unit='bytes'>338585064960</allocation>
<available unit='bytes'>161520152064</available>
<source>
<device path='/dev/sda'>
<freeExtent start='107372805120' end='107373133824'/>
<freeExtent start='338585425920' end='500105249280'/>
</device>
<format type='dos'/>
</source>
<target>
<path>/dev</path>
<permissions>
<mode>0700</mode>
<owner>-1</owner>
<group>-1</group>
</permissions>
</target>
</pool>
# virsh vol-list dev --details
Name Path Type Capacity Allocation
---------------------------------------------
sda1 /dev/sda1 block 100.00 GB 100.00 GB
sda2 /dev/sda2 block 200.00 GB 200.00 GB
sda3 /dev/sda3 block 7.67 GB 7.67 GB
sda4 /dev/sda4 block 7.67 GB 7.67 GB
3.Create a VM based on the above partition:
....
<disk type='block' device='disk'>
<driver name='qemu' type='raw' cache='none' io='native'/>
<source dev='/dev/sda3'/>
<target dev='hda' bus='ide'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
....
4.Use virt-v2v to convert the above guest to rhevm:
# virt-v2v -o rhev -os 10.66.90.115:/vol/v2v_auto/nfs_export -n rhevm test-sda3
virt-v2v: RHEV cannot handle volumes of format none
Also I tried with local libvirtxml,it can convert successfully.
# virt-v2v -i libvirtxml -o rhev -os 10.66.90.115:/vol/v2v_auto/auto_export -n rhevm test-sda3.xml
[====================================================================sda3: 100% 0h05m29s
virt-v2v: test-sda3 configured with virtio drivers.
Actual results:
virt-v2v error:cannot handle volumes of format none
Expected results:
virt-v2v should handle the format and convert successfully.
Additional info:
In virt-manager,the format of the block volume listed in pool is none,and libvirt can not handle the format of block volume,see the screenshot.
Created attachment 570238[details]
screenshot of the volume format
Attached the screenshot of the volume format.
Comment 3RHEL Program Management
2012-05-03 04:37:36 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Find two other similar issues:
1.If add a iscsi pool,by default,the format of the volumes is lvm2,when install a guest on the volume then convert,error occurs:
virt-v2v: Failed to create storage volume: libvirt error code: 27, message: XML error: unknown volume format type lvm2
2.If add a mpath pool,by default,the format of the volumes is dos,when install a guest on the volume then convert,error occurs:
virt-v2v: Failed to create storage volume: libvirt error code: 27, message: XML error: unknown volume format type dos
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0477.html
Description of problem: Convert VM with image pointing to host's partition,virt-v2v error:cannot handle volumes of format none Version-Release number of selected component (if applicable): virt-v2v-0.8.7-4.el6.x86_64 libvirt-0.9.10-5.el6.x86_64 llibguestfs-1.16.8-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1. Create new partition on host: #fdisk /dev/sd3 Command (m for help): n Command (m for help): w 2.Create a pool to include the partition. # virsh pool-dumpxml dev <pool type='disk'> <name>dev</name> <uuid>27c1cfc7-c3fe-989b-384f-ca4c7f06e2c0</uuid> <capacity unit='bytes'>500105249280</capacity> <allocation unit='bytes'>338585064960</allocation> <available unit='bytes'>161520152064</available> <source> <device path='/dev/sda'> <freeExtent start='107372805120' end='107373133824'/> <freeExtent start='338585425920' end='500105249280'/> </device> <format type='dos'/> </source> <target> <path>/dev</path> <permissions> <mode>0700</mode> <owner>-1</owner> <group>-1</group> </permissions> </target> </pool> # virsh vol-list dev --details Name Path Type Capacity Allocation --------------------------------------------- sda1 /dev/sda1 block 100.00 GB 100.00 GB sda2 /dev/sda2 block 200.00 GB 200.00 GB sda3 /dev/sda3 block 7.67 GB 7.67 GB sda4 /dev/sda4 block 7.67 GB 7.67 GB 3.Create a VM based on the above partition: .... <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/sda3'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> .... 4.Use virt-v2v to convert the above guest to rhevm: # virt-v2v -o rhev -os 10.66.90.115:/vol/v2v_auto/nfs_export -n rhevm test-sda3 virt-v2v: RHEV cannot handle volumes of format none Also I tried with local libvirtxml,it can convert successfully. # virt-v2v -i libvirtxml -o rhev -os 10.66.90.115:/vol/v2v_auto/auto_export -n rhevm test-sda3.xml [====================================================================sda3: 100% 0h05m29s virt-v2v: test-sda3 configured with virtio drivers. Actual results: virt-v2v error:cannot handle volumes of format none Expected results: virt-v2v should handle the format and convert successfully. Additional info: In virt-manager,the format of the block volume listed in pool is none,and libvirt can not handle the format of block volume,see the screenshot.