[Users] Making v2v easier?

[Markus Stockhausen]

> Von: users-bounces at ovirt.org [users-bounces at ovirt.org]" im Auftrag von "Itamar Heim [iheim at redhat.com]
> Gesendet: Freitag, 17. Januar 2014 16:19
> An: users >> "users at ovirt.org"
> Betreff: [Users] Making v2v easier?
> 
> I see a lot of threads about v2v pains (mostly from ESX?)
>
> I'm interested to see if we can make this simpler/easier.
> 
> if you have experience with this, please describe the steps you are
> using (also the source platform), and how you would like to see this
> make simpler (I'm assuming that would start from somewhere in the
> webadmin probably).
> 
> Thanks,
>     Itamar

Hello,

for me virt-v2v will be a one-timer until everything is migrated
into OVirt. If you had hard times to arrange everything and know
how to deal with it, the tool works quite well. Nevertheless for
for new users this can be very frustrating. 

The two most annoying things are for me:

- Migration is sequential and slow. We have a lot of big SAP systems
with 250GB++. The infrastructure is backed by a 10G IPoIB network 
that can easily copy files between NFS server at sustained speed of 
500MB/s. virt-v2v cannot go beyond 40MB/s and thus about 2 hours
to migrate a machine. I understand that the process involves a "long"  
chain ESXNFS->ESX->virt-v2v->OVirtNFS. Maybe one should think 
of providing a parametrization to copy multiple disk images at the 
same time. 

- Even worse is to wait 2 hours for the migration to finish and getting
afterwards errors about missing entries in virt-v2v.db or problems
during mount of the VM filesystems. Maybe the step or at least a check
could be issued after the migration of the (small) OS/boot disk.

Markus

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140119/b2ab004b/attachment-0001.txt>