<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 5, 2017 at 4:15 PM, Richard W.M. Jones <span dir="ltr"><<a href="mailto:rjones@redhat.com" target="_blank">rjones@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span>On Wed, Jul 05, 2017 at 11:14:09AM +0200, Matthias Leopold wrote:<br>
> hi,<br>
><br>
> i'm trying to import a VM in oVirt from a KVM host that doesn't use<br>
> storage pools. this fails with the following message in<br>
> /var/log/vdsm/vdsm.log:<br>
><br>
> 2017-07-05 09:34:20,513+0200 ERROR (jsonrpc/5) [root] Error getting<br>
> disk size (v2v:1089)<br>
> Traceback (most recent call last):<br>
> File "/usr/lib/python2.7/site-packa<wbr>ges/vdsm/v2v.py", line 1078, in<br>
> _get_disk_info<br>
> vol = conn.storageVolLookupByPath(di<wbr>sk['alias'])<br>
> File "/usr/lib64/python2.7/site-pac<wbr>kages/libvirt.py", line 4770,<br>
> in storageVolLookupByPath<br>
> if ret is None:raise libvirtError('virStorageVolLoo<wbr>kupByPath()<br>
> failed', conn=self)<br>
> libvirtError: Storage volume not found: no storage vol with matching path<br>
><br>
> the disks in the origin VM are defined as<br>
><br>
> <disk type='file' device='disk'><br>
> <driver name='qemu' type='raw' cache='writethrough'/><br>
> <source file='/dev/kvm108/kvm108_img'/<wbr>><br>
><br>
> <disk type='file' device='cdrom'><br>
> <driver name='qemu' type='raw'/><br>
> <source file='/some/path/CentOS-7-x86_<wbr>64-Minimal-1611.iso'/><br>
><br>
> is this a virt-v2v or oVirt problem?<br>
<br>
</span>Well the stack trace is in the oVirt code, so I guess it's an oVirt<br>
problem. Adding ovirt-users mailing list.<br></blockquote><div><br></div><div>Right, import of KVM VMs to oVirt doesn't involve virt-v2v.</div><div>The current process gets the virtual size (i.e., capacity) and the actual size (i.e., allocation) of the volume using libvirt api that seems to rely on having the volume in a storage pool. So the process would need to be extended in order to support the case of having volumes that are not part of a storage pool.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Rich.<br>
<span class="gmail-m_8771377581766124450HOEnZb"><font color="#888888"><br>
--<br>
Richard Jones, Virtualization Group, Red Hat <a href="http://people.redhat.com/~rjones" rel="noreferrer" target="_blank">http://people.redhat.com/~rjon<wbr>es</a><br>
Read my programming and virtualization blog: <a href="http://rwmj.wordpress.com" rel="noreferrer" target="_blank">http://rwmj.wordpress.com</a><br>
virt-df lists disk usage of guests without needing to install any<br>
software inside the virtual machine. Supports Linux and Windows.<br>
<a href="http://people.redhat.com/~rjones/virt-df/" rel="noreferrer" target="_blank">http://people.redhat.com/~rjon<wbr>es/virt-df/</a><br>
</font></span><div class="gmail-m_8771377581766124450HOEnZb"><div class="gmail-m_8771377581766124450h5"><br>
______________________________<wbr>_________________<br>
Libguestfs mailing list<br>
<a href="mailto:Libguestfs@redhat.com" target="_blank">Libguestfs@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/libguestfs" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/libguestfs</a><br>
</div></div></blockquote></div><br></div></div>