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.2 change in bridge behavior is causing problems

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen 3.2 change in bridge behavior is causing problems
From: "Tomoki Taniguchi" <tomoki.taniguchi@xxxxxxxxx>
Date: Tue, 1 Jul 2008 18:17:59 +0900
Delivery-date: Tue, 01 Jul 2008 02:18:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=sKvkTALkn7fGWdcVQooNhXLhX9x0M8UwwxvTC4tNAEg=; b=hfViPgfnOtGB0E2UqD+/s9gllfBGwKcXZgs7nmsqQpJYONfx6Gdq1v1CVxqNDd0RZX 0f8F5biH0SxBfGRad6oF/XDbAQD+syeJY97F8aXLgSReaceBDiEcp+biYe0TkZONErH2 mx1w6nY893RzUwpnAuViMl4//xL3KJ4uqQz+w=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=nGGooGGK0+WkJHs3SRZ1PBIjudy3hCJ7oBv/8H+ukU9+CV/Xm20bNjQ4tm12ZI9ZSR w4zjibGll8cB9inzzhOnKC8AkZsDhNGD3LzFVbUg2BXnkg6CCf/Dykzg28WP2vVYe1u0 p5vRxyDNAGMkRaRbs4EFb6DprMqB+EUMy6n0M=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
i have recently upgraded one of my xen servers from running ubunty
7.10 (gutsy) to ubuntu 8.04 (hardy)
to test xen 3.2 prior to upgrading the rest of the xen 3.1 servers.

my servers have 2 interfaces
eth0 is attached to the lan
eth1 is attached to the wan

on xen 3.1 to create the bridges for domUs i would run the following script

dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 bridge=xenbr0 netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1 netdev=eth1

which created a seperate bridge interfaces
xenbr0 and xenbr1 apart from the eth0 and eth1

the domU was able to access the eth1 interface via xenbr1
even if  the dom0s eth1 was not up.

but since switching to 3.2 i have heard the behavior has cahnged and
xenbr are no longer created
and that the interface name equals the bridge name.  so i have
modified my script to the following

dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 bridge=eth0 netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 bridge=eth1 netdev=eth1

domUs have no problem accessing the LAN (eth0),
but i have been having lots of problems with the domUs accessing the WAN (eth1)

what i have come to realize is that since i don't set eth1 to up on
the dom0 (don't want to be able to access the xen server itself from
the WAN)
eth1 remains in the down state.

this wasn't a problem when the bridge interface was seperate,
but now that eth1 is the bridge interface as well as the eth1
interface for dom0,
i have to specifically call "ifconfig eth1 up" on boot to allow my
domUs to access eth1

is there some way to avoid this?

is there some way to have xenbr0 and xenbr1 seperate from eth0 and eth1?

Tomoki Taniguchi

Xen-users mailing list

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