Axel Thimm (Axel.Thimm(a)ATrpms.net) said:
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.
Correct.
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?
Ideally, xen shouldn't be mucking with networking that much. It
does it because of some supposed race.
Bill
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list