WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen creating two bridges

To: "Russell Horn" <albanach@xxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen creating two bridges
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Fri, 11 Jan 2008 07:05:45 -0700
Delivery-date: Fri, 11 Jan 2008 06:07:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I've found that I have better luck creating bridges when I use the bridge facilities built in to Linux instead of the XEN ones.  For example, on SuSE you can create an /etc/sysconfig/network/ifcfg-xenbr0 file and put configuration directives in this file that tell Linux which interface(s) to put in the bridge and even assign an IP or set DHCP on the bridge.  Most of my XEN servers have multiple VLANs - usually five or six, so I've found that doing this greatly simplifies the amount of configuration I have to do.
 
-Nick

>>> On 2008/01/10 at 19:51, "Russell Horn" <albanach@xxxxxxxxx> wrote:
Hi,

I'm trying to set up networking on a new machine.

I'm not getting any networking from the domU's

I notice that I have two bridges being created:

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:3024 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1802480 (1.7 Mb)  TX bytes:258 (258.0 b)

xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:44 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1232 (1.2 Kb)  TX bytes:468 (468.0 b)

Any idea why that would be?

/etc/xen/xend-config.sxp only contains this:

(xend-relocation-server yes)
(xend-relocation-hosts-allow '^localhost$')
(network-script 'network-bridge netdev=eth0')
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)

I'm configuring networking for the domU with this line:
vif=[ 'mac=00:16:3e:6a:b4:43', 'bridge=xenbr0' ]

Any idea why I'm seeing two bridges and if that might point to why I'm
not getting any network throughput on my virtual machines?

Thanks,

Russell


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