WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] SLES10 SP1 - xen bridges break after update

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] SLES10 SP1 - xen bridges break after update
From: Fred Blaise <fred.blaise@xxxxxxxxxxx>
Date: Fri, 29 Jun 2007 12:06:50 +0200
Delivery-date: Fri, 29 Jun 2007 03:05:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.12 (X11/20060911)
Hello all,

I upgraded a SLES10 to SP1 yesterday, xen-3.0.4_13138-0.40.

I have dot1q setup there, 3 physical interfaces (eth0, eth6 and eth7)
each one on a different vlan.

I have this custom network-bridge script, common one, called from
xend-config.xsp:

#!/bin/bash

dir=$(dirname "$0")
"$dir/network-bridge" "$@" netdev=eth0 vifnum=0
"$dir/network-bridge" "$@" vifnum=6 bridge=devnw netdev=eth6
"$dir/network-bridge" "$@" vifnum=7 bridge=testnw netdev=eth7

At server reboots, no bridge at all comes up. If I launch it manually
afterwards, I get:

bornem2:~ # /etc/xen/scripts/custom-network-script start
    eth0      device: Intel Corporation 82547GI Gigabit Ethernet Controller
    eth0      configuration: eth-id-00:04:23:b8:1b:8a
    eth0      IP address: 172.17.8.14/24
    eth0      device: Intel Corporation 82547GI Gigabit Ethernet Controller
    eth0      configuration: eth-id-00:04:23:b8:1b:8a
Nothing to flush.
Nothing to flush.
Waiting for peth0 to negotiate link...    eth0
    eth0      configuration: eth-id-00:04:23:b8:1b:8a
    eth0      IP address: 172.17.8.14/24

Link veth6 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the
parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.


Link veth7 is missing.
This may be because you have reached the limit of the number of
interfaces BLA BLA BLA

I am allowed up to 64 loopbacks, so this isn't the problem.

ifconfig looks like this, after launching the script manually:

bornem2:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:04:23:B8:1B:8A
          inet addr:172.17.8.14  Bcast:172.17.8.255  Mask:255.255.255.0
          inet6 addr: fe80::204:23ff:feb8:1b8a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2020 errors:0 dropped:0 overruns:0 frame:0
          TX packets:251 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1591615 (1.5 Mb)  TX bytes:37402 (36.5 Kb)

eth6      Link encap:Ethernet  HWaddr 00:0D:88:70:E1:ED
          inet6 addr: fe80::20d:88ff:fe70:e1ed/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1480 (1.4 Kb)  TX bytes:960 (960.0 b)
          Interrupt:22 Base address:0xb800

eth7      Link encap:Ethernet  HWaddr 00:0D:88:70:E1:EC
          inet6 addr: fe80::20d:88ff:fe70:e1ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1792 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:108037 (105.5 Kb)  TX bytes:960 (960.0 b)
          Interrupt:21 Base address:0xbc00

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5450 (5.3 Kb)  TX bytes:5450 (5.3 Kb)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:26906 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42138 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:4683437 (4.4 Mb)  TX bytes:55161554 (52.6 Mb)
          Base address:0xac00 Memory:fc4e0000-fc500000

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:251 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2020 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:37402 (36.5 Kb)  TX bytes:1591615 (1.5 Mb)

vif5.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:39157 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30386 errors:0 dropped:74 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:73187258 (69.7 Mb)  TX bytes:4739158 (4.5 Mb)

vif8.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:5433 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16816 errors:0 dropped:648 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:501722 (489.9 Kb)  TX bytes:20133414 (19.2 Mb)

vlan503   Link encap:Ethernet  HWaddr 00:0D:88:70:E1:EC
          inet6 addr: fe80::20d:88ff:fe70:e1ec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:492 (492.0 b)

vlan504   Link encap:Ethernet  HWaddr 00:0D:88:70:E1:ED
          inet6 addr: fe80::20d:88ff:fe70:e1ed/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:492 (492.0 b)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:890 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:36620 (35.7 Kb)  TX bytes:0 (0.0 b)


Well, has anyone seen this yet? What other info can I provide you guys
to better understand the problem? It worked perfect on SLES10 without SP1...

Thanks a lot.

fred

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] SLES10 SP1 - xen bridges break after update, Fred Blaise <=