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] multiple interface issues

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] multiple interface issues
From: "McFadden, Gordon" <gordon_mcfadden@xxxxxxxxx>
Date: Thu, 29 Jun 2006 14:46:59 -0700
Delivery-date: Thu, 29 Jun 2006 14:48:21 -0700
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
Thread-index: AcabxCHqtYUFW5CiTXeYzespbPYrgw==
Thread-topic: multiple interface issues

 

 

Hi All

 

I am struggling to get two interfaces up in a domU.

I have read lots about this, and have gotten quite far along.

 

I have two bridges

 

[root@irir301-serial5-0-518-point-to-point xen]# brctl show

bridge name     bridge id               STP enabled     interfaces

xenbr0          8000.feffffffffff       no              peth0

                                                        vif0.0

xenbr1          8000.feffffffffff       no              peth1

                                                        vif0.1

 

configured on two physical interfaces.

 

My virtual interfaces seem ok:

 

eth0      Link encap:Ethernet  HWaddr 00:0E:0C:9F:F9:F8 

          inet addr:134.134.158.167  Bcast:134.134.158.255  Mask:255.255.255.0

          inet6 addr: fe80::20e:cff:fe9f:f9f8/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:11414 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1609 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:1352662 (1.2 MiB)  TX bytes:249154 (243.3 KiB)

 

eth1      Link encap:Ethernet  HWaddr 00:15:F2:AE:EF:28 

          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::215:f2ff:feae:ef28/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:0 (0.0 b)  TX bytes:636 (636.0 b)

 

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:48 errors:0 dropped:0 overruns:0 frame:0

          TX packets:48 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:9821 (9.5 KiB)  TX bytes:9821 (9.5 KiB)

 

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1

          RX packets:11652 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1723 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:100

          RX bytes:1469293 (1.4 MiB)  TX bytes:273758 (267.3 KiB)

          Base address:0x9c00 Memory:f46e0000-f4700000

 

peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 

          UP BROADCAST NOARP 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:1000

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

          Interrupt:19

 

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1611 errors:0 dropped:0 overruns:0 frame:0

          TX packets:11420 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:249486 (243.6 KiB)  TX bytes:1353150 (1.2 MiB)

 

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 

          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:10 errors:0 dropped:0 overruns:0 frame:0

          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:636 (636.0 b)  TX bytes:846 (846.0 b)

 

xenbr0    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:8110 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:939119 (917.1 KiB)  TX bytes:468 (468.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:10 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:496 (496.0 b)  TX bytes:468 (468.0 b)

 

 

The virtual interface entry in my confile seems ok to me.

 

vif = [ 'mac=00:16:3e:00:00:13, bridge=xenbr0', 'mac=00:16:3e:00:01:27, bridge=xenbr1' ]

 

But when I boot my user domain, I see no interfaces.  If I shorten the vif entry to indicate only one interface, that one will work.

Ie

vif = [ 'mac=00:16:3e:00:00:13, bridge=xenbr0'] does generate aneth0 in my domU.

 

It seems like the xm create accepts but does not process correctly the vif entry with two interface spec.  But I have seen this used over and over in examples.

 

Am I missing something?

 

We are using Xen 3.0.2 on FC4 for the host if that is relavent.

 

Thanks

 

Gord

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] multiple interface issues, McFadden, Gordon <=