[Xen-changelog] Diagnostic for hitting the nloopbacks limit. This is presumably the cause of

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User emellor@xxxxxxxxxxxxxxxxxxxxxx
# Node ID a4bff55d4a16b1cf60360331d31cca7128878f54
# Parent  ecb5997f7b259dd3180627d68544430022ee3deb
Diagnostic for hitting the nloopbacks limit.  This is presumably the cause of
all the "two bridges don't work" bugs that have been reported (bug #381).

Consideration will be given to raising the default limit -- this is just a
diagnostic of the problem.

Signed-off-by: Ewan Mellor <ewan@xxxxxxxxxxxxx>

diff -r ecb5997f7b25 -r a4bff55d4a16 tools/examples/network-bridge
--- a/tools/examples/network-bridge     Mon Nov  7 11:36:16 2005
+++ b/tools/examples/network-bridge     Mon Nov  7 11:36:35 2005
@@ -195,11 +195,17 @@
        return
     fi
 
+    if ! ip link show 2>/dev/null | grep -q "^[0-9]*: ${vdev}"; then
+        echo "
+Link $vdev 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>).
+" >&2
+        exit 1
+    fi
+
     create_bridge ${bridge}
-
-    if ! ip link show 2>/dev/null | grep -q "^[0-9]*: ${vdev}"; then
-       return
-    fi
 
     if ip link show ${vdev} 2>/dev/null >/dev/null; then
        mac=`ip link show ${netdev} | grep 'link\/ether' | sed -e 's/.*ether 
\(..:..:..:..:..:..\).*/\1/'`

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