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/
Home Products Support Community News


[Xen-bugs] [Bug 381] New: new network scripts does not work for two brid

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 381] New: new network scripts does not work for two bridges topology
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 02 Nov 2005 18:47:46 +0000
Delivery-date: Wed, 02 Nov 2005 18:47:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: new network scripts does not work for two bridges
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: lge@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx,niv@xxxxxxxxxx,pl@xxxxxxxxxx

Changeset:  7572:ea6d9f29dff5
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Mon Oct 31 08:07:14 2005 +0100
summary:     Watch events may get lost, the xenstored response races against 
the new


I tried the two bridges topology by following the exact steps Ewan suggested,
but I could not get it work.

dom0: fake eth0 -> vif0.0 ----------------------------+
dom0: fake eth1 -> vif0.1 ---+                        |
                            |                        |
                            |                       bridge 0 -> real eth0
                            |                        |
                           bridge 1 -> real eth1     |
                            |                        |
                            |                        |
domU: fake eth0 -> vifN.0 ----------------------------+
domU: fake eth1 -> vifN.1 ---+

then you need to create a wrapper script:

(network-script my-network-script)

and in /etc/xen/scripts/my-network-script:

dir=$(dirname "$0")
"$dir/network-bridge" vifnum=0 start
"$dir/network-bridge" vifnum=1 start

Here are the lines uncommented in my xend-config.sxp

(xend-http-server yes)
(xend-relocation-server yes)
(xend-address localhost)
(xend-relocation-address localhost)
(network-script my-network-script)
(dom0-min-mem 0)
 (dom0-cpus 0)
I've also tried to start network-bridge manually. But still it does not look 

Please see the detailed info (brtcl show, ifconfig, route, iptables -L, trace
output) in the attached file.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 381] New: new network scripts does not work for two bridges topology, bugzilla-daemon <=