[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] getting multiple network interfaces to work in 3.2

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Tomoki Taniguchi" <tomoki.taniguchi@xxxxxxxxx>
  • Date: Wed, 14 May 2008 01:30:08 +0900
  • Delivery-date: Tue, 13 May 2008 09:30:41 -0700
  • 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=eDPnezrOWiUnNOG0ggR9syBBrG2dJwcrhO/w5qxUjDXFRhARi+XGZrtqt3CBo+1+LW3KmIRJo4/1tI28SBeiNgKhAln5g3LHLbUNItjRafAMcF/Soy8WNDXfPv20E3k/N/BXf2qQR0UAGvhS/Y4+S2uqQQgMU6AQjeHKqna5D3Q=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I have a couple of Xen 3.1 servers running on Ubuntu 7.10 AMD64 Server machines.

I decided to to upgrade these machines up to the latest release of
Ubuntu (8.04 LTS)
which upgrades Xen to version 3.2.

I upgraded the first machine, installed the xen component.
these machines all have two network interfaces one connected to the
WAN and the other
to the local LAN network.  In a tutorial i read a while back it
mentioned that in order to
get both interfaces available to the domUs i need to setup a wrapper
script and call it
instead of the standard network-bridge script.

i wrote a script called multi-network-bridge
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 bridge=xenbr0 netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1 netdev=eth1
which works for the current xen 3.1 installation
but on the new xen 3.2 installation it cause problems
dom0 is no longer accessible via the network.

i read about a bug in the 8.04 kernel for xen,
so i updated to the patched kernel listed in
hoping that this will fix the issue, but no luck.

now i am starting to suspect the the way i am calling the network-bridge
in the wrapper script maybe wrong.

did something change in the way network-bridge script is called from 3.1 to 3.2?

Tomoki Taniguchi

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.