Xen users - May 2008 - getting multiple network interfaces to work in 3.2

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
<snip>
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 bridge=xenbr0
netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1
netdev=eth1
<snip>
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
http://howtoforge.com/ubuntu-8.04-server-install-xen-from-ubuntu-repositories
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?


TIA,
Tomoki Taniguchi

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, May 13, 2008 at 12:30 PM, Tomoki Taniguchi <
tomoki.taniguchi@gmail.com> wrote:
> 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 wrote a script called multi-network-bridge
>
> did something change in the way network-bridge script is called from 3.1
> to 3.2?
>
The default bridge devices are now ethX instead of xenbrX.

Try brctl show to verify for your setup.

Cheers,
Todd


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users