Thanks for looking in to this. I am looking for a way to achieve this through command/script. I tried using virtv2v as below.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.
[root@hcadev3 tmp]# virt-v2v -i ova 1Deepakvm2.ova -o rhev -of qcow2 -os hcadev3:/dav_vm_vol
[ 0.0] Opening the source -i ova 1Deepakvm2.ova
[ 1.2] Creating an overlay to protect the source from being modified
[ 2.3] Initializing the target -o rhev -os hcadev3:/dav_vm_vol
mount.nfs: requested NFS version or transport protocol is not supported
On Mon, Jul 10, 2017 at 2:36 AM, Arik Hadas <ahadas@redhat.com> wrote:On Fri, Jul 7, 2017 at 9:38 PM, Ramachandra Reddy Ankireddypalle <rcreddy.ankireddypalle@gmail.com > wrote:Hi,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.I don't see a reason why it wouldn't work.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.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.RamThanks and Regards,
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users