This doesn''t look good... Any ideas?
Martti
bonding: bond0: link status up for interface eth2, enabling it in 200 ms.
bonding: bond0: link status definitely up for interface eth2.
bonding: bond0: making interface eth2 the new active one.
RTNL: assertion failed at
/usr/src/xen-3.4.0/linux-2.6.18-xen.hg/net/ipv4/devinet.c (984)
Call Trace:
<IRQ> [<ffffffff803e231d>] inetdev_event+0x48/0x2a7
[<ffffffff803bafba>] rt_run_flush+0x7f/0xb8
[<ffffffff8023d0ea>] raw_notifier_call_chain+0x20/0x32
[<ffffffff803a093b>] dev_set_mac_address+0x53/0x59
[<ffffffff881cae36>] :bonding:alb_set_slave_mac_addr+0x3f/0x6a
[<ffffffff881cb2b7>] :bonding:alb_swap_mac_addr+0x90/0x160
[<ffffffff881c6134>] :bonding:bond_change_active_slave+0x1ea/0x303
[<ffffffff881c6d52>] :bonding:bond_select_active_slave+0xaf/0xdd
[<ffffffff881c735b>] :bonding:bond_mii_monitor+0x3ae/0x3fe
[<ffffffff881c6fad>] :bonding:bond_mii_monitor+0x0/0x3fe
[<ffffffff80238b01>] run_timer_softirq+0x188/0x231
[<ffffffff80352d4c>] evtchn_do_upcall+0x1b3/0x26f
[<ffffffff8023545d>] __do_softirq+0x89/0x115
[<ffffffff8020b2e8>] call_softirq+0x1c/0x28
[<ffffffff8020cd18>] do_softirq+0x60/0xf4
[<ffffffff8020ae1e>] do_hypervisor_callback+0x1e/0x2c
<EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff8020e7e2>] raw_safe_halt+0xb8/0xdd
[<ffffffff80209753>] xen_idle+0x6d/0x7f
[<ffffffff80209819>] cpu_idle+0xb4/0xf5
[<ffffffff8035146a>] force_evtchn_callback+0xa/0xb
# ifconfig bond0
bond0 Link encap:Ethernet HWaddr 00:15:17:91:02:19
inet addr:172.16.17.22 Bcast:172.16.17.255 Mask:255.255.255.0
inet6 addr: fe80::215:17ff:fe91:219/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:9000 Metric:1
RX packets:1255 errors:0 dropped:0 overruns:0 frame:0
TX packets:2940 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1854912 (1.7 MiB) TX bytes:238720 (233.1 KiB)
# cat /etc/network/interfaces
auto bond0
iface bond0 inet static
address 172.16.17.22
netmask 255.255.255.0
broadcast 172.16.17.255
mtu 9000
up /sbin/ifenslave bond0 eth2 eth3
down /sbin/ifenslave -d bond0 eth2 eth3
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Just as a clarification, bonding works without any problems when I''m using Xen 3.3.1 and the Debian 2.6.26-2-xen-amd64 kernel... Martti _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I had the same error on Xen 3.3.1 with 2.6.18.8 kernel. I got rid of this error by changing the mode to 0. Obviously there something wrong in 2.6.18''s bonding code (which according to some reports are fixed in RHEL/CentOS but not in the Xen tree). --- /etc/modprobe.d/arch-aliases 2009-06-08 13:44:18.000000000 +0300 +++ etc/modprobe.d/arch-aliases 2009-03-30 15:48:49.000000000 +0300 @@ -3,4 +3,4 @@ alias binfmt-0064 ia32_aout alias bond0 bonding -options bonding mode=0 miimon=100 downdelay=200 updelay=200 +options bonding mode=6 miimon=100 downdelay=200 updelay=200 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users