Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-users

[Xen-users] 2 nics in domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] 2 nics in domU
From: Roland Zimmermann <Roland.Zimmermann@xxxxxxxxxx>
Date: Thu, 29 Sep 2005 12:27:07 +0200
Delivery-date: Thu, 29 Sep 2005 10:25:03 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
User-agent: Thunderbird 1.4 (Windows/20050908)
Hi,

i didn't find any informations about the correct setup in xen to use more than 1 nic.

I have the latest xen-unstable running on RHAS4 with domU with RHAS3. If i configure to use only 1 nic (fix ip-address) xen works fine. However i need 2 nics configured in xenU. My approach was to create 2 bridges (1 points to eth0 and the other one to dummy0):

ifconfig looks like this:

dummy0 Link encap:Ethernet HWaddr CE:1F:17:EB:E5:60 inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
         UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:08:74:F6:1C:86 inet addr:140.86.194.94 Bcast:140.86.199.255 Mask:255.255.248.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:169941 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2592 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:23642265 (22.5 MiB)  TX bytes:275369 (268.9 KiB)

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:12 errors:0 dropped:0 overruns:0 frame:0
         TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:976 (976.0 b)  TX bytes:976 (976.0 b)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
         RX packets:177748 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2680 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:25276339 (24.1 MiB)  TX bytes:300080 (293.0 KiB)
         Base address:0xecc0 Memory:ff8e0000-ff900000

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
         RX packets:2592 errors:0 dropped:0 overruns:0 frame:0
         TX packets:169941 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:275369 (268.9 KiB)  TX bytes:23642265 (22.5 MiB)

vif4.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:51761 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vif4.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

xen-br0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
         RX packets:165862 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:19737926 (18.8 MiB)  TX bytes:0 (0.0 b)

xen-br1 Link encap:Ethernet HWaddr CE:1F:17:EB:E5:60 inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

The bridges are showed up like this:

bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.feffffffffff       no              vif0.0
                                                       peth0
                                                       vif4.1
xen-br1         8000.ce1f17ebe560       no              dummy0
                                                       vif4.2

on start of the domU i create the vif-bridges.

If i specify only 1 ip-address (and nic=1) in config-file everything works fine (of course only 1 nic). However as soon as i try to specify 2 nics i have no network at all. Here my question: What is the correct syntax to provide more than 1 ip-address, netmask, etc in the conf-file?

I tried another approach by configuring the 2nd nic in domU directly (/etc/sysconfig/network-scripts/ifcfg-eth1). This works, however it has some odd side-effects (wrong routing tables,etc). Moreover, based on the concept of xen i don't think this is the correct way...

Any help is highly appreciated...

cheers,

Roland

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] 2 nics in domU, Roland Zimmermann <=