thr3ads.net - Xen users - [Xen-users] Problems with bridged networking [Sep 2008]

If this information is useful, please help other people find it:
Share via:

Thomas Robers

2008-Sep-09 14:30 UTC

[Xen-users] Problems with bridged networking

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
''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@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Power

2008-Sep-09 14:45 UTC

head link

Re: [Xen-users] Problems with bridged networking

At some point I am guessing around 3.1 the bridge network scripts 
changed the resulting bridge configuration they produced.

You can see some diagrams here:
http://wiki.xensource.com/xenwiki/XenNetworking#head-708d4c55f42b5e2b866c06e1ae69530e8c748799

 From my quick reading of your problem your domU config files probably 
still point at the nonexistent bridge xenbr0.  Take a look at the link I 
sent you to help you understand what your scripts are doing and that 
should get you on the road to setting up your networking the way you 
want.  At very least the link should show you that the new bridge name 
will be something like eth0.

Thomas Robers 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
>
> ''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@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Steffen Heil

2008-Sep-09 14:56 UTC

head link

AW: [Xen-users] Problems with bridged networking

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.
Just for interest... why?
Aren''t they all connected to the very same switch?
> 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
So there IS a bridge, but it''s name is eth0, which is default for xen
3.2.1...
Earlier versions created xenbr0 and added a virtual interface eth0, newer
versions just name the bridge eth0. Basically the same, with one indirection
less.

Regards,
  Steffen



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

Tej

2008-Sep-10 05:26 UTC

head link

Re: [Xen-users] Problems with bridged networking

On 9/9/08, Thomas Robers <robers@tutech.de> 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@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Thomas Robers

2008-Sep-10 09:17 UTC

head link

Re: [Xen-users] Problems with bridged networking

Hi Tej,

thanks for your answer.

Tej schrieb:> I am not sure your domU is up or not, because your ifconfig is not
> showing any vif interfaces.
No, there were no domUs up when I did ''brctl show'' because
they
don''t start because of missing ''xenbrX''-bridges.
> 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.
I have this in my config files for the domUs (I don''t set mac
adresses) e.g.:

vif = [ ''bridge=xenbr1'' ] for domU A
   .
   .
   .
vif = [ ''bridge=xenbr5'' ] for domU E
vif = [ ''bridge=xenbr6'' ] for domU F

I''m using 6 Bridges at the moment for 6 domUs, so xenbr0
wouldn''t
be an option. Also I don''t have an bridge called
''xenbr0''
and with this setting no domU booted. It ended up with an error
message saying that it could not create device.
> HTH
> thanks
> -tej
> 
> P.S. I am just wondering why vif0.0 is not showing in your brctl show.

Thanks
Thomas


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

Thomas Robers

2008-Sep-10 09:35 UTC

head link

Re: [Xen-users] Problems with bridged networking

Hi Steffen,

thanks for the answer

Steffen Heil schrieb:>> 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.
> 
> Just for interest... why?
> Aren''t they all connected to the very same switch?
Yes, that''s right, the vm are partially on different
networks.
>> 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
> 
> So there IS a bridge, but it''s name is eth0, which is default for
xen
> 3.2.1...
Is this normal to version 3.2.0 too? Because I only found version 3.2.0
for Debian.
> Earlier versions created xenbr0 and added a virtual interface eth0, newer
> versions just name the bridge eth0. Basically the same, with one
indirection
> less.
Ok, but is there a chance to get the other bridges up too? I tried:

	server:/etc/xen/scripts# ./network-bridge bridge=eth1 netdev=eth1 start
	ifdown: interface eth1 not configured
	Nothing to flush.
	Waiting for peth1 to negotiate link......
	Ignoring unknown interface eth1=eth1.

So that doesn''t work, and I used this command for version 3.0.3 to set
up all
the bridges and the message I get is the same when I use
''bridge=xenbr1''.
I also tried this:

	server:/etc/xen/scripts# ./network-bridge start netdev=eth3 bridge=xenbr3
	ifdown: interface eth3 not configured
	Nothing to flush.
	Waiting for peth3 to negotiate link.
	Ignoring unknown interface xenbr3=xenbr3.

and brctl shows the bridge named ''xenbr3'':

	server:/etc/xen/scripts# brctl show
	bridge name     bridge id               STP enabled     interfaces
	eth0            8000.000e0c43ab3d       no              peth0
	eth1            8000.000e0c43ab3e       no              peth1
	xenbr3          8000.000e0cc51af5       no              peth3


I don''t understand whats happening there. Why is there a bridge
interface
like it should but I can''t use it. I booted the domU (thats possible
now)
which uses xenbr3 but I don''t get a connection the network. In the domU
the eth0
interface is up and running when I try to do a ping to the gateway ip address
I get no answer. So I don''t really understand why the
''network-bridge'' script
doesn''t work. Do you have any other advice where I can search?

Thanks
Thomas

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

Thomas Robers

2008-Sep-10 09:58 UTC

head link

Re: [Xen-users] Problems with bridged networking

Mike Power schrieb:> At some point I am guessing around 3.1 the bridge network scripts 
> changed the resulting bridge configuration they produced.
> 
> You can see some diagrams here:
>
http://wiki.xensource.com/xenwiki/XenNetworking#head-708d4c55f42b5e2b866c06e1ae69530e8c748799
> 
> 
>  From my quick reading of your problem your domU config files probably 
> still point at the nonexistent bridge xenbr0.  Take a look at the link I 
> sent you to help you understand what your scripts are doing and that 
> should get you on the road to setting up your networking the way you 
> want.  At very least the link should show you that the new bridge name 
> will be something like eth0.
Hi Mike,

thank you for your answer. I looked at wiki entry and as Steffen also told
me, I can see, that in Xen 3.2.x the bridge names have changed from 3.1.x ->
3.2.x
So I tried what I found in almost every howto and book:

	server:/etc/xen/scripts# ./network-bridge bridge=eth1 netdev=eth1 start
	ifdown: interface eth1 not configured
	Nothing to flush.
	Waiting for peth1 to negotiate link......
	Ignoring unknown interface eth1=eth1

for the eth1 interface and a brctl afterwards:

	server:/etc/xen/scripts# brctl show
	bridge name     bridge id               STP enabled     interfaces
	eth0            8000.000e0c43ab3d       no              peth0
	eth1            8000.000e0c43ab3e       no              peth1

shows that there is an bridge named eth1 but the domU which formerly used
''xenbr1'' doesn''t start with the bridge named eth1. I
tried this in the
config file for domU

	vif = [ ''bridge=eth1'' ]

The domU starts but there is no network connection possible. I thought that
the ''network-bridge'' script would set up the bridge and put it
up a ifconfig
doesn''t show an interface eth1 only peth1.

Now I''ve booted Xen 3.0.3 again and almost everything works as
expected. After
booting all bridges are up and working

	xenbr1    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:43:AB:3E
         	  inet6 Adresse: fe80::20e:cff:fe43:ab3e/64
Gültigkeitsbereich:Verbindung
        		  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           	  RX packets:186 errors:0 dropped:0 overruns:0 frame:0
         	  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         	  Kollisionen:0 Sendewarteschlangenlänge:0
         	  RX bytes:26111 (25.4 KiB)  TX bytes:468 (468.0 b)

	xenbr2    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F4
         	  inet6 Adresse: fe80::20e:cff:fec5:1af4/64
Gültigkeitsbereich:Verbindung
         	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         	  RX packets:163 errors:0 dropped:0 overruns:0 frame:0
         	  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         	  Kollisionen:0 Sendewarteschlangenlänge:0
         	  RX bytes:22984 (22.4 KiB)  TX bytes:468 (468.0 b)

	xenbr3    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F5
         	  inet6 Adresse: fe80::20e:cff:fec5:1af5/64
Gültigkeitsbereich:Verbindung
         	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         	  RX packets:134 errors:0 dropped:0 overruns:0 frame:0
         	  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         	  Kollisionen:0 Sendewarteschlangenlänge:0
         	  RX bytes:18998 (18.5 KiB)  TX bytes:468 (468.0 b)

	xenbr4    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F6
         	  inet6 Adresse: fe80::20e:cff:fec5:1af6/64
Gültigkeitsbereich:Verbindung
         	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         	  RX packets:208 errors:0 dropped:0 overruns:0 frame:0
         	  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         	  Kollisionen:0 Sendewarteschlangenlänge:0
         	  RX bytes:32637 (31.8 KiB)  TX bytes:468 (468.0 b)

	xenbr5    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:1A:F7
         	  inet6 Adresse: fe80::20e:cff:fec5:1af7/64
Gültigkeitsbereich:Verbindung
         	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         	  RX packets:273 errors:0 dropped:0 overruns:0 frame:0
         	  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         	  Kollisionen:0 Sendewarteschlangenlänge:0
         	  RX bytes:37964 (37.0 KiB)  TX bytes:468 (468.0 b)

	xenbr6    Protokoll:Ethernet  Hardware Adresse 00:0E:0C:C5:14:95
         	  inet6 Adresse: fe80::20e:cff:fec5:1495/64
Gültigkeitsbereich:Verbindung
         	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         	  RX packets:3396 errors:0 dropped:0 overruns:0 frame:0
         	  TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         	  Kollisionen:0 Sendewarteschlangenlänge:0
         	  RX bytes:497298 (485.6 KiB)  TX bytes:468 (468.0 b)

I did this with the wrapper script:

	/etc/xen/scripts/network-bridge start vifnum=0 bridge=xenbr0 netdev=eth0
	/etc/xen/scripts/network-bridge start vifnum=1 bridge=xenbr1 netdev=eth1
	/etc/xen/scripts/network-bridge start vifnum=2 bridge=xenbr2 netdev=eth2
	/etc/xen/scripts/network-bridge start vifnum=3 bridge=xenbr3 netdev=eth3
	/etc/xen/scripts/network-bridge start vifnum=4 bridge=xenbr4 netdev=eth4
	/etc/xen/scripts/network-bridge start vifnum=5 bridge=xenbr5 netdev=eth5
	/etc/xen/scripts/network-bridge start vifnum=6 bridge=xenbr6 netdev=eth6


Do you have any further suggestions where I could look?

Many Thanks.
Thomas


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

Fischer, Anna

2008-Sep-10 10:26 UTC

head link

RE: [Xen-users] Problems with bridged networking

> Now I''ve booted Xen 3.0.3 again and almost everything works as
> expected. After
> booting all bridges are up and working.
Are you booting Xen 3.0.3 and Xen 3.2 on the same machine using the same
userspace tools but different kernels? Are you sure that you have not messed up
your networking scripts?

When you run Xen 3.2 (and it does not work), do you have connectivity between
Dom0 and external hosts using eth1?

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

Thomas Robers

2008-Sep-10 13:16 UTC

head link

Re: [Xen-users] Problems with bridged networking

Fischer, Anna schrieb:>> Now I''ve booted Xen 3.0.3 again and almost everything works as
>> expected. After
>> booting all bridges are up and working.
> 
> Are you booting Xen 3.0.3 and Xen 3.2 on the same machine using the same
userspace tools but different kernels? Are you sure that you have not messed up
your networking scripts?
> 
> When you run Xen 3.2 (and it does not work), do you have connectivity
between Dom0 and external hosts using eth1?
Hello Anna,

maybe there''s something mixed up. I remember that I had problems
getting up 10 bridges
with Xen 3.0.3 from Debian.
I use a wrapper script which starts the bridges at boot time:

	/etc/xen/xend.config.sxp:
	(network-script network-bridge-wrapper)

	/etc/xen/scripts/network-bridge-wrapper:
	#!/bin/bash
	/etc/xen/scripts/network-bridge start vifnum=0 bridge=xenbr0 netdev=eth0
	/etc/xen/scripts/network-bridge start vifnum=1 bridge=xenbr1 netdev=eth1
	/etc/xen/scripts/network-bridge start vifnum=2 bridge=xenbr2 netdev=eth2
	/etc/xen/scripts/network-bridge start vifnum=3 bridge=xenbr3 netdev=eth3
	/etc/xen/scripts/network-bridge start vifnum=4 bridge=xenbr4 netdev=eth4
	/etc/xen/scripts/network-bridge start vifnum=5 bridge=xenbr5 netdev=eth5
	/etc/xen/scripts/network-bridge start vifnum=6 bridge=xenbr6 netdev=eth6
	/etc/xen/scripts/network-bridge start vifnum=7 bridge=xenbr7 netdev=eth7
	/etc/xen/scripts/network-bridge start vifnum=8 bridge=xenbr8 netdev=eth8
	/etc/xen/scripts/network-bridge start vifnum=9 bridge=xenbr9 netdev=eth9

But with the ''network-bridge''-script from Debian I only got 4
bridges from xenbr0
up to xenbr3. So I exchanged the script with the one from the binary package
from
xen.org and with that script everything worked as expected.
And now I made the upgrade via backports.org to hypervisor version 3.2 and
there''s
Xen Hypervisor version 3.0.3 and 3.2.0 installed and bootable. And it works
with Hypervisor 3.0.3 and 3.2.0 as long as  I make *no* upgrade of the Debian
package ''xen-utils-common''

	server:~# apt-show-versions xen-utils-common
	xen-utils-common/etch upgradeable from 3.0.3-0-2 to 3.2.0-1~bpo4+1


Tomorrow I will make that update and see what happens but the main problem seem
to me, that the ''network-bridge''-script stops setting up xenbr
bridges. Is it
possible to set limitations regarding how many bridges are possible? Or is there
any other reason, why only 4 briges got up? I haven''t found anything
and the fact
that it works with the script from xen.org looks to me like an error in the
Debian
script, or am I wrong?

Thanks!
Thomas

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

Tej

2008-Sep-10 13:35 UTC

head link

Re: [Xen-users] Problems with bridged networking

On 9/10/08, Thomas Robers <robers@tutech.de>
wrote:> Hi Tej,
>
> thanks for your answer.
>
> Tej schrieb:
>> I am not sure your domU is up or not, because your ifconfig is not
>> showing any vif interfaces.
>
> No, there were no domUs up when I did ''brctl show''
because they
> don''t start because of missing ''xenbrX''-bridges.
xenbrX is optional, there is no relation in providing this information
and booting domU.


>
>> 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.
>
> I have this in my config files for the domUs (I don''t set mac
> adresses) e.g.:
>
> vif = [ ''bridge=xenbr1'' ] for domU A
>    .
>    .
>    .
> vif = [ ''bridge=xenbr5'' ] for domU E
> vif = [ ''bridge=xenbr6'' ] for domU F
>
> I''m using 6 Bridges at the moment for 6 domUs, so xenbr0
wouldn''t
> be an option. Also I don''t have an bridge called
''xenbr0''
> and with this setting no domU booted. It ended up with an error
> message saying that it could not create device.
Ok, please provide your domU config file and the exact error messages


>
>> HTH
>> thanks
>> -tej
>>
>> P.S. I am just wondering why vif0.0 is not showing in your brctl show.
>
>
> Thanks
> Thomas
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Power

2008-Sep-10 15:25 UTC

head link

Re: [Xen-users] Problems with bridged networking

>
>
> thank you for your answer. I looked at wiki entry and as Steffen also 
> told
> me, I can see, that in Xen 3.2.x the bridge names have changed from 
> 3.1.x -> 3.2.x
> So I tried what I found in almost every howto and book:
>
>     server:/etc/xen/scripts# ./network-bridge bridge=eth1 netdev=eth1 
> start
>     ifdown: interface eth1 not configured
>     Nothing to flush.
>     Waiting for peth1 to negotiate link......
>     Ignoring unknown interface eth1=eth1
>Are your physical interfaces configured?  3.2 bridge script scrapes off 
the information from netdev and applies it to bridge.  If your netdev is 
not up and running by the time network-bridge is run I am not sure it 
will be able to stand up the bridge.

Before you run your network-bridge scripts check the output of ifconfig 
and make sure each physical interface is mentioned and has an ip.


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

Nadolski, Ed

2008-Sep-11 21:35 UTC

head link

RE: [Xen-users] Problems with bridged networking

I seem to have hit the same issue, but with just a single NIC.  This is on
CentOS 5.2 with Xen 3.3 installed.  I run /etc/init.d/xend start manually since
it is not (yet) hooked into the rc scripts.



The eth0 works fine from dom0 but there is no bridge being created that works
with any of the VMs:



[root@xensys3 ~]# brctl show

bridge name       bridge id               STP enabled interfaces

eth0            8000.001cc03c02d7    no         peth0





Shouldn''t that include a vif0.0?  That is what I see with Xen version
3.1.2-92.el5 on the same system:



[root@xensys3 ~]# brctl show

bridge name       bridge id               STP enabled interfaces

virbr0          8000.000000000000    yes

xenbr0          8000.feffffffffff    no         peth0

                                                      vif0.0





Below is a partial "xm log" output.  To me the messages about the
"missing tmpbridge"  and "VBD.set_device not found" seem
suspicious.  Can anyone please tell me what those messages mean?



Thanks,

Ed



[2008-09-11 14:42:54 6421] INFO (SrvDaemon:331) Xend Daemon started

[2008-09-11 14:42:54 6421] INFO (SrvDaemon:335) Xend changeset: unavailable.

[2008-09-11 14:42:54 6421] INFO (XendNetwork:114) Not recreating missing
unmanaged network tmpbridge

[2008-09-11 14:42:54 6421] DEBUG (XendDomainInfo:137)
XendDomainInfo.recreate(<<snip>>)

[2008-09-11 14:42:54 6421] INFO (XendDomainInfo:153) Recreating domain 0, UUID
00000000-0000-0000-0000-000000000000. at /local/domain/0

[2008-09-11 14:42:54 6421] DEBUG (XendDomainInfo:2729) Storing VM details:
{<<snip>>}

[2008-09-11 14:42:54 6421] DEBUG (XendDomainInfo:1359) Storing domain details:
{<<snip>>}

[2008-09-11 14:42:54 6421] DEBUG (XendDomain:447) Adding Domain: 0

[2008-09-11 14:42:54 6421] DEBUG (XendDomain:383) number of vcpus to use is 0

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VBD.set_device not
found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VBD.set_type not
found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call:
session.get_all_records not found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: event.get_record not
found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: event.get_all not
found

[2008-09-11 14:42:54 6421] DEBUG (XendDomainInfo:1443)
XendDomainInfo.handleShutdownWatch

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VM.get_auto_power_on
not found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VM.set_auto_power_on
not found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VIF.get_network not
found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VIF.set_device not
found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VIF.set_MAC not found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: VIF.set_MTU not found

[2008-09-11 14:42:54 6421] WARNING (XendAPI:684) API call: debug.get_all not
found









-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike Power
Sent: Wednesday, September 10, 2008 9:25 AM
To: Thomas Robers
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Problems with bridged networking




>
>
> thank you for your answer. I looked at wiki entry and as Steffen also
> told
> me, I can see, that in Xen 3.2.x the bridge names have changed from
> 3.1.x -> 3.2.x
> So I tried what I found in almost every howto and book:
>
>     server:/etc/xen/scripts# ./network-bridge bridge=eth1 netdev=eth1
> start
>     ifdown: interface eth1 not configured
>     Nothing to flush.
>     Waiting for peth1 to negotiate link......
>     Ignoring unknown interface eth1=eth1
>
Are your physical interfaces configured?  3.2 bridge script scrapes off

the information from netdev and applies it to bridge.  If your netdev is

not up and running by the time network-bridge is run I am not sure it

will be able to stand up the bridge.



Before you run your network-bridge scripts check the output of ifconfig

and make sure each physical interface is mentioned and has an ip.





_______________________________________________

Xen-users mailing list

Xen-users@lists.xensource.com

http://lists.xensource.com/xen-users


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

Thomas Robers

2008-Sep-15 15:00 UTC

head link

Re: [Xen-users] Problems with bridged networking

Hi,

I''ve now tested Xen 3.2 from backports.org on a Debian 4.0 test
machine with 7 Interfaces and the problem is in the script
''network-bridge''.
There''s a function ''do_ifup'' in it which I have
modified and after
modification Xen 3.2 works on my Debian machine. I found that
with Xen 3.2 the bridges were there but not up and everything
works as expected when I did a ''ifconfig xenbrX up''.

Before modification:

	do_ifup() {
	if ! ifup $1 ; then
	    if [ -n "$addr_pfx" ] ; then
	        # use the info from get_ip_info()
	        ip addr flush $1
	        ip addr add ${addr_pfx} dev $1
	        ip link set dev $1 up
	        [ -n "$gateway" ] && ip route add default via
${gateway}
	    fi
         fi
}


After modification:

	do_ifup() {
         ifconfig $1 up
         if [ -n "$addr_pfx" ] ; then
             # use the info from get_ip_info()
             ip addr flush $1
             ip addr add ${addr_pfx} dev $1
             ip link set dev $1 up
             [ -n "$gateway" ] && ip route add default via
${gateway}
         fi
}

So that way it works for me for now. But could there be any other
drawback except for further updates? I also haven''t really found out
what this test with ''ifup'' is really for. Can anybody explain
what''s
happening there? I saw this message from ''ifup'' when it got
executed
(e.g. for xenbr6):

	''Ignoring unkown interfacexenbr6=xenbr6''

Perhaps there is there anybody else with Debian Xen machine and uses more
than one physical network interface in bridged mode where it works out of
the box? Maybe I''ve overlooked something essentail?

Here''s my xend-config.sxp

	(network-script network-bridge-wrapper)
	(vif-script vif-bridge)
	(dom0-min-mem 196)
	(dom0-cpus 0)
	(vncpasswd '''')

and a config file for a domU machine:

	kernel  = ''/boot/vmlinuz-2.6.18-6-xen-amd64''
	ramdisk = ''/boot/initrd.img-2.6.18-6-xen-amd64''
	memory  = ''256''
	root    = ''/dev/hda1 ro''
	disk    = [ ''file:/xen/domains/dom1/disk.img,hda1,w'',
''file:/xen/domains/dom1/swap.img,hda2,w'' ]
	name    = ''dom1''
	dhcp = ''dhcp''
	vif  = [ ''bridge=xenbr6'' ]
	on_poweroff = ''destroy''
	on_reboot   = ''restart''
	on_crash    = ''restart''

''brctl show'':

	xen-test:/etc/xen# brctl show
	bridge name     bridge id               STP enabled     interfaces
	xenbr0          8000.001d602f1a39       no              peth0
	xenbr1          8000.000a5e610e18       no              peth1
	xenbr2          8000.000a5e4efe58       no              peth2
	xenbr3          8000.000d88684080       no              peth3
	xenbr4          8000.000d88684081       no              peth4
	xenbr5          8000.000d88684082       no              peth5
	xenbr6          8000.000d88684083       no              peth6
	                                                        vif2.0
Any suggestions are welcome.

Thanks!
Thomas

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

Angel L. Mateo

2008-Sep-17 06:05 UTC

head link

Re: [Xen-users] Problems with bridged networking

El lun, 15-09-2008 a las 17:00 +0200, Thomas Robers
escribió:> Hi,
> 
> I''ve now tested Xen 3.2 from backports.org on a Debian 4.0 test
> machine with 7 Interfaces and the problem is in the script
> ''network-bridge''.
> There''s a function ''do_ifup'' in it which I have
modified and after
> modification Xen 3.2 works on my Debian machine. I found that
> with Xen 3.2 the bridges were there but not up and everything
> works as expected when I did a ''ifconfig xenbrX up''.
> 
> Before modification:
> 
> 	do_ifup() {
> 	if ! ifup $1 ; then
> 	    if [ -n "$addr_pfx" ] ; then
> 	        # use the info from get_ip_info()
> 	        ip addr flush $1
> 	        ip addr add ${addr_pfx} dev $1
> 	        ip link set dev $1 up
> 	        [ -n "$gateway" ] && ip route add default via
${gateway}
> 	    fi
>          fi
> }
> 
> 
> After modification:
> 
> 	do_ifup() {
>          ifconfig $1 up
>          if [ -n "$addr_pfx" ] ; then
>              # use the info from get_ip_info()
>              ip addr flush $1
>              ip addr add ${addr_pfx} dev $1
>              ip link set dev $1 up
>              [ -n "$gateway" ] && ip route add default
via ${gateway}
>          fi
> }
> 
> So that way it works for me for now. But could there be any other
> drawback except for further updates? I also haven''t really found
out
> what this test with ''ifup'' is really for. Can anybody
explain what''s
> happening there? I saw this message from ''ifup'' when it
got executed
> (e.g. for xenbr6):
> 	I haven''t check the rest of the scripts, but ifup is a debian command
to bring an interface up (and returns zero is everything is ok). So your
code and the original are different ways to do the same (I haven''t
tried
to find out why yours works and the other doesn''t).

-- 
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información       _o)
y las Comunicaciones Aplicadas (ATICA)      / \\
http://www.um.es/atica                    _(___V
Tfo: 968367590
Fax: 968398337



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

Nemeth, Tamas

2008-Sep-17 07:36 UTC

head link

Re: [Xen-users] Problems with bridged networking

2008. 09. 15, hétfő keltezéssel 17.00-kor Thomas Robers ezt
írta:> I''ve now tested Xen 3.2 from backports.org on a Debian 4.0 test
> machine with 7 Interfaces and the problem is in the script
> ''network-bridge''.
I''ve sent a mail to this list at Tue, 16 Sep 2008 22:39:35 +0200 with
a
subject of "xen on openSUSE" which seems to describe the same problem
as yours, but on openSUSE.I''ve found that
the /etc/xen/scripts/xen-network-common.sh script in recent xen
releases  makes some incorrect assumptions on the ifup script. (Or ifup
itself behaves incorrectly?) So i modified the xen-network-common.sh
script as follows:

#if ! which ifup >/dev/null 2>/dev/null
if true


More details in my mail mentioned above.


A you might already realize that xen no more loads the netloop module
which creates the vif/veth pairs, but it uses the bridge itself, which
is now called eth0 instead of xenbr0.

Without modificating the xen networking scripts (either your way or my
way) the bridge interfaces will not be switched in the "UP" state. And
interfaces in state "DOWN" are invisible for the old (and maybe
deprecated) ifconfig command. Only "ip address show" or "ip link
show"
will show tht they exist but are turned off.

Best regards

Tamas


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

Maybe Matching Threads

Search for more apparently analagous threads

Xen users - Sep 2008 - Problems with bridged networking

[Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

AW: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

RE: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

RE: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Re: [Xen-users] Problems with bridged networking

Maybe Matching Threads