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 517236

Summary:	[RHEL5 Xen]: Backport fix for migration hang
Product:	Red Hat Enterprise Linux 5	Reporter:	Chris Lalancette <clalance>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.5	CC:	jdenemar, pbonzini, xen-maint
Target Milestone:	rc
Target Release:	5.6
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-10-23 13:42:39 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:

Description Chris Lalancette 2009-08-13 07:33:42 UTC

Description of problem:
Recently the patch mentioned in this mailing list post:

http://lists.xensource.com/archives/html/xen-devel/2009-07/msg01094.html

Went into xen-unstable as c/s 19990.  We should evaluate whether we have the problem mentioned in that mailing list post, and if this patch fixes it for us.

Comment 1 Paolo Bonzini 2009-08-13 09:43:42 UTC

This looks like a very ugly fix for upstream...  it would be better to ensure every file descriptor is FD_CLOEXEC'd unless necessary.  But I guess for RHEL5.5 is exactly the hack that we need to fix the bug non-invasively. :-)

Comment 2 Jiri Denemark 2009-10-23 13:42:39 UTC

I haven't decided yet which approach would actually be better. This is just a mess and very prone to miss some of the thousands kinds of process execution used in xend...

Anyway, I'm closing this as a dup of a real problem we have because of this.

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

Comment 3 Paolo Bonzini 2010-04-08 15:48:54 UTC

This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).

Comment 4 Chris Lalancette 2010-07-19 13:54:10 UTC

Clearing out old flags for reporting purposes.

Chris Lalancette