Hide Forgot
Description of problem: When I attempt to migrate VM's from the VMware platform to the Ovirt platform all goes well up until the point where the migration actually needs to start copying data from the VMware host. VDSM log shows. V2VProcessError: Job u'420fd066-5fdd-8a3f-1a03-9f168e73124b' process failed exit-code: 1, stderr: curl -q --insecure --user '<hidden>' --head --silent --url 'https://172.16.1.251/folder/migrateme/migrateme-flat.vmdk?dcPath=APSYS/Home&dsName=ISCSI-LUN0' HTTP/1.1 404 Not Found Version-Release number of selected component (if applicable): engine virt-v2v-1.28.1-1.55.el7.centos.x86_64 Compute Node: selected proxy virt-v2v-1.28.1-1.55.el7.centos.x86_64 How reproducible: Consistent. Steps to Reproduce: 1. Walkthrough as shown in Arik's instruction. https://www.youtube.com/watch?v=7vd8X6t9eBk 2. 3. Actual results: System throws error and cleans up the VM created during the initial phase of the migration. Expected results: Successful migration ov VM. Additional info:
is it possible you have a Cluster on VMware side? See bug 1292096 - there are fixed packages available(not yet released), maybe you can try out those? (both libvirt and v2v)
Yes the VM is in a cluster. (that’s pretty much standard for production setups) I'd love to try out the updated packages. What version do i need and do you have any pointers to where i get them? + if I need to do something additional. I got the test rig running and I/we can thrash it as much as I'd like.
*** Bug 1318008 has been marked as a duplicate of this bug. ***
the fix is on v2v and libvirt side, pending updates in RHEL and CentOS, should happen in 3.6.5 timeframe see also bug 1292096
Verified using VMware 6 build 2594327 and VMware 5.5 build 2893190: rhevm-3.6.5.3-0.1.el6 qemu-kvm-rhev-2.3.0-31.el7_2.10.x86_64 vdsm-4.17.26-0.el7ev.noarch libvirt-daemon-1.2.17-13.el7_2.4.x86_64 sanlock-3.2.4-2.el7_2.x86_64