<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 10, 2017 at 7:54 PM, Ramachandra Reddy Ankireddypalle <span dir="ltr"><<a href="mailto:rcreddy.ankireddypalle@gmail.com" target="_blank">rcreddy.ankireddypalle@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Thanks for looking in to this. I am looking for a way to achieve this through command/script. I tried using virtv2v as below.<br><br>[root@hcadev3 tmp]# virt-v2v -i ova 1Deepakvm2.ova -o rhev -of qcow2 -os hcadev3:/dav_vm_vol<br>[ 0.0] Opening the source -i ova 1Deepakvm2.ova<br>[ 1.2] Creating an overlay to protect the source from being modified<br>[ 2.3] Initializing the target -o rhev -os hcadev3:/dav_vm_vol<br>mount.nfs: requested NFS version or transport protocol is not supported<br><br></div>I am looking for a way to provide an option to virt-v2v to understand that dav_vm_vol is a glusterfs volume and that it can be accessed from node hcadev3.<br></div></blockquote><div><br></div><div>So the "-o rhev" should not be used in that case because then virt-v2v assumes the target is an export domain and tries to mount it as NFS.</div><div>If this has to be done via the command line then the flag that needs to be used in virt-v2v is "-o vdsm" but it requires you to create the images and mount them to the host that the conversion is executed on by yourself + to execute virt-v2v with vdsm's permissions - which is complicated. That is why this option was not intended for invocation by users from the command line (but to be used by vdsm), however, that's possible.</div><div>It would be simpler to use the REST-API based clients in that case.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 10, 2017 at 2:36 AM, Arik Hadas <span dir="ltr"><<a href="mailto:ahadas@redhat.com" target="_blank">ahadas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, Jul 7, 2017 at 9:38 PM, Ramachandra Reddy Ankireddypalle <span dir="ltr"><<a href="mailto:rcreddy.ankireddypalle@gmail.com" target="_blank">rcreddy.ankireddypalle@gmail.<wbr>com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi,<br></div> Does virt-v2v command work with glusterfs storage domain. I have an OVA image and that needs to be imported to glusterfs storage domain. Please provide some pointers to this.<br></div></div></div></blockquote><div><br></div></span><div> I don't see a reason why it wouldn't work.</div><div>Assuming that the import operation is triggered from oVirt, the engine then creates the target disk(s) and prepares the image(s) on the host that the conversion will be executed on as it regularly does. virt-v2v then just to write to that "prepared" image.</div><div>In the import dialog you can select the target storage domain. I would suggest that you just try to pick the glusterfs storage domain and see if it works. It should work, if not - please let us know.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><br></div>Thanks and Regards,<br></div>Ram <br></div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>