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

[Xen-users] Re: debian wheezy interface bonding (dom0) / xen 4.1.2*

To: Mark Schneider <ms@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: debian wheezy interface bonding (dom0) / xen 4.1.2*
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sun, 28 Aug 2011 13:18:21 +0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 28 Aug 2011 03:19:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E595E99.8050405@xxxxxxxxxxxxxxxxxxxxxx>
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: <4E595E99.8050405@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, Aug 27, 2011 at 11:16:09PM +0200, Mark Schneider wrote:
> Hello Pasi,
>
> Thank you for your hints due to my questions about interface bonding and  
> xen HVMs.
> I have commented out the network-script line in /etc/xen/xend-config.sxp  
> and tested a bit around (s. below):
> ### (network-script network-bridge)
> ### (network-script 'network-bridge netdev=bond0 antispoof=yes')
>
> I have tried to use "bridge_ports bond0" and activated config for bond0  
> but it didn't worked as I expected. *Would you expect that such  
> "bond0-config" also should work?*
>

You should do one step at a time.

First get the bond0 working without any Xen stuff.
When bond0 works from dom0, then add bond0 to the bridge.


> Maybe you would like to put some parts of my config into your wiki  
> xen-networking pages.
>
>
> auto xenbr0
> iface xenbr0 inet static
>     address 192.168.1.150
>     network 192.168.1.0
>     broadcast 192.168.1.255
>     netmask 255.255.255.0
>     gateway 192.168.1.1
>     bridge_ports eth0 eth2
>     #bridge_ports bond0
>

This looks dangerous. Having both eth0 and eth2 in the same
bridge could cause a loop in the network!



-- Pasi



> #auto bond1
> #iface bond1 inet static
> #    address 10.0.1.150
> #    netmask 255.255.255.0
> #    network 10.0.1.0
> #    broadcast 10.0.1.255
> #    gateway 10.0.1.1
> #    slaves eth1 eth3
> #    bond-mode active-backup
> #    #bond-mode 802.3ad
> #    bond-miimon 100
> #    bond-downdelay 200
> #    bond-updelay 200
>
> auto xenbr1
> iface xenbr1 inet static
>     address 10.0.1.150
>     network 10.0.1.0
>     broadcast 10.0.1.255
>     netmask 255.255.255.0
>     gateway 10.0.1.1
>     bridge_ports eth1 eth3
>     #bridge_ports bond1
>
>
> #auto xenbr0
> #iface xenbr0 inet static
> #    bridge_ports eth0 eth2
> #    address 192.168.1.150
> #    broadcast 192.168.1.255
> #    netmask 255.255.255.0
> #    gateway 192.168.1.1
>
> #auto xenbr1
> #iface xenbr1 inet static
> #    bridge_ports eth1
> #    address 192.168.1.151
> #    broadcast 192.168.1.255
> #    netmask 255.255.255.0
> #    gateway 192.168.1.1
> #
> #auto xenbr2
> #iface xenbr2 inet static
> #    bridge_ports eth2
> #    address 10.0.1.152
> #    broadcast 10.0.1.255
> #    netmask 255.255.255.0
> #    gateway 10.0.1.1
> #
> #auto xenbr3
> #iface xenbr3 inet static
> #    bridge_ports eth3
> #    address 10.0.1.153
> #    broadcast 10.0.1.255
> #    netmask 255.255.255.0
> #    gateway 10.0.1.1
>
> # ---
>
> root@xen411dom0:/ftp/HVM# brctl show
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.b499bac12736       no              eth0
>                                                         eth2
>                                                         vif4.0
>                                                         vif5.0
> xenbr1          8000.b499bac12738       no              eth1
>                                                         eth3
>                                                         vif5.1
>
> root@xen411dom0:/ftp/HVM# xm list
> Name                                        ID   Mem VCPUs      State    
> Time(s)
> Domain-0                                     0  1536     2     r-----     
> 527.2
> squeezehvm.born2b3.net                       4  8192     4     -b----     
> 14.9
> wheezyhvm.born2b3.net                        5  8192     8     -b----     
> 23.3
>
>
> Best regards,
> Mark
>
> -- 
> ms@xxxxxxxxxxxxxxxxxxxxxx
>

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