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


Re: [Xen-users] Problem with Xen bridge on Debian Lenny

To: Antoine Benkemoun <antoine.benkemoun@xxxxxxxxx>
Subject: Re: [Xen-users] Problem with Xen bridge on Debian Lenny
From: Olivier Le Cam <Olivier.LeCam@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 22 Apr 2009 12:44:36 +0200
Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 22 Apr 2009 03:45:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fc1cbedb0904220243v7fd4636k45050253b8e4dbd9@xxxxxxxxxxxxxx>
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>
References: <fc1cbedb0904220243v7fd4636k45050253b8e4dbd9@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20090302)
Bonjour Antoine,

Antoine Benkemoun wrote:
Now the killer problem... When I boot into Xen everything works fine except... the networking. The interface that was recognized as eth0 when I was with Debian (no Xen) now become eth1 for some unknown reason. The line responsible for this is the following :

/tpxen kernel: udev: renamed network interface eth0 to eth1/

I guess that xend does reconfigure your network during the boot sequence and the new interface might be detected as different. You can probably deal with this in:

So in Xen I have eth1. I enabled /(network-script network-bridge) /as well as /(vif-script vif-bridge)/. No bridge appears and no vif interfaces, no nothing except eth1 and lo.

I personnaly prefer not to change anything in xend-config.sxw in order to ease future dist-upgrade.

Actually, there is -- in my knowledges -- at least two ways to get the domUs bridged to the dom0 interface with Debian. The one you describe (which I faced many times problems with) is one of them. Another one is to let xend-config as is it (aka /(network-script network-dummy)/ and /(vif-script vif-bridge)/) and to configure the bridges at the network level. Here is my /etc/network/interface:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto xenbr0
iface xenbr0 inet static
        bridge_ports eth0
        bridge_stp off
        bridge_maxwait 0
# dns-* options are implemented by the resolvconf package, if installed
        dns-search my-domain.tld

When you boot your dom0, it will have xenbr0 instead of eth0. DomUs will work as usual and the "eth0" of each domU will be bridged to xenbr0. This is *IMO* the best way to configure Xen in bridge-mode on Debian.


Olivier Le Cam

Xen-users mailing list

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