https://bugzilla.novell.com/show_bug.cgi?id=419095 User schueffler@softgarden.de added comment https://bugzilla.novell.com/show_bug.cgi?id=419095#c1 --- Comment #1 from Stefan Schueffler 2008-08-21 01:42:37 MDT --- Created an attachment (id=234646) --> (https://bugzilla.novell.com/attachment.cgi?id=234646) config-file of eth0. eth1 is analogous -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=419095 User schueffler@softgarden.de added comment https://bugzilla.novell.com/show_bug.cgi?id=419095#c3 --- Comment #3 from Stefan Schueffler 2008-09-01 08:03:53 MDT --- Hi, after some experiments on this issue, the situation is as follows: using openSUSE 10.3, the yast2-network-bonding-setup shows as "slaveable" interfaces all nics having bootproto=none, and startmode=off. using openSUSE 11.0, the setup only shows the nics for which no configuration exists at all, and furthermore only then when there is no configuration having bootproto=none and startmode=off on any (other) nic in the same pc. if someone has trouble to understand my english, i gladly could explain this issue in my native language - german. regards Stefan Schueffler -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=419095 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=419095#c4 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mzugec@novell.com |jfehlig@novell.com --- Comment #4 from Michal Zugec 2008-09-15 00:34:17 MDT --- Ok, so YaST issue is away. Jim could you comment second part (replacong bond by pbond in xen)? But in my personal opinin we have documentation for that ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=419095 User schueffler@softgarden.de added comment https://bugzilla.novell.com/show_bug.cgi?id=419095#c6 --- Comment #6 from Stefan Schueffler 2008-09-16 09:43:37 MDT --- Hi after removing the invocation of network-script in xend-config.sxp, i'm now able to boot the dom0 having bonding enabled. Unfortunately, i'm not able to create a bridge having this bond0-interface attached. Using yast2 -> network-settings-> add -> network bridge, it shows me those interfaces as options for "bridged devices": eth0 eth1 bond0 (configuration exists) Now, when i add the bond0 to this bridge and press "next", yast2 shows an error-screen stating that "there is already a configuration for bond0. Either cancel or remove this configuration." This shows up regardless of the chosen address-setup for the bonding interface (e.g. dhcp, none, statically). Now, canceling obviously does not create a bridge, and removing the configuration for bond0 obviously removes the bonding- configuration at all... How can i create the bridge and add the bond-interface to this bridge? Is this an error in my understanding or usage of the yast2-tool, or is there an error in the tool itself? thanks, regards Stefan Schüffler -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=419095 User llipavsky@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=419095#c9 --- Comment #9 from Lukas Lipavsky 2008-09-22 07:56:29 MDT --- There are several yast issues here, marked as *bugN* in the text: Problem 1: described in comment 3 When new bonding device is created/edited, it allows only unconfigured devices to be added to the bond. Other devices - especially those configured to be bonding slaves - aren't shown on the list (*bug1*). This list should definitely include devices that are configured as bonding slaves (no IP address) as well! And when device is set to be bonding slave for some bond, it should be configured as bonding slave and not remain unconfigured(*bug2*). Another bug - as described in comment 3 - is that no device are shown in bonding-slaves list when any device has configuration set to 'no IP address'(*bug3*). Problem 2: described in comment 6 The device that is bridged should have ip 0.0.0.0/24 (as described in http://en.opensuse.org/YaST/Network/11.0-bridge). (BTW This is first problem since it should be 'no IP address' configuration instead of 0.0.0.0/24 which is weird. *bug4*) If it has different configuration, yast will inform you that it's configuration will be *removed*. And removes it. Together with bonding device since it's pure virtual - *bug5*. When the yast finish, the bond configuration is gone, thus the bridge has nothing to connect with, and is unusable. If the bond0 is set up with ip 0.0.0.0/24 bridge can be successfully created... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=419095 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=419095#c11 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trinh.dao@hp.com --- Comment #11 from Michal Zugec 2008-10-03 04:15:33 MDT --- *** Bug 431068 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=431068 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.