9:38 p.m.
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.
Thanks and Regards,
Ram
9:36 a.m.
On Fri, Jul 7, 2017 at 9:38 PM, Ramachandra Reddy Ankireddypalle <
rcreddy.ankireddypalle(a)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.
Thanks and Regards,
Ram
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:54 p.m.
Thanks for looking in to this. I am looking for a way to achieve this
through command/script. I tried using virtv2v as below.
[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
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.
On Mon, Jul 10, 2017 at 2:36 AM, Arik Hadas <ahadas(a)redhat.com> wrote:
On Fri, Jul 7, 2017 at 9:38 PM, Ramachandra Reddy Ankireddypalle <
rcreddy.ankireddypalle(a)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.
>
> Thanks and Regards,
> Ram
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
11:18 a.m.
On Mon, Jul 10, 2017 at 7:54 PM, Ramachandra Reddy Ankireddypalle <
rcreddy.ankireddypalle(a)gmail.com> wrote:
Thanks for looking in to this. I am looking for a way to achieve
this
through command/script. I tried using virtv2v as below.
[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
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.
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.
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.
It would be simpler to use the REST-API based clients in that case.
On Mon, Jul 10, 2017 at 2:36 AM, Arik Hadas <ahadas(a)redhat.com> wrote:
>
>
> On Fri, Jul 7, 2017 at 9:38 PM, Ramachandra Reddy Ankireddypalle <
> rcreddy.ankireddypalle(a)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.
>
>
>>
>> Thanks and Regards,
>> Ram
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
2690
days inactive
2694
days old
3 comments
2 participants
participants (2)
-
Arik Hadas -
Ramachandra Reddy Ankireddypalle