[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen network Dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Ko0nz <yesiko0nz@xxxxxxxxx>
  • Date: Tue, 5 Jun 2007 22:47:28 +0200
  • Delivery-date: Tue, 05 Jun 2007 13:46:15 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gMOzyG/DthQDLT57q2x8tK2o6PdPxDlSiNN3MvLC4ytdCWqk7p29qu/lAEUXwgnYxawqcicMxOLcnAQJLyX9Xpz8EeA3f5IcklRB20HluATnOTHW9lY33WwqUbk8CMUIbtAOzsZzE9wW6HRygPRjL4lGkwC8vej6/2xKGP/aBzA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

is it possible that something is not build in the kernel?
i wonder if i souldn't have a try with the compil....

On 6/5/07, ko0nz <yesiko0nz@xxxxxxxxx> wrote:
hi,

i've tried again Debian testing, with xen 3.1 binary.
it works fine but i can't have the networt working:
i've have an ethernet card with
static IP: 172.20.2.160
gateway: 172.20.2.1
uname -r :2.6.18-xen

without xen, the network works fine.

here's my output:

eth0      Lien encap:Ethernet  HWaddr 00:0F:FE:6B:57:32
          inet adr:172.20.2.160  Bcast:172.20.2.255  Masque:255.255.255.0
          adr inet6: fe80::20f:feff:fe6b:5732/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:140 (140.0 b)  TX bytes:3370 (3.2 KiB)

lo        Lien 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:286 errors:0 dropped:0 overruns:0 frame:0
          TX packets:286 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:23600 (23.0 KiB)  TX bytes:23600 (23.0 KiB)

peth0     Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet adr:169.254.249.7  Bcast:169.254.255.255  Masque:255.255.0.0
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:322 errors:0 dropped:481 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:100
          RX bytes:53172 (51.9 KiB)  TX bytes:7674 (7.4 KiB)
          Adresse de base:0x1100 Mémoire:f0500000-f0520000

vif0.0    Lien 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:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:3370 (3.2 KiB)  TX bytes:210 (210.0 b)

xenbr0    Lien encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:2922 (2.8 KiB)  TX bytes:168 (168.0 b)

Table de routage IP du noyau
Destination     Passerelle      Genmask         Indic   MSS Fenêtre irtt Iface
172.20.2.0      0.0.0.0         255.255.255.0   U         0 0          0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 peth0
0.0.0.0         172.20.2.1      0.0.0.0         UG        0 0          0 eth0

i think i forgot something...

thank in advance for any information.

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


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.