[Xen-users] Network with xen 4.2

["Artem Metra" <Artem.Metra@xxxxxx>]

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@xxxxxxxxxxxxx
http://lists.xen.org/xen-users