Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 731293

Summary: guest->host and host->guest packets have wrong checksums when tx offload is on
Product: Red Hat Enterprise Linux 5 Reporter: Pengzhen Cao <pcao>
Component: xenpv-winAssignee: Paolo Bonzini <pbonzini>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.8CC: bgollahe, drjones, fnadge, herbert.xu, leiwang, llim, moli, pbonzini, qwan, xen-maint, yufang521247
Target Milestone: rcKeywords: Regression, TestOnly
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 617435 Environment:
Last Closed: 2011-09-01 10:10:35 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: 617435    
Bug Blocks: 518405    

Comment 2 Paolo Bonzini 2011-08-17 23:21:13 UTC 
Will be fixed by the patch in bug 718329.
Comment 3 Yufang Zhang 2011-08-29 07:00:05 UTC 
(In reply to comment #2)
> Will be fixed by the patch in bug 718329.

We also encounter such problem for the 'remote host <----> guest' scenario. RDP just got stuck there when I tried to connect to Win2003 guest from a native Windows host.
Comment 4 Paolo Bonzini 2011-08-29 08:06:59 UTC 
Please check that the steps in bug 718329 comment 9 work around the problem.
Comment 5 Yufang Zhang 2011-08-30 08:59:55 UTC 
Just a confirmation, the workaround in bug 718329 comment 9 works for me. Thanks Paolo.
Comment 6 Paolo Bonzini 2011-09-01 10:10:35 UTC 
Closing then, thanks!

*** This bug has been marked as a duplicate of bug 657540 ***