Hide Forgot
Description of problem: There is no workaround step popped-up when converting a VM, which doesn't belong to any storage pool, from *KVM*, although the steps will pop up when converting a VM with the same scenario but from *Xen* (Bug 672498) Version-Release number of selected component (if applicable): virt-v2v-0.7.1-2.el5 libvirt-0.8.2-15.el5_6.3 libguestfs-1.2.7-1.el5.13 How reproducible: always Steps to Reproduce: 1.In KVM kernel, setup a VM that doesn't belong to any storage pool 2. Convert the above VM from KVM to RHEV # virt-v2v -ic qemu+ssh://10.66.72.122/system -o rhev -op 10.66.90.115:/vol/v2vrwu1/rwu_export v2v-auto-rhevm-2k8-r2 root.72.122's password: virt-v2v: Failed to retrieve storage volume /mnt/sdb/image/Win2008r2-64-hvm.raw:libvirt error code: 47, message: invalid storage volume pointer in no storage vol with matching path Actual results: as steps mentioned Expected results: The workaround steps will pop up when converting a VM from KVM Additional info:
Verified with virt-v2v-0.7.1-4.el5.There is the popped-up msg when converting a vm which doesn't belong to a storage pool. # virt-v2v -ic xen+ssh://10.66.72.123 -os default rhel4-32-hvm-min -b breth0 root.72.123's password: virt-v2v: Failed to retrieve volume information for /var/lib/xen/images/rhel4-32-hvm-min.img. This could be because the volume doesn't exist, or because the volume exists but is not contained in a storage pool. In the latter case, you must create a storage pool of the correct type to contain the volume. Note that you do not have to re-create or move the volume itself, only define a pool which contains it. libvirt will automatically detect the volume when it scans the pool after creation. virt-manager is able to create storage pools. Select Edit->Connection Details from the application menu. Storage pools are displayed in the Storage tab.