On Fri, Feb 24, 2006 at 06:28:20PM -0500, Bill Nottingham wrote:
Axel Thimm (Axel.Thimm(a)ATrpms.net) said:
> I'm having a hard time getting bonding to work on FC5t3.
Not surprising. The way Xen does its bridging breaks bonding
It's possible it could be fixed in the xen scripts, but I don't
think it's been looked at.
I now jumped into the xen networking concepts. These make sense, but
there are two issues:
a) bonding should be performed onto the "physical" bonding interface,
which xen renames to pbond0. Still the initscripts only work with
MASTER=pbond0 if called *after* completion of the boot process.
b) even if a) is fixed and requires MASTER=pbond0 setting, the
switching from a xen kernel to a non-xen kernel the
configuration in the initscripts would be bogus (pointing to
a nonexisting pbond0), and the bonding device would be w/o slaves.
I don't understand why a) happens, seems to be dependent on the order
of the steps performed. Maybe the bonding/enslaving (at boot time)
happens before xen renames the bond0 device and later on the enslaving
is wrong. Reruning the ifup scripts sees the renamed devices and
performs properly. That's a theory at least.
I'm not sure how to solve b). Ideally one would like to not have xen
specific actions in initscripts, but otherwise one risks cutting of
the system of the net completely when upgrading kernels and booting
into the wron one. Probably not something one wants when setting up
bonding to ensure network availability. ;)
Should I file a bugzilla? xen or initscripts?
Axel.Thimm at ATrpms.net