I'm using Fedora 4 and wound up fixing it manually for now, if we decide to keep xen we'll write a boot script to do it.
Basically, both bond0 and pbond0 must be active at the same time, so leave your bond0 setup as is. Copy /etc/sysconfig/network-scripts/ifcfg-bond0 to ifcfg-pbond0 and rename the Device value (not sure this step is necessary).
Reboot and on bootup, do:
sudo ifconfig pbond0 (IP address) network (255.255.255.x) broadcast (your address)
sudo ifenslave pbond0 eth0
sudo ifenslave pbond0 eth1
The 3 addresses above are the same as used by bond0.
| Axel Thimm <Axel.Thimm@xxxxxxxxxx>
Sent by: fedora-xen-bounces@xxxxxxxxxx 04/20/06 08:15 AM
|
|
Hi,
I'm retrying to get bonding and xen working with FC5:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189473
The summary is that
o xend at boot time does not attach anything to xenbr, the network is
other than the added broken xenbr unaltered. So at least booting
into kernel-xen0 doesn't hook you off the wire anymore (as it was
with FC5t3)
o after calling xend restart the bridge is almost properly set up,
only the slaves of the bond interface get lost in the process
Anyone know how to fix/workaround these issues?
Thanks!
--
Axel.Thimm at ATrpms.net
--
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
Attachment:
att24w91.dat
Description: Binary data
