virt-v2v auto running to convert esx guests failed with error "qemu-img: error while reading sector 24942336: Protocol error"
1.The test results of virt-v2v auto running for all esx guests are failed,because when using virt-v2v to convert guests from vmware to libvirt by auto running,and the error info is "qemu-img: error while reading sector 24942336: Protocol error", details pls refer to log"virt-v2v-auto-running"
The environment of virt-v2v auto running:
1.Try to use virt-v2v convert guest from vmware to libvirt by manual on above server 10.73.72.xx, found the speed of converting is so slow that v2v conversion still can't be finished after 2h,actually, v2v will cost 2.5h to convert a linux guest from vmware to libvirt and converting a windows guest cost more time (3h+),the hopes between v2v auto machine(10.73.72.xx) and esx6.0 server is as below
traceroute to 10.73.72.61 (10.73.72.61), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
30 * * *
1.The test results of virt-v2v auto running for all xen guests are passed and the speed is normal when using virt-v2v convert guest from xen to libvirt by manual on this v2v auto machine,the hopes between v2v auto machine(10.73.72.xx) and xen server is as below
# traceroute 10.73.3.21
traceroute to 10.73.3.21 (10.73.3.21), 30 hops max, 60 byte packets
1 gateway (10.73.75.254) 42.786 ms 42.770 ms 42.759 ms
2 10.72.0.54 (10.72.0.54) 0.695 ms 0.709 ms 0.725 ms
3 10.72.0.49 (10.72.0.49) 0.892 ms 10.72.0.51 (10.72.0.51) 1.148 ms 10.72.0.49 (10.72.0.49) 0.938 ms
4 * * *
5 hp-dl360eg8-08.lab.eng.pek2.redhat.com (10.73.3.21) 4.171 ms 4.149 ms 4.129 ms
About the virt-v2v packages you can get from the bug https://bugzilla.redhat.com/show_bug.cgi?id=1414505 comment5 :http://oirase.annexia.org/tmp/bz1414505/
Created attachment 1243828 [details]
The causes of this are always:
(1) The vCenter server is too slow.
(2) The network connection is interrupted in some way. For
example, there is actual network break, or a machine gets
assigned a different IP address.
> #traceroute 10.73.72.61
> traceroute to 10.73.72.61 (10.73.72.61), 30 hops max, 60 byte packets
> 1 * * *
> 2 * * *
I don't understand this traceroute. Address 10.73.72.61 is
not mentioned at all in the virt-v2v log file.
These commits were added upstream which should prevent ssh
connections from being dropped:
However I don't believe this is related to the cause of this
bug which will be down to network slowness or interruption
(see comment 3).