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.

Bug 800776

Summary: P2V fail with error:Error receiving data
Product: Red Hat Enterprise Linux 6 Reporter: tingting zheng <tzheng>
Component: virt-p2vAssignee: Matthew Booth <mbooth>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.3CC: hyao, jgreguske, jwu, lcui, rjones, rwu, syeghiay, yupzhang
Target Milestone: rcKeywords: TestBlocker, TestOnly
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libssh2-1.2.2-7.el6_2.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 15:09:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 804145    
Bug Blocks:    
Attachments:
Description Flags
P2V error screenshot none

Description tingting zheng 2012-03-07 08:20:03 UTC
Created attachment 568189 [details]
P2V error screenshot

Description of Problem:
P2V fail with error:Error receiving data

Version-Release number of selected component:
rubygem-virt-p2v-0.8.6-1.el6
virt-v2v-0.8.7-3.el6.x86_64

How reproducible:
Always

Step to Reproduce:
1.Download the virt-p2v iso from brewweb.

2.Plug in USB,boot the Live CD with USB
#livecd-iso-to-disk --format VirtP2V_0.8.6-1.iso  /dev/sdb 

3.Boot from USB,input the ip and password of conversion server to connect the virt-p2v server.

4.Configure the server address and target storage,start to convert the host.

Actual Results:
When the data transferred about 60-70G,then the error occurred:
in p2v-client:Error writing to channel:unable to send channal data.
Also can find error in log:Error receiving data.


Expected Results:
It should be converted successfully.

Additional info:
The screenshot of p2v error is attached.

Comment 4 Matthew Booth 2012-03-16 15:41:07 UTC
Lets track this here because this bug is critically important to virt-p2v, however it's actually a bug in libssh2. I've posted an upstream patch here:

http://www.libssh2.org/mail/libssh2-devel-archive-2012-03/0106.shtml

Comment 11 tingting zheng 2012-03-29 09:32:26 UTC
Verified this issue with :
Virt-P2V_0.8.6-2.iso
virt-v2v-0.8.7-4.el6.x86_64

Use virt-p2v to convert a physical machine with about 350G disk,it can convert successfully.So set the bug to VERIFIED.

Comment 12 errata-xmlrpc 2012-06-20 15:09:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0965.html