Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionkuwei@redhat.com
2017-01-24 06:42:47 UTC
virt-v2v auto running to convert esx guests failed with error "qemu-img: error while reading sector 24942336: Protocol error"
Package version:
libguestfs-1.32.7-3.el7.3.x86_64
virt-v2v-1.32.7-3.el7.3.x86_64
Scenario 1:
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:
Server IP:
10.73.72.xx
Packages:
virt-v2v-1.32.7-3.el7.3.x86_64
libguestfs-1.32.7-3.el7.3.x86_64
Scenario 2：
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 10.73.72.61
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 * * *
Scenario 3:
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
Additional info:
About the virt-v2v packages you can get from the bug https://bugzilla.redhat.com/show_bug.cgi?id=1414505comment5 :http://oirase.annexia.org/tmp/bz1414505/
Comment 3Richard W.M. Jones
2017-01-24 13:24:09 UTC
The causes of this are always:
(1) The vCenter server is too slow.
http://libguestfs.org/virt-v2v.1.html#vmware-vcenter-resources
(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.
Comment 7Richard W.M. Jones
2017-02-09 10:32:40 UTC