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)
I do not know what to search for ... No idea of what would be the problem. Does
anyone could help diagnose ?
Thx a lot.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello, Futhermore, here are enclosed the log files generated by xne for the command line : service xend start : Thx ----- Original Message ----- From: "TURPIN Olivier" <turpin_olivier@bigfoot.com> To: "Yves-Gaël Chény" <yves-gael.cheny@tranquil-it-systems.fr> Sent: Monday, November 19, 2007 12:40 PM Subject: Re: [Xen-users] xen 3.1 network configuration> Heelo Yves, > > Here is the result of the command: > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > > This seemed normal to me ? > > Thx > > ----- Original Message ----- > From: "Yves-Gaël Chény" <yves-gael.cheny@tranquil-it-systems.fr> > To: "TURPIN Olivier" <turpin_olivier@bigfoot.com> > Sent: Monday, November 19, 2007 9:32 AM > Subject: Re: [Xen-users] xen 3.1 network configuration > > > TURPIN Olivier a écrit : >> 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) >> I do not know what to search for ... No idea of what would be the >> problem. Does >> anyone could help diagnose ? >> Thx a lot. >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > can you send us the result of > brctl show > > regards > yves > > -- > Yves-Gaël Chény > Directeur technique > > 44 Boulevard des Pas Enchantés > 44230 St Sébastien sur Loire > Tel : 02 40 97 62 67 - 08 73 77 24 91 > GSM : 06 98 58 41 55 > http://www.tranquilitsystems.com/ > yves-gael.cheny@tranquil-it-systems.fr > > Tranquil IT Systems . SAS 37 000 ¤ > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, I am using xen for hosting servers (database and apache). In order to configure the domU, I am using the SDL. But I am experiencing strange behaviors of the event managers. 1) The mouse becomes uncontrollable. It moves from one point to the other end of the SDL window without any reason. 2) On the login screen (GDM) , the login field is fulfilled with "@" characters without my typing anything. I wonder what configuration parameter could set the things better ? Anyone has any idea or similar experience ? I am using mandriva 2008 as Dom0, and mandriva 2007.1 as domU. Thx for any help ! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Maybe you can try using VNC or running a vnc based X server in DomU. Another method is to install freenx, or possibly using XDMCP. Br, Emre On Nov 19, 2007 8:21 PM, TURPIN Olivier <turpin_olivier@bigfoot.com> wrote:> Hello, > > I am using xen for hosting servers (database and apache). > In order to configure the domU, I am using the SDL. But I am experiencing > strange behaviors of the event managers. > 1) The mouse becomes uncontrollable. It moves from one point to the other > end of the SDL window without any reason. > 2) On the login screen (GDM) , the login field is fulfilled with "@" > characters without my typing anything. > I wonder what configuration parameter could set the things better ? > Anyone has any idea or similar experience ? > > I am using mandriva 2008 as Dom0, and mandriva 2007.1 as domU. > > Thx for any help ! > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Emre Erenoglu erenoglu@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users