Bug 213559
Summary: | bonding does not work with xen kernel | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | jordan hargrave <jordan_hargrave> |
Component: | xen | Assignee: | Herbert Xu <herbert.xu> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 5.0 | CC: | jfeeney, mbrodeur, wwlinuxengineering, xen-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kernel-xen-2.6.18-1.2747.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-29 14:33:38 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: | |||
Bug Blocks: | 189473, 200812 |
Description
jordan hargrave
2006-11-01 23:25:49 UTC
Another xen bonding thread: http://lists.xensource.com/archives/html/xen-bugs/2006-09/msg00000.html Crictical bug. Changing severity. Raised priority and added ACK flags for approval into rhel5. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Dell wants to make sure we do not come back later and tell them that we do not support bonding with Xen Kernel. I have assured them that this is being looked at will be assigned to an engineer for evaluation into RHEL5.1. > will be assigned to an engineer for evaluation into RHEL5.1.
Sammy- You surely mean RHEL 5.0 ??
Yes, I was looking for this comment and I see that Amit has caught this mistyping :-). RHEL 5.0 it is. Perhaps because I am extremely literal, I got a confused when I read the entire bug description because I thought it was describing multiple bugs. I checked with Dell and determined that the scope of this bugzilla should be limited to just the behavior described in the "Description of problem" and perhaps the first two "threads" listed under "Additional Info". Thus the bug descripton should be "ping does not work when you bond and bridge due to a problem with the default bridging script". All additional "threads on xen bonding" (from Sébastien Cramatte et al.) should be considered superfluous to the issue at hand. I hope this clarifies the issue. Deferring QE ack until we scope the necessary work. Could you please show me the output of ifconfig before you start xend and the output afterwards? Thanks. Appears that this issue has been resolved with Beta2 code drop. All of the preliminary testing is positive. Issue can be marked as MODIFIED. Thanks! Dell verified fix. Requesting RH to close. I wonder whether this is really fixed. There is no mentioning of (bond|enslave) anywhere in beta2's xen, and renaming the bond0 device will drop the slaves and needs re-enslaving. Unfortunately my RHEL5 test systems are not capable of bonding, but the issue persist on FC6 (bug #189473) and also rawhide. The only fix I can imagine that wouldn't involve doing reenslaving in xen scripts is that renaming the bond device does not lose its slave anymore. Is that the case? If so, where exactly is the fix, so I can use it in Fedora? |