Hello,
I am trying to use XEN networking as default : bridge xenbr0 with
ethernet adaptor eth0. As soon as xend is started , xenbr0 does not
activate and eth0 seems to run as if no bridge were preent.
Here is my config file:
# To bridge network traffic, like this:
#
# dom0: fake eth0 -vif0.0 -+
# |
# bridge -real eth0 -the network
# |
# domU: fake eth0 -vifN.0 -+
#
# use
#
# (network-script network-bridge)
#
# Your default ethernet device is used as the outgoing interface, by
default.
# To use a different one (e.g. eth1) use
#
# (network-script ''network-bridge netdev=eth1'')
#
# The bridge is named xenbr0, by default. To rename the bridge, use
#
# (network-script ''network-bridge bridge=<name>'')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges,
and
# two fake interfaces per guest domain. To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as
appropriate.
#
(network-script ''network-bridge bridge=xenbr0 netdev=eth0'')
# The script used to control virtual interfaces. This can be overridden
on a
# per-vif basis when creating a domain or a configuring a new vif. The
# vif-bridge script is designed for use with the network-bridge script,
or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script ''network-bridge bridge=<name>'') then
you may wish to do
the
# same here. The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a
default.
#
# If you are using only one bridge, the vif-bridge script will discover
that,
# so there is no need to specify it explicitly.
#
(vif-script ''vif-bridge bridge=xenbr0'')
-------------------------------------------------------------
An ifconfig gives the following:
eth0 Link encap:Ethernet HWaddr 9E:34:72:FC:1B:00
inet adr:192.168.0.3 Bcast:192.168.0.255 Masque:255.255.255.0
adr inet6: fe80::9c34:72ff:fefc:1b00/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:2727 (2.6 KiB) TX bytes:4357 (4.2 KiB)
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:882 errors:0 dropped:0 overruns:0 frame:0
TX packets:882 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:44100 (43.0 KiB) TX bytes:44100 (43.0 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:260 errors:0 dropped:0 overruns:0 frame:0
TX packets:363 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:39940 (39.0 KiB) TX bytes:35555 (34.7 KiB)
Interruption:16 Adresse de base:0x6000
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:4357 (4.2 KiB) TX bytes:2797 (2.7 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet adr:192.168.0.20 Bcast:192.168.0.255 Masque:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:4021 (3.9 KiB) TX bytes:2979 (2.9 KiB)
-------------------------------------------------------
Here is the result of the command:
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
I enclosed the log files generated by xen for the command line : service
xend start :
I have no idea of the reason why the xen network does not start. (Do I need
a package which is not present ?)
If anyone could give a way where to investigate ...
Thx a lot
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
TURPIN Olivier wrote:> Hello, > > I am trying to use XEN networking as default : bridge xenbr0 with > ethernet adaptor eth0. As soon as xend is started , xenbr0 does not > activate and eth0 seems to run as if no bridge were preent. > > Here is my config file: > # To bridge network traffic, like this: > # > # dom0: fake eth0 -vif0.0 -+ > # | > # bridge -real eth0 -the network > # | > # domU: fake eth0 -vifN.0 -+ > # > # use > # > # (network-script network-bridge) > # > # Your default ethernet device is used as the outgoing interface, by > default. > # To use a different one (e.g. eth1) use > # > # (network-script ''network-bridge netdev=eth1'') > # > # The bridge is named xenbr0, by default. To rename the bridge, use > # > # (network-script ''network-bridge bridge=<name>'') > # > # It is possible to use the network-bridge script in more complicated > # scenarios, such as having two outgoing interfaces, with two bridges, > and > # two fake interfaces per guest domain. To do things like this, write > # yourself a wrapper script, and call network-bridge from it, as > appropriate. > # > (network-script ''network-bridge bridge=xenbr0 netdev=eth0'') > # The script used to control virtual interfaces. This can be overridden > on a > # per-vif basis when creating a domain or a configuring a new vif. The > # vif-bridge script is designed for use with the network-bridge script, > or > # similar configurations. > # > # If you have overridden the bridge name using > # (network-script ''network-bridge bridge=<name>'') then you may wish to do > the > # same here. The bridge name can also be set when creating a domain or > # configuring a new vif, but a value specified here would act as a > default. > # > # If you are using only one bridge, the vif-bridge script will discover > that, > # so there is no need to specify it explicitly. > # > (vif-script ''vif-bridge bridge=xenbr0'') > ------------------------------------------------------------- > > An ifconfig gives the following: > > eth0 Link encap:Ethernet HWaddr 9E:34:72:FC:1B:00 > inet adr:192.168.0.3 Bcast:192.168.0.255 Masque:255.255.255.0 > adr inet6: fe80::9c34:72ff:fefc:1b00/64 Scope:Lien > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:13 errors:0 dropped:0 overruns:0 frame:0 > TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:0 > RX bytes:2727 (2.6 KiB) TX bytes:4357 (4.2 KiB) > lo Link encap:Boucle locale > inet adr:127.0.0.1 Masque:255.0.0.0 > adr inet6: ::1/128 Scope:Hôte > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:882 errors:0 dropped:0 overruns:0 frame:0 > TX packets:882 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:0 > RX bytes:44100 (43.0 KiB) TX bytes:44100 (43.0 KiB) > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:260 errors:0 dropped:0 overruns:0 frame:0 > TX packets:363 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:1000 > RX bytes:39940 (39.0 KiB) TX bytes:35555 (34.7 KiB) > Interruption:16 Adresse de base:0x6000 > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:0 > RX bytes:4357 (4.2 KiB) TX bytes:2797 (2.7 KiB) > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet adr:192.168.0.20 Bcast:192.168.0.255 Masque:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:0 > RX bytes:4021 (3.9 KiB) TX bytes:2979 (2.9 KiB) > > ------------------------------------------------------- > > Here is the result of the command: > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > > I enclosed the log files generated by xen for the command line : > service xend start : > > I have no idea of the reason why the xen network does not start. (Do I > need a package which is not present ?) > > If anyone could give a way where to investigate ... > > Thx a lot > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersAs far as I see the ifconfig command says that the bridge is there? The eth0 is normal. I only dont know why you have ip address assigned for xenbr0? I dont see anything bad on your configuration. Tell us what does not work? For domU you have to then specify the bridge in domU config. For comparison here is mine with more bridges. eth0 Link encap:Ethernet HWaddr 00:14:C2:3A:AB:63 inet addr:192.168.30.11 Bcast:192.168.30.255 Mask:255.255.255.0 inet6 addr: fe80::214:c2ff:fe3a:ab63/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:24989 errors:0 dropped:0 overruns:0 frame:0 TX packets:17339 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2253137 (2.1 MiB) TX bytes:3373292 (3.2 MiB) 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: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) 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 MTU:1500 Metric:1 RX packets:24972 errors:0 dropped:0 overruns:0 frame:0 TX packets:17349 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2351825 (2.2 MiB) TX bytes:3443564 (3.2 MiB) Interrupt:20 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:126737 errors:0 dropped:0 overruns:0 frame:0 TX packets:106149 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44011994 (41.9 MiB) TX bytes:84835611 (80.9 MiB) Interrupt:18 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 NOARP MTU:1500 Metric:1 RX packets:17339 errors:0 dropped:0 overruns:0 frame:0 TX packets:24989 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3373292 (3.2 MiB) TX bytes:2253137 (2.1 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 NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1127 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:127247 (124.2 KiB) vif18.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:97626 errors:0 dropped:0 overruns:0 frame:0 TX packets:112923 errors:0 dropped:77 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:81439022 (77.6 MiB) TX bytes:39929936 (38.0 MiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:550 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:74036 (72.3 KiB) TX bytes:0 (0.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 NOARP MTU:1500 Metric:1 RX packets:938 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:96030 (93.7 KiB) TX bytes:0 (0.0 b) Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
oturpin@free.fr
2007-Nov-23 12:31 UTC
Re: [Xen-users] xen 3.1 network configuration problem
Hello, I set up an @IP for xenbr0 because I do not use a DHCP server on my LAN, so I need to give a manual config for IP. This morning, I tried to remove the xend service from the init of Mandriva, for testing network before xend is started. here are the strange results: 1) ping of the default gateway 192.168.0.1 is ok 2) service xend start and xendomains ok 3) ping of the default gateway NOK and ping of the domU NOK 4) service xend stop 5) ping of then default gateway NOK 6) service xend start 7) ping of default gateway OK AND ping of the domUs OK. With that sequence , the network seems to operate correctly. I wonder if there is a racing condition somewhere which is not fulfilled when the xend service is started in init scripts. Thx for your help.> TURPIN Olivier wrote: > > Hello, > > > > I am trying to use XEN networking as default : bridge xenbr0 with > > ethernet adaptor eth0. As soon as xend is started , xenbr0 does not > > activate and eth0 seems to run as if no bridge were preent. > > > > Here is my config file: > > # To bridge network traffic, like this: > > # > > # dom0: fake eth0 -vif0.0 -+ > > # | > > # bridge -real eth0 -the network > > # | > > # domU: fake eth0 -vifN.0 -+ > > # > > # use > > # > > # (network-script network-bridge) > > # > > # Your default ethernet device is used as the outgoing interface, by > > default. > > # To use a different one (e.g. eth1) use > > # > > # (network-script ''network-bridge netdev=eth1'') > > # > > # The bridge is named xenbr0, by default. To rename the bridge, use > > # > > # (network-script ''network-bridge bridge=<name>'') > > # > > # It is possible to use the network-bridge script in more complicated > > # scenarios, such as having two outgoing interfaces, with two bridges, > > and > > # two fake interfaces per guest domain. To do things like this, write > > # yourself a wrapper script, and call network-bridge from it, as > > appropriate. > > # > > (network-script ''network-bridge bridge=xenbr0 netdev=eth0'') > > # The script used to control virtual interfaces. This can be overridden > > on a > > # per-vif basis when creating a domain or a configuring a new vif. The > > # vif-bridge script is designed for use with the network-bridge script, > > or > > # similar configurations. > > # > > # If you have overridden the bridge name using > > # (network-script ''network-bridge bridge=<name>'') then you may wish to do > > the > > # same here. The bridge name can also be set when creating a domain or > > # configuring a new vif, but a value specified here would act as a > > default. > > # > > # If you are using only one bridge, the vif-bridge script will discover > > that, > > # so there is no need to specify it explicitly. > > # > > (vif-script ''vif-bridge bridge=xenbr0'') > > ------------------------------------------------------------- > > > > An ifconfig gives the following: > > > > eth0 Link encap:Ethernet HWaddr 9E:34:72:FC:1B:00 > > inet adr:192.168.0.3 Bcast:192.168.0.255 Masque:255.255.255.0 > > adr inet6: fe80::9c34:72ff:fefc:1b00/64 Scope:Lien > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:13 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 lg file transmission:0 > > RX bytes:2727 (2.6 KiB) TX bytes:4357 (4.2 KiB) > > lo Link encap:Boucle locale > > inet adr:127.0.0.1 Masque:255.0.0.0 > > adr inet6: ::1/128 Scope:Hôte > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:882 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:882 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 lg file transmission:0 > > RX bytes:44100 (43.0 KiB) TX bytes:44100 (43.0 KiB) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien > > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > > RX packets:260 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:363 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 lg file transmission:1000 > > RX bytes:39940 (39.0 KiB) TX bytes:35555 (34.7 KiB) > > Interruption:16 Adresse de base:0x6000 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien > > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 lg file transmission:0 > > RX bytes:4357 (4.2 KiB) TX bytes:2797 (2.7 KiB) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > inet adr:192.168.0.20 Bcast:192.168.0.255 Masque:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 lg file transmission:0 > > RX bytes:4021 (3.9 KiB) TX bytes:2979 (2.9 KiB) > > > > ------------------------------------------------------- > > > > Here is the result of the command: > > > > bridge name bridge id STP enabled interfaces > > xenbr0 8000.feffffffffff no vif0.0 > > peth0 > > > > I enclosed the log files generated by xen for the command line : > > service xend start : > > > > I have no idea of the reason why the xen network does not start. (Do I > > need a package which is not present ?) > > > > If anyone could give a way where to investigate ... > > > > Thx a lot > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > As far as I see the ifconfig command says that the bridge is there? > The eth0 is normal. I only dont know why you have ip address assigned > for xenbr0? > > I dont see anything bad on your configuration. Tell us what does not work? > > For domU you have to then specify the bridge in domU config. > > For comparison here is mine with more bridges. > > eth0 Link encap:Ethernet HWaddr 00:14:C2:3A:AB:63 > inet addr:192.168.30.11 Bcast:192.168.30.255 Mask:255.255.255.0 > inet6 addr: fe80::214:c2ff:fe3a:ab63/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:24989 errors:0 dropped:0 overruns:0 frame:0 > TX packets:17339 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2253137 (2.1 MiB) TX bytes:3373292 (3.2 MiB) > > 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: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) > > 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 MTU:1500 Metric:1 > RX packets:24972 errors:0 dropped:0 overruns:0 frame:0 > TX packets:17349 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:2351825 (2.2 MiB) TX bytes:3443564 (3.2 MiB) > Interrupt:20 > > peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:126737 errors:0 dropped:0 overruns:0 frame:0 > TX packets:106149 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:44011994 (41.9 MiB) TX bytes:84835611 (80.9 MiB) > Interrupt:18 > > 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 NOARP MTU:1500 Metric:1 > RX packets:17339 errors:0 dropped:0 overruns:0 frame:0 > TX packets:24989 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3373292 (3.2 MiB) TX bytes:2253137 (2.1 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 NOARP MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1127 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:127247 (124.2 KiB) > > vif18.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:97626 errors:0 dropped:0 overruns:0 frame:0 > TX packets:112923 errors:0 dropped:77 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:81439022 (77.6 MiB) TX bytes:39929936 (38.0 MiB) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:550 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:74036 (72.3 KiB) TX bytes:0 (0.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 NOARP MTU:1500 Metric:1 > RX packets:938 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:96030 (93.7 KiB) TX bytes:0 (0.0 b) > > Jiri >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
oturpin@free.fr wrote:> Hello, > > I set up an @IP for xenbr0 because I do not use a DHCP server on my LAN, so I > need to give a manual config for IP. > > This morning, I tried to remove the xend service from the init of Mandriva, for > testing network before xend is started. here are the strange results: > 1) ping of the default gateway 192.168.0.1 is ok > 2) service xend start and xendomains ok > 3) ping of the default gateway NOK and ping of the domU NOK > 4) service xend stop > 5) ping of then default gateway NOK > 6) service xend start > 7) ping of default gateway OK AND ping of the domUs OK. > > With that sequence , the network seems to operate correctly. > > I wonder if there is a racing condition somewhere which is not fulfilled when > the xend service is started in init scripts. > > Thx for your help. > >> TURPIN Olivier wrote: >>> Hello, >>> >>> I am trying to use XEN networking as default : bridge xenbr0 with >>> ethernet adaptor eth0. As soon as xend is started , xenbr0 does not >>> activate and eth0 seems to run as if no bridge were preent. >>> >>> Here is my config file: >>> # To bridge network traffic, like this: >>> # >>> # dom0: fake eth0 -vif0.0 -+ >>> # | >>> # bridge -real eth0 -the network >>> # | >>> # domU: fake eth0 -vifN.0 -+ >>> # >>> # use >>> # >>> # (network-script network-bridge) >>> # >>> # Your default ethernet device is used as the outgoing interface, by >>> default. >>> # To use a different one (e.g. eth1) use >>> # >>> # (network-script ''network-bridge netdev=eth1'') >>> # >>> # The bridge is named xenbr0, by default. To rename the bridge, use >>> # >>> # (network-script ''network-bridge bridge=<name>'') >>> # >>> # It is possible to use the network-bridge script in more complicated >>> # scenarios, such as having two outgoing interfaces, with two bridges, >>> and >>> # two fake interfaces per guest domain. To do things like this, write >>> # yourself a wrapper script, and call network-bridge from it, as >>> appropriate. >>> # >>> (network-script ''network-bridge bridge=xenbr0 netdev=eth0'') >>> # The script used to control virtual interfaces. This can be overridden >>> on a >>> # per-vif basis when creating a domain or a configuring a new vif. The >>> # vif-bridge script is designed for use with the network-bridge script, >>> or >>> # similar configurations. >>> # >>> # If you have overridden the bridge name using >>> # (network-script ''network-bridge bridge=<name>'') then you may wish to do >>> the >>> # same here. The bridge name can also be set when creating a domain or >>> # configuring a new vif, but a value specified here would act as a >>> default. >>> # >>> # If you are using only one bridge, the vif-bridge script will discover >>> that, >>> # so there is no need to specify it explicitly. >>> # >>> (vif-script ''vif-bridge bridge=xenbr0'') >>> ------------------------------------------------------------- >>> >>> An ifconfig gives the following: >>> >>> eth0 Link encap:Ethernet HWaddr 9E:34:72:FC:1B:00 >>> inet adr:192.168.0.3 Bcast:192.168.0.255 Masque:255.255.255.0 >>> adr inet6: fe80::9c34:72ff:fefc:1b00/64 Scope:Lien >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:13 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 lg file transmission:0 >>> RX bytes:2727 (2.6 KiB) TX bytes:4357 (4.2 KiB) >>> lo Link encap:Boucle locale >>> inet adr:127.0.0.1 Masque:255.0.0.0 >>> adr inet6: ::1/128 Scope:Hôte >>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>> RX packets:882 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:882 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 lg file transmission:0 >>> RX bytes:44100 (43.0 KiB) TX bytes:44100 (43.0 KiB) >>> peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >>> adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien >>> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >>> RX packets:260 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:363 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 lg file transmission:1000 >>> RX bytes:39940 (39.0 KiB) TX bytes:35555 (34.7 KiB) >>> Interruption:16 Adresse de base:0x6000 >>> vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >>> adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien >>> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >>> RX packets:24 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 lg file transmission:0 >>> RX bytes:4357 (4.2 KiB) TX bytes:2797 (2.7 KiB) >>> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >>> inet adr:192.168.0.20 Bcast:192.168.0.255 Masque:255.255.255.0 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:24 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 lg file transmission:0 >>> RX bytes:4021 (3.9 KiB) TX bytes:2979 (2.9 KiB) >>> >>> ------------------------------------------------------- >>> >>> Here is the result of the command: >>> >>> bridge name bridge id STP enabled interfaces >>> xenbr0 8000.feffffffffff no vif0.0 >>> peth0 >>> >>> I enclosed the log files generated by xen for the command line : >>> service xend start : >>> >>> I have no idea of the reason why the xen network does not start. (Do I >>> need a package which is not present ?) >>> >>> If anyone could give a way where to investigate ... >>> >>> Thx a lot >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >> As far as I see the ifconfig command says that the bridge is there? >> The eth0 is normal. I only dont know why you have ip address assigned >> for xenbr0? >> >> I dont see anything bad on your configuration. Tell us what does not work? >> >> For domU you have to then specify the bridge in domU config. >> >> For comparison here is mine with more bridges. >> >> eth0 Link encap:Ethernet HWaddr 00:14:C2:3A:AB:63 >> inet addr:192.168.30.11 Bcast:192.168.30.255 Mask:255.255.255.0 >> inet6 addr: fe80::214:c2ff:fe3a:ab63/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:24989 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:17339 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:2253137 (2.1 MiB) TX bytes:3373292 (3.2 MiB) >> >> 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: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) >> >> 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 MTU:1500 Metric:1 >> RX packets:24972 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:17349 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:2351825 (2.2 MiB) TX bytes:3443564 (3.2 MiB) >> Interrupt:20 >> >> peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:126737 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:106149 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:44011994 (41.9 MiB) TX bytes:84835611 (80.9 MiB) >> Interrupt:18 >> >> 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 NOARP MTU:1500 Metric:1 >> RX packets:17339 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:24989 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:3373292 (3.2 MiB) TX bytes:2253137 (2.1 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 NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:1127 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:0 (0.0 b) TX bytes:127247 (124.2 KiB) >> >> vif18.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:97626 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:112923 errors:0 dropped:77 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:81439022 (77.6 MiB) TX bytes:39929936 (38.0 MiB) >> >> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:550 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:74036 (72.3 KiB) TX bytes:0 (0.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 NOARP MTU:1500 Metric:1 >> RX packets:938 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:96030 (93.7 KiB) TX bytes:0 (0.0 b) >> >> Jiri >> > >I am not 100% sure but you don''t need to setup ip for xenbr0. You have already the ip on eth0 in dom0. I believe there should not be IP for xenbr0 and any other bridge. Dom0 has IP on its interface eth0... DomU has setup for bridge or vif in xen-config for domU and IP for interface is configured in xen-config for domU or in domU. Thats how I would approach this. jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users