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] Re: RE : XEN Two NICS Two Bridges

To: lists@xxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, "Pozzi, Jean-Paul" <jean-paul.pozzi@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: RE : XEN Two NICS Two Bridges
From: Jorge Constán <jorqejcv@xxxxxxxxx>
Date: Mon, 16 Feb 2009 11:46:38 +0000
Cc:
Delivery-date: Mon, 16 Feb 2009 03:47:39 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=pLJWgrkJBaE/uIjWhCbhzURo9YZBwYjDni0MyPkneA0=; b=sJPVwbd+YaAZ3nIpXMxf2ms8nWBA8kYqRtYpWEfenAjAgBJGokRZ718//fPzIeh/me YGm3peCiTsTXc20Jefimuv9WpDe9HKiXTVDc6wyg9bOHaSGPp8UldGGY540f2elDlKfX sk68jufc8NKNjPmg4Scu506z+I9Kj2F2KJmwI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=chran4bDCYN3gScRWEWOJrbwGB+HULop8TubOX8DnAX+ydVccf94xLFe13/nGprf0I ocypZJRvhRZyCpjnQSRZn6YblHJ/uTuxSSUVEOb8vAg5Wi+wrjN4jo157x67KdX0PRXW 1Y2JRdM/niWf9ZXbOWExBGWsiLQBDgHdO3MYY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1234527919.24962.6.camel@ubu32>
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: <985DF29CD2B99849A9843282ADFCB19302E2A39E@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <adf2db0d0902120701h67f5d377q8cd112e7b71e7db6@xxxxxxxxxxxxxx> <1234473707.24429.4.camel@ubu32> <adf2db0d0902130349h124c4156h18e3fb726952d184@xxxxxxxxxxxxxx> <1234527919.24962.6.camel@ubu32>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Fixed!!!!!!!!!!

Thank you very much Thomas and Jean.

As you've show me, I proceeded to list the /etc/udev/rules.d/z25_persistent-net.rules file and use the MAC that appeared in associated to eth0. Then I added this MAC in the domu configuration file.

Now all domus works perfectly and  simultaneously.

Thanks for yours help.

There are folks in this world!!!!!!!!!!


2009/2/13 Thomas Halinka <lists@xxxxxxxxx>
Hi Jorge,

Am Freitag, den 13.02.2009, 11:49 +0000 schrieb Jorge Constán:
> Hi Thomas.
>
> Thank you very much for your help.
>
> Like you say, well, too many problems for only two bridges.
>
> I used the network-s2nics script that you gave me but it is the same
> as the previous ones.
>
> Ie, it creates perfectly bridges (see the bottom of the message), but
> domu can only use the card eth1 if I add the physical MAC in domu.cfg
> file.


The problem is udev - check:

cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules
file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x11ab:0x4363 (sky2)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:a0:d1:78:99:70",
ATTR{type}=="1", NAME="eth0"

Just rename your devices here to get eth0 as wanted. The Problem is, if
you _do_ not explicitly define a mac-address in domu-cfg, xen will
generate one on each startup of the domu, so your nic will become eth99
on the 98th startup ;)


>
> This not works:
> vif   = [ 'bridge=xenbr1' ]

should work - check "ifconfig -a" on domU

> The error is:
> .............................................................
> Configuring network interfaces...SIOCSIFADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> eth1: ERROR while getting interface flags: No such device
> Failed to bring up eth1.
> .............................................................
>
>
> This works:
> vif   = [ 'mac=00:13:72:57:7B:AF,bridge=xenbr1' ]
>
>
> In addition, if the domUs use the physical MAC, can not have
> simultaneous access to eth1.
>
> I think there is something obvious I am overlooking, but I do not know
> what it is.
>
>  /etc/xen/scripts/network-2nics status:
> ============================================================
> 6: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
>     link/ether 00:13:72:57:7b:ae brd ff:ff:ff:ff:ff:ff
>     inet 192.168.0.10/24 brd 192.168.0.255 scope global eth0
>     inet6 fe80::213:72ff:fe65:b6ae/64 scope link
>        valid_lft forever preferred_lft forever
> 13: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::200:ff:fe00:0/64 scope link
>        valid_lft forever preferred_lft forever
>
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.feffffffffff       no              vif0.0
>                                                         peth0
> xenbr1          8000.feffffffffff       no              vif0.1
>                                                         peth1
>                                                         vif4.0
>                                                         vif5.0
>
> 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.10
> 10.0.0.0/8 dev eth1  proto kernel  scope link  src 10.0.0.10
> default via 10.0.0.5 dev eth1
> default via 192.168.0.3 dev eth0
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref
> Use Iface
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
> 0 eth0
> 10.0.0.0        0.0.0.0         255.0.0.0       U     0      0
> 0 eth1
> 0.0.0.0         10.0.0.5        0.0.0.0         UG    0      0
> 0 eth1
> 0.0.0.0         192.168.0.3     0.0.0.0         UG    0      0
> 0 eth0
> ============================================================
> ============================================================
> 8: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
>     link/ether 00:13:72:57:7b:af brd ff:ff:ff:ff:ff:ff
>     inet 10.0.0.10/8 brd 10.0.0.255 scope global eth1
>     inet6 fe80::213:72ff:fe65:b6af/64 scope link
>        valid_lft forever preferred_lft forever
> 14: xenbr1: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::200:ff:fe00:0/64 scope link
>        valid_lft forever preferred_lft forever
>
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.feffffffffff       no              vif0.0
>                                                         peth0
> xenbr1          8000.feffffffffff       no              vif0.1
>                                                         peth1
>                                                         vif4.0
>                                                         vif5.0
>
> 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.10
> 10.0.0.0/8 dev eth1  proto kernel  scope link  src 10.0.0.10
> default via 10.0.0.5 dev eth1
> default via 192.168.0.3 dev eth0
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref
> Use Iface
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
> 0 eth0
> 10.0.0.0        0.0.0.0         255.0.0.0       U     0      0
> 0 eth1
> 0.0.0.0         10.0.0.5        0.0.0.0         UG    0      0
> 0 eth1
> 0.0.0.0         192.168.0.3     0.0.0.0         UG    0      0
> 0 eth0
> ============================================================
>
>
>
> 2009/2/12 Thomas Halinka <lists@xxxxxxxxx>
>         Hi together,
>
>         Only 2 bridges and so much trouble?
>
>         Do something like:
>
>         # vim /etc/xen/scripts/network-2nics
>
>         -----------snip------------------
>         #!/bin/bash
>         /etc/xen/scripts/network-bridge $1 netdev=eth0 bridge=xenbr0
>         vifnum=0
>         /etc/xen/scripts/network-bridge $1 netdev=eth1 bridge=xenbr1
>         vifnum=1
>         ---------------snap---------------
>
>         # chmod a+x /etc/xen/scripts/network-2nics
>
>         and put this as network-script into xend-config.sxp
>
>         Restart xend and your done
>
>         hth,
>
>         Thomas
>
>         Am Donnerstag, den 12.02.2009, 15:01 +0000 schrieb Jorge
>         Constán:
>
>         > Hello Jean.
>         >
>         > First of all thank you for your help.
>         >
>         > I followed your instructions. I used the network-multinet
>         script
>         > instead of the network-bridge (I download network-multinet
>         and xend
>         > script from
>         >
>         http://thepenguinpriest.com/linux/scripts/network-multinet.html).
>         >
>         > When I runs network-multinet script everything was fine but
>         only
>         > picked up the first physical card (eth0).
>         >
>         > I had to modify the xend script to seized the physical card
>         2. I
>         > modified this in xend script:
>         >
>         -----------------------------------------------------------------
>         >
>         > NETWORK_LIST="bridge,0,eth0,,,dhcp-off
>         bridge,1,eth1,,,dhcp-off"
>         >
>         > BRIDGE_NETDEV_LIST="eth0 eth1"
>         >
>         > LOCAL_BRIDGE_LIST=""
>         >
>         -----------------------------------------------------------------
>         >
>         > Now when I launch the network-multinet script believe that
>         is correct
>         > (two physical interfaces,two virtual bridge and two virtual
>         > interfaces). However when I launch the dums can not detect
>         the eth1
>         > (which is catching want for the network 10.0.0.0). Also if I
>         put the
>         > REAL mac.
>         >
>         > I do not know what else to do to get it working.
>         >
>         > Could you be kind enough to pass an instance of your
>         configuration?
>         >
>         > Thanks in advance.
>         >
>         >
>         > P.D. This is the result from network-multinet status:
>         >
>         > sever# /etc/xen/scripts/network-multinet status
>         >
>         > ============================================================
>         > Configuring Virtual Bridge: xenbr0
>         > using-  Physical Interface: eth0
>         >          Virtual Interface: vif0
>         > ============================================================
>         >
>         > ============================================================
>         > 6: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc
>         noqueue
>         >     link/ether 00:13:72:57:7b:ae brd ff:ff:ff:ff:ff:ff
>         >     inet 192.168.0.10/24 brd 192.168.0.255 scope global eth0
>         >     inet6 fe80::213:72ff:fe65:b6ae/64 scope link
>         >        valid_lft forever preferred_lft forever
>         > 21: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc
>         noqueue
>         >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>         >     inet6 fe80::200:ff:fe00:0/64 scope link
>         >        valid_lft forever preferred_lft forever
>         >
>         > bridge name     bridge id               STP enabled
>         interfaces
>         > xenbr0          8000.feffffffffff       no
>          vif0.0
>         >
>         peth0
>         > xenbr1          8000.feffffffffff       no
>          vif0.1
>         >
>         peth1
>         >
>         vif9.0
>         > xenbr2          8000.feffffffffff       no
>          vif0.2
>         > xenbr3          8000.feffffffffff       no
>          vif0.3
>         > xenbr4          8000.000000000000       no
>         >
>         > 192.168.0.0/24 dev eth0  proto kernel  scope link  src
>         192.168.0.10
>         > 172.22.0.0/16 dev veth2  proto kernel  scope link  src
>         172.22.0.1
>         > 172.23.0.0/16 dev veth3  proto kernel  scope link  src
>         172.23.0.1
>         > 10.0.0.0/8 dev eth1  proto kernel  scope link  src 10.0.0.10
>         > default via 10.0.0.5 dev eth1
>         > default via 192.168.0.3 dev eth0
>         >
>         > Kernel IP routing table
>         > Destination     Gateway         Genmask         Flags Metric
>         Ref
>         > Use Iface
>         > 192.168.0.0     0.0.0.0         255.255.255.0   U     0
>          0
>         > 0 eth0
>         > 172.22.0.0      0.0.0.0         255.255.0.0     U     0
>          0
>         > 0 veth2
>         > 172.23.0.0      0.0.0.0         255.255.0.0     U     0
>          0
>         > 0 veth3
>         > 10.0.0.0        0.0.0.0         255.0.0.0       U     0
>          0
>         > 0 eth1
>         > 0.0.0.0         10.0.0.5        0.0.0.0         UG    0
>          0
>         > 0 eth1
>         > 0.0.0.0         192.168.0.3     0.0.0.0         UG    0
>          0
>         > 0 eth0
>         > ============================================================
>         >
>         >
>         > ============================================================
>         > Configuring Virtual Bridge: xenbr1
>         > using-  Physical Interface: eth1
>         >          Virtual Interface: vif1
>         > ============================================================
>         >
>         > ============================================================
>         > 8: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc
>         noqueue
>         >     link/ether 00:13:72:57:7b:af brd ff:ff:ff:ff:ff:ff
>         >     inet 10.0.0.10/8 brd 10.0.0.255 scope global eth1
>         >     inet6 fe80::213:72ff:fe65:b6af/64 scope link
>         >        valid_lft forever preferred_lft forever
>         > 22: xenbr1: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc
>         noqueue
>         >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>         >     inet6 fe80::200:ff:fe00:0/64 scope link
>         >        valid_lft forever preferred_lft forever
>         >
>         > bridge name     bridge id               STP enabled
>         interfaces
>         > xenbr0          8000.feffffffffff       no
>          vif0.0
>         >
>         peth0
>         > xenbr1          8000.feffffffffff       no
>          vif0.1
>         >
>         peth1
>         >
>         vif9.0
>         > xenbr2          8000.feffffffffff       no
>          vif0.2
>         > xenbr3          8000.feffffffffff       no
>          vif0.3
>         > xenbr4          8000.000000000000       no
>         >
>         > 192.168.0.0/24 dev eth0  proto kernel  scope link  src
>         192.168.0.10
>         > 172.22.0.0/16 dev veth2  proto kernel  scope link  src
>         172.22.0.1
>         > 172.23.0.0/16 dev veth3  proto kernel  scope link  src
>         172.23.0.1
>         > 10.0.0.0/8 dev eth1  proto kernel  scope link  src 10.0.0.10
>         > default via 10.0.0.5 dev eth1
>         > default via 192.168.0.3 dev eth0
>         >
>         > Kernel IP routing table
>         > Destination     Gateway         Genmask         Flags Metric
>         Ref
>         > Use Iface
>         > 192.168.0.0     0.0.0.0         255.255.255.0   U     0
>          0
>         > 0 eth0
>         > 172.22.0.0      0.0.0.0         255.255.0.0     U     0
>          0
>         > 0 veth2
>         > 172.23.0.0      0.0.0.0         255.255.0.0     U     0
>          0
>         > 0 veth3
>         > 10.0.0.0        0.0.0.0         255.0.0.0       U     0
>          0
>         > 0 eth1
>         > 0.0.0.0         10.0.0.5        0.0.0.0         UG    0
>          0
>         > 0 eth1
>         > 0.0.0.0         192.168.0.3     0.0.0.0         UG    0
>          0
>         > 0 eth0
>         > ============================================================
>         >
>         >
>         > ============================================================
>         > xenbr4          8000.000000000000       no
>         > ============================================================
>         >
>         > ============================================================
>         > ============================================================
>         >
>         >
>         >
>         >
>         >
>         > 2009/2/11 Pozzi, Jean-Paul <jean-paul.pozzi@xxxxxxxxxxxxx>
>         >         Hello,
>         >
>         >         I use Xen servers 2 with XEN 3.0, 1 with XEN 3.2
>         with many
>         >         NICS and # 40 VMs.
>         >
>         >          In fact each server has 4 Nics on 4 different
>         subnets. I
>         >         encounter many problems with
>         >
>         >         the "standard" scripts until I find a "good" script.
>         You can
>         >         try the "network-multinet"
>         >
>         >         script which fit perfectly my use.
>         >
>         >         It can be found on Internet, if you cannot find it I
>         can send
>         >         it.
>         >
>         >
>         >
>         >         Regards
>         >
>         >         JP Pozzi
>         >
>         >
>         >
>         >         >Hello everyone.
>         >
>         >         >I just installed Xen 3.0.3 in a debian etch box.
>         >
>         >         >Linux server1.example.com 2.6.18-6-xen-686 #1
>         >
>         >         >This server1 has two real nic (eth0 with real MAC
>         >         00:13:72:57:7B:AE and eth1 with real
>         MAC00:13:72:57:7B:AF).
>         >
>         >         > I made a network-bridge custom like this:
>         >
>         >
>         >
>
>         > _______________________________________________
>         > Xen-users mailing list
>         > Xen-users@xxxxxxxxxxxxxxxxxxx
>         > http://lists.xensource.com/xen-users
>
>


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>