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-users] How does one create a bridge interfaces in dom0 without IPs?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] How does one create a bridge interfaces in dom0 without IPs?
From: Freddie Cash <fjwcash@xxxxxxxxx>
Date: Wed, 9 Apr 2008 10:04:58 -0700
Delivery-date: Wed, 09 Apr 2008 10:05:45 -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: KMail/1.9.7
I have a Debian Etch box running with Linux kernel 2.6.18 and Xen 3.0.3.  
On that box, in dom0, I have three active interfaces, eth0, eth1, and 
eth2.  However, only eth2 has an IP (this is the management interface).

eth0 and eth1 are simply "up" ("iface eth0 inet manual" 
in /etc/network/interfaces).

I have a custom network-bridge script with the following:
/etc/xen/scripts/network-bridge $1 vifnum=0 bridge=xenbr0 netdev=eth0
/etc/xen/scripts/network-bridge $1 vifnum=1 bridge=xenbr1 netdev=eth1

which creates xenbr0 and xenbr1 at boot, attached to eth0 and eth1 

My domUs are configured to use xenbr0 or xenbr1.  Everything works great!  
The physical interfaces, the vif0.X interfaces, and the bridge interfaces 
all have the same numbers and match up nicely (eth0, peth0, vif0.0, 
xenbr0 all link together).

I have an Ubuntu Hardy box running with Linux kernel 2.6.24 and Xen 3.2, 
and I cannot replicate this setup.  The included network-bridge script no 
longer accepts any parameters except "start/stop" and doesn't seem to 
create bridges for interfaces without IPs in dom0.

How can I replicate the bridge setup that I have on my Xen 3.0 box, where 
bridges are created at boot on all the interfaces that are marked "up"?

I want eth0 to be the management interface with an IP in dom0 only.  And I 
want eth3 through eth6 to be bridged interfaces with no IPs in dom0, just 
up and running so I can attach the different domUs to the different 
bridges.  Ideally, I'd also like to name the bridges something other than 

I've tried using the included network-bridge script, but it doesn't seem 
to work on interfaces without IPs, and it (or xend) is not linking the 
vif0.X numbers with the interfaces numbers (vif0.0 is linked to eth3 for 

I've tried using a wrapper around network-bridge that passes parameters, 
and another that exports env variables.  No go.

I've tried creating the bridges automatically via /etc/network/interfaces, 
and manually.  I can get either the domUs to connect or the dom0 to 
connect to the network, but not both at the same time.

What am I missing?  How does one create bridges for the domUs to use 
without wasting a bunch of IPs for the dom0?

Freddie Cash

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>