[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Problems with bridged networking

  • To: "Thomas Robers" <robers@xxxxxxxxx>
  • From: Tej <bewith.tej@xxxxxxxxx>
  • Date: Wed, 10 Sep 2008 10:56:52 +0530
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 09 Sep 2008 22:27:27 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PVC6uWdTl4tjsMWfTni7g31ZGhvZPZflpm7Hzt+E7mtoqXGhMH09CBkdH4MMsJFpQr OETaIAdyVmK2FpuI8t1c7a9E9YUZPh+9iP+p/fGNRtUNTEOMds4N5RAMajb7eGRNZ1ua nyVJ7p4NGIAVIwEcHg+fqitpdNrHMqZAIqUHE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
On 9/9/08, Thomas Robers <robers@xxxxxxxxx> wrote:
> Hi,
>
> I'm using Xen 3.0.3 on two servers with Debian Etch (amd64). These
> servers have 10 nics (2 onboard and 8 in two 4-port cards) so that
> every vm can have its own interface.
> This worked so far with the Xen Version from Etch with a wrapper
> script wich started 10 bridges at boot time. But now I've updated Xen
> on one of these server to Xen 3.2.0 from backports.org and now the
> network doesn't work anymore resp not like it should.
> When I use the wrapper script the server doesn't have any network
> connection and when I use the 'network-bridge' script from Xen 3.2.0
> I get the machine connected to the network but without any bridge,
>
> ifconfig tells me this:
>
>> server:~# ifconfig
>> eth0      Protokoll:Ethernet  Hardware Adresse 00:0E:0C:43:AB:3D
>>           inet Adresse:XXX.XXX.XXX.XXX  Bcast:XXX.XXX.XXX.XXX
>> Maske:255.255.255.192
>>           inet6 Adresse: fe80::20e:cff:fe43:ab3d/64
>> Gültigkeitsbereich:Verbindung
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:14954 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1314 errors:0 dropped:0 overruns:0 carrier:0
>>           Kollisionen:0 Sendewarteschlangenlänge:0
>>           RX bytes:2067814 (1.9 MiB)  TX bytes:136934 (133.7 KiB)
>>
>> lo        Protokoll:Lokale Schleife
>>           inet Adresse:127.0.0.1  Maske:255.0.0.0
>>           inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
>>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>           Kollisionen:0 Sendewarteschlangenlänge:0
>>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>
>> peth0     Protokoll:Ethernet  Hardware Adresse 00:0E:0C:43:AB:3D
>>           inet6 Adresse: fe80::20e:cff:fe43:ab3d/64
>> Gültigkeitsbereich:Verbindung
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:16544 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1800 errors:0 dropped:0 overruns:0 carrier:0
>>           Kollisionen:0 Sendewarteschlangenlänge:1000
>>           RX bytes:2460253 (2.3 MiB)  TX bytes:208166 (203.2 KiB)
>>           Interrupt:17
>
> So there's no xenbr0 up and brctl shows this:
>
>> server:~# brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> eth0            8000.000e0c43ab3d       no              peth0

I am not sure your domU is up or not, because your ifconfig is not
showing any vif interfaces.

try this in your domU config file
vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ], now boot domU
vif <domid>.0 should be just below peth0.

HTH
thanks
-tej

P.S. I am just wondering why vif0.0 is not showing in your brctl show.



>
> 'ip link show' looks like this:
>
>> 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
>>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> 2: peth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
>> 1000
>>     link/ether 00:0e:0c:43:ab:3d brd ff:ff:ff:ff:ff:ff
>> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:43:ab:3e brd ff:ff:ff:ff:ff:ff
>> 4: eth8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:14:94 brd ff:ff:ff:ff:ff:ff
>> 5: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:14:95 brd ff:ff:ff:ff:ff:ff
>> 6: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:14:96 brd ff:ff:ff:ff:ff:ff
>> 7: eth9: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:14:97 brd ff:ff:ff:ff:ff:ff
>> 8: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:1a:f4 brd ff:ff:ff:ff:ff:ff
>> 9: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:1a:f5 brd ff:ff:ff:ff:ff:ff
>> 10: eth4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:1a:f6 brd ff:ff:ff:ff:ff:ff
>> 11: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>>     link/ether 00:0e:0c:c5:1a:f7 brd ff:ff:ff:ff:ff:ff
>> 12: sit0: <NOARP> mtu 1480 qdisc noop
>>     link/sit 0.0.0.0 brd 0.0.0.0
>> 13: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>> 14: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
>> 15: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>> 16: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
>> 17: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>> 18: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
>> 19: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>> 20: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
>> 21: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
>>     link/ether 00:0e:0c:43:ab:3d brd ff:ff:ff:ff:ff:ff
>
> /var/log/xend.log shows this:
>
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Xend Daemon started
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Xend changeset:
>> unavailable.
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Xend version: Unknown.
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr1
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr8
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr9
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr3
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr5
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr2
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr6
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network tmpbridge
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr0
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr4
>> [2008-09-09 15:34:42 3755] INFO (__init__:1072) Not recreating missing
>> unmanaged network xenbr7
>> [2008-09-09 15:34:43 3755] DEBUG (__init__:1072)
>> XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 31253704308L,
>> 'ssidref': 1278071716, '
>> hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 8, 'domid': 0,
>> 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L,
>> 'shutdown': 0, 'mem_kb': 16382760L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0,
>> 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'})
>> [2008-09-09 15:34:43 3755] INFO (__init__:1072) Recreating domain 0, UUID
>> 00000000-0000-0000-0000-000000000000. at /local/domain/0
>> [2008-09-09 15:34:43 3755] DEBUG (__init__:1072) Storing VM details:
>> {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0
>> 000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel
>> ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash':
>>  'restart', 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': '255',
>> 'name': 'Domain-0'}
>> [2008-09-09 15:34:43 3755] DEBUG (__init__:1072) Storing domain details:
>> {'cpu/3/availability': 'online', 'name': 'Domain-0', 'console/limit':
>>  '1048576', 'memory/target': '16382760', 'cpu/2/availability': 'online',
>> 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'secu
>> rity_label': '', 'cpu/7/availability': 'online', 'cpu/0/availability':
>> 'online', 'cpu/1/availability': 'online', 'cpu/5/availability': 'online
>> ', 'control/platform-feature-multiprocessor-suspend': '1',
>> 'cpu/6/availability': 'online', 'console/type': 'xenconsoled',
>> 'cpu/4/availability'
>> : 'online'}
>> [2008-09-09 15:34:43 3755] DEBUG (__init__:1072) Adding Domain: 0
>> [2008-09-09 15:34:43 3755] DEBUG (__init__:1072) number of vcpus to use is
>> 0
>> [2008-09-09 15:34:43 3755] DEBUG (__init__:1072)
>> XendDomainInfo.handleShutdownWatch
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call:
>> VBD.set_device not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call: VBD.set_type
>> not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call:
>> session.get_all_records not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call:
>> event.get_record not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call: event.get_all
>> not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call:
>> VM.get_auto_power_on not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call:
>> VM.set_auto_power_on not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call:
>> VIF.get_network not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call:
>> VIF.set_device not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call: VIF.set_MAC
>> not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call: VIF.set_MTU
>> not found
>> [2008-09-09 15:34:43 3755] WARNING (__init__:1072) API call: debug.get_all
>> not found
>> [2008-09-09 15:34:43 3755] INFO (__init__:1072) Opening Unix domain socket
>> XML-RPC server on /var/run/xend/xen-api.sock; authentication has be
>> en disabled for this server.
>> [2008-09-09 15:34:43 3755] INFO (__init__:1072) Opening Unix domain socket
>> XML-RPC server on /var/run/xend/xmlrpc.sock.
>
> When I try the network-bridge script by hand I get this message:
>
>> server:/etc/xen/scripts# ./network-bridge netdev=eth3 bridge=xenbr3 start
>> ifdown: interface eth3 not configured
>> Nothing to flush.
>> Waiting for peth3 to negotiate link.
>> Ignoring unknown interface xenbr3=xenbr3.
>
> I have this  problem also with Xen on a Gentoo box. Here Xen only works up
> to version 3.1.3.
> All other versions don't work, because of the missing bridges.
>
> I searched for this problem but it seems that I'm the only one with this a
> problem.
> Can someone give me any hint, or perhaps there's someone with a similar
> problem?
> If any further informations are needed I can provide them.
>
> Many thanks
> Thomas
>
>
>
> _______________________________________________
> 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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.