> On 19 Aug 2018, at 09:59, Roy Golan <[email protected]> wrote: > > > > On Sat, 18 Aug 2018 at 18:45 Bernhard Dick <[email protected] > <mailto:[email protected]>> wrote: > Hi, > > currently I'm trying to move VMs from our vsphere 5 environment to > oVirt. While the io performance on oVirt and on the esxi platform is > quite well (about 100MByte/sec on a 1GBit storage link) the transfer > speed using the integrated v2v-feature is very slow (only 10MByte/sec). > That would result in transfer time of >24h for some machines. > Do you have any ideas how I can improve the transfer speed? > > Regards > Bernhard Dick > > Hi Bernhard, > > With the latest version of the ovirt-imageio and the v2v we are performing > quite nicely, and without specifying
the difference is that with the integrated v2v you don’t use any of that. It’s going through the vCenter server which is the major slowdown. With 10MB/s I do not expect the bottleneck is on our side in any way. After all the integrated v2v is writing locally directly to the target prepared volume so it’s probably even faster than imageio. the “new” virt-v2v -o rhv-upload method is not integrated in GUI, but supports VDDK and SSH methods of access which both should be faster you could try to use that, but you’d need to use it on cmdline https://github.com/oVirt/ovirt-ansible-v2v-conversion-host/ might help to use it a bit more nicely Thanks, michal > number I can tell you that weakest link is the read rate from the vmware data > store. In our lab > I can say that we roughly peek ~40 MiB/sec reading a single vm and the rest > of our components(after the read from vmds) > have no problem dealing with that - i.e buffering -> converting -> writing to > imageio -> writing to storage > > So, in short, examine the read-rate from vm datastore, let us know, and > please specify the versions you are using. > > _______________________________________________ > Users mailing list -- [email protected] <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[email protected]> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > <https://www.ovirt.org/site/privacy-policy/> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://www.ovirt.org/community/about/community-guidelines/> > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/KQZPRX4M7V74FSYIY5LRUPC46CCJ2DCR/ > > <https://lists.ovirt.org/archives/list/[email protected]/message/KQZPRX4M7V74FSYIY5LRUPC46CCJ2DCR/> > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/WYKFJPEIPGVUT7Q6TMRVLYRAFQVWBQTI/
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/M76NNN32GURMT4OHNWERJFJJFNWV3UUG/
