Hallo Mailinglist:),
i used xen 4.1 with xend xm a while. I compiled the unstable 4.2 today and most
thinks run fine :). I have only one big problem, the network for my
guestsystems. It don't want to work. Hopefully somebody can help me.
In Xen 4.1 i only wrote the following line in my questconfig:
vif = [ "bridge=eth0,script=vif-bridge" ]
And everything works fine. This does not work anymore and maybe somebody knows
why:).
I have a Debian 6.0.5 as dom0 the ifconfig tells me the following:
eth0 Link encap:Ethernet Hardware Adresse 00:21:70:49:2e:98
inet Adresse:129.217.43.51 Bcast:129.217.43.127
Maske:255.255.255.128
inet6-Adresse: fe80::221:70ff:fe49:2e98/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:176525 errors:0 dropped:0 overruns:0 frame:0
TX packets:63344 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:256528227 (244.6 MiB) TX bytes:5984886 (5.7 MiB)
Interrupt:21 Speicher:febe0000-fec00000
lo Link encap: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 Metrik:1
RX packets:3967 errors:0 dropped:0 overruns:0 frame:0
TX packets:3967 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:37747530 (35.9 MiB) TX bytes:37747530 (35.9 MiB)
xl.config:
## Global XL config file ##
# automatically balloon down dom0 when xen doesn't have enough free
# memory to create a domain
#autoballoon=1
# full path of the lockfile used by xl during domain creation
lockfile="/var/lock/xl"
# default vif script
vifscript="vif-bridge"
# default output format used by "xl list -l"
#output_format="json"
# first block device to be used for temporary VM disk mounts
#blkdev_start="xvda"
# default option to run hotplug scripts from xl
# if disabled the old behaviour will be used, and hotplug scripts will be
# launched by udev.
#run_hotplug_scripts=1
Thank you very much:).
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
On 24 August 2012 20:13, Artem Metra <Artem.Metra@gmx.de> wrote:> Hallo Mailinglist:), > i used xen 4.1 with xend xm a while. I compiled the unstable 4.2 today and most thinks run fine :). I have only one big problem, the network for my guestsystems. It don''t want to work. Hopefully somebody can help me. > > In Xen 4.1 i only wrote the following line in my questconfig: > vif = [ "bridge=eth0,script=vif-bridge" ] > > And everything works fine. This does not work anymore and maybe somebody knows why:). > > I have a Debian 6.0.5 as dom0 the ifconfig tells me the following: > eth0 Link encap:Ethernet Hardware Adresse 00:21:70:49:2e:98 > inet Adresse:129.217.43.51 Bcast:129.217.43.127 Maske:255.255.255.128 > inet6-Adresse: fe80::221:70ff:fe49:2e98/64 Gültigkeitsbereich:Verbindung > UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 > RX packets:176525 errors:0 dropped:0 overruns:0 frame:0 > TX packets:63344 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:1000 > RX bytes:256528227 (244.6 MiB) TX bytes:5984886 (5.7 MiB) > Interrupt:21 Speicher:febe0000-fec00000 > > lo Link encap: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 Metrik:1 > RX packets:3967 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3967 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:37747530 (35.9 MiB) TX bytes:37747530 (35.9 MiB) > > xl.config: > ## Global XL config file ## > > # automatically balloon down dom0 when xen doesn''t have enough free > # memory to create a domain > #autoballoon=1 > > # full path of the lockfile used by xl during domain creation > lockfile="/var/lock/xl" > > # default vif script > vifscript="vif-bridge" > > # default output format used by "xl list -l" > #output_format="json" > > # first block device to be used for temporary VM disk mounts > #blkdev_start="xvda" > > # default option to run hotplug scripts from xl > # if disabled the old behaviour will be used, and hotplug scripts will be > # launched by udev. > #run_hotplug_scripts=1 > > Thank you very much:). > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-usersHi, XL doesn''t create the bridge for you. First create a bridge with bridge-utils (brctl addbr <brigdgename>) then the guest vms will have their vif adapters added to the bridge automatically via udev. Joseph. -- CTO | Orion Virtualisation Solutions | www.orionvm.com.au Phone: 1300 56 99 52 | Mobile: 0428 754 846
On Sat, 2012-08-25 at 09:00 +0100, Joseph Glanville wrote:> XL doesn''t create the bridge for you. > > First create a bridge with bridge-utils (brctl addbr <brigdgename>) > then the guest vms will have their vif adapters added to the bridge > automatically via udev.Also see http://wiki.xen.org/wiki/Network_Configuration_Examples_%28Xen_4.1%2B%29 for per distro configuration hints. http://wiki.xen.org/wiki/XL#Upgrading_from_xend might be useful too. Ian.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Artem Metra <Artem.Metra@gmx.de> schrieb:>In Xen 4.1 i only wrote the following line in my questconfig: >vif = [ "bridge=eth0,script=vif-bridge" ] > >And everything works fine. This does not work anymore and maybe >somebody knows why:).It seems you have no bridge set up. If you use 4.2 (with xl) you have to configure your Dom0 host bridge byself with your OS network tools / topology. Xen does not anymore set up this byself as this leads to many distro / platform specific problems in the past - it is much more stable to use your OS / distros tools for that. In this case - use the debian network config stack by i.e. /etc/config/interfaces (hope this is right by mind) to set up your bridge i.e. bridge0. 4.2 will then add your DomUs to the configured bride by udev. With xl no xend is required anymore and should be disabled. So this is no bug - it's a feature... ß) hth cheers, Niels. - -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com -----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iIEEAREIAEEFAlA5IzQ6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDYIEAJkB9xzq+QHi BXiiTuldLMm6q2YNIgCfakqF3CxVVtqiLasqu+fRf+odgbw=bPz9 -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
i hope it is anwsering partially to my question in this thread: http://lists.xen.org/archives/html/xen-users/2012-08/msg00228.html "hvm network interface slow in 100 Mb" I do set-up myself bridges but guest-side (microsoft ones) interfaces appear in 100Mb. Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users