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] xen-3.3 missing xenbr0 new tmpbridge

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen-3.3 missing xenbr0 new tmpbridge
From: "Torsten" <tlehmann@xxxxxxxxxxxxx>
Date: Sun, 7 Dec 2008 20:30:49 +0100 (CET)
Delivery-date: Sun, 07 Dec 2008 11:39:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.9a

I should be read my article still another 2. time...
xenbr0 was renamed to eth0, but why?

On [3] "Xen 3.2+ Networking" written: "eth0 and eth1 are the bridge names..."
Me too find it is confusing.

[3] http://wiki.xensource.com/xenwiki/XenNetworking

it contains network-samples, but no config-examples and
predivide and disadvantages.

on xend-config.sxp written:

# To bridge network traffic, like this:
# dom0: ----------------- bridge -> real eth0 -> the network
#                            |
# domU: fake eth0 -> vifN.0 -+
# use
# (network-script network-bridge)
# The bridge is named xenbr0, by default.  To rename the bridge, use
# (network-script 'network-bridge bridge=<name>')


It seen to be description and working to drift apart.


- Test7 overwrite bridge-name

# diff xend-config.sxp.org xend-config.sxp
< (network-script network-bridge)
> #(network-script network-bridge)
> (network-script 'network-bridge bridge=xenbr0')

## network-bridge stop .. start || reboot

# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.0015c5be8f93       no              peth0

  -> not working

How must it are configured that xenbr0 showing as before version 3.2 ?

regards torsten

Xen-users mailing list