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] Xen 3.3.0 on Gentoo Kernel 2.6.18, Bridge-Setup Problems

To: <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Xen 3.3.0 on Gentoo Kernel 2.6.18, Bridge-Setup Problems
From: "Andreas Westermaier" <andreas.westermaier@xxxxxx>
Date: Mon, 17 Nov 2008 15:09:30 +0100
Cc:
Delivery-date: Mon, 17 Nov 2008 06:10:00 -0800
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/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>
Reply-to: andreas.westermaier@xxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclIvhvbdWaSuIr5Rvi3c+i3bwiu2g==
Hi,

I'm new to this list. The last days I messed a bit around with Xen on Gentoo 
(2.6.18, emerged xen-sources) and after disabling IPv6 support in the kernel I 
also got the network-bridge script almost working I think. There are no error 
messages anymore.

Reading the Xen Wiki [1] I found that the network-bridge script should perform 
the following actions:
1. creates a new bridge named xenbr0
2. "real" ethernet interface eth0 is brought down
3. the IP and MAC addresses of eth0 are copied to virtual network interface 
veth0
4. real interface eth0 is renamed peth0
5. virtual interface veth0 is renamed eth0
6. peth0 and vif0.0 are attached to bridge xenbr0
7. the bridge, peth0, eth0 and vif0.0 are brought up

In my case it successfully creates the bridge xenbr0 and renames the real 
interface eth0 to peth0. ifconfig shows up:

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:64 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4096 (4.0 KiB)  TX bytes:4096 (4.0 KiB)

peth0     Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:100766 errors:0 dropped:0 overruns:0 frame:0
          TX packets:91552 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:48721126 (46.4 MiB)  TX bytes:85752042 (81.7 MiB)
          Interrupt:16 Memory:f8000000-f8011100

xenbr0    Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
          inet addr:192.168.0.84  Bcast:192.168.1.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:71132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:73847 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3392032 (3.2 MiB)  TX bytes:84049770 (80.1 MiB)

xenbr0 and peth0 have the same mac addresses. No new (virtual) eth0 and vif0.0 
device is created (also verified by trying to get them manually up with 
'ifconfig XXX up').

My xend-config.sxp looks like this:

(network-script 'network-bridge netdev=eth0 bridge=xenbr0 vifnum=0')
(vif-script vif-bridge)
(dom0-min-mem 196)
(enable-dom0-ballooning yes)
(dom0-cpus 0)


Any ideas on this issue?


[1] http://wiki.xensource.com/xenwiki/XenNetworking


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

<Prev in Thread] Current Thread [Next in Thread>