RE: [Xen-users] No eth0 device found in domU

["Boudreau Luc" <luc.boudreau@xxxxxxxxxxxx>]

See this : vif = [ '' ]

That's a bad sign. "RTFM" as they say. 
http://bits.xensource.com/Xen/docs/user.pdf

Luc



-----Message d'origine-----
De : xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] De la part de Jens Seidel
Envoyé : 25 septembre 2007 08:48
À : xen-users@xxxxxxxxxxxxxxxxxxx
Objet : [Xen-users] No eth0 device found in domU

Hi,

I tried already a long time to enable network in my domU but I always
fail with:

# ifconfig eth0 192.168.0.1 up
SIOCSIFADDR: No such device
SIOCGIFFLAGS: No such device

Do I need to load a kernel module?

I use OpenSuse 10.2 with kernel 2.6.18.8-0.5-xen (for both domU and dom0).

My config:

kernel = "/boot/vmlinuz-xen"
ramdisk = "/home/jens/initrd.gz"
memory = 1024
name = "debian"
disk = [ "/home/jens/hda,hda1,w", "/home/jens/hda,hda2,w,", "/,hda3,r" ]
root = "/dev/hda2 ro"
vif = [ '' ]

network settings in dom0:

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:19:5B:70:7B:6F  
          inet addr:192.168.0.1  Bcast:255.255.255.255 Mask:255.255.255.0
          inet6 addr: fe80::219:5bff:fe70:7b6f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:310334 errors:0 dropped:0 overruns:0 frame:0
          TX packets:177949 errors:652 dropped:0 overruns:0 carrier:652
          collisions:104425 txqueuelen:1000 
          RX bytes:318922367 (304.1 Mb)  TX bytes:21339374 (20.3 Mb)
          Interrupt:17 Base address:0xb000 

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:82102 errors:0 dropped:0 overruns:0 frame:0
          TX packets:82102 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5688468 (5.4 Mb)  TX bytes:5688468 (5.4 Mb)

vif6.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  
          UP BROADCAST NOARP  MTU:1500  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)

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: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)

Shouldn't there are a peth0, ...?

# brctl showstp xenbr0
xenbr0
 bridge id              8000.feffffffffff
 designated root        8000.feffffffffff
 root port                 0                    path cost                  0
 max age                  20.00                 bridge max age            20.00
 hello time                2.00                 bridge hello time          2.00
 forward delay             0.00                 bridge forward delay       0.00
 ageing time             300.01
 hello timer               0.58                 tcn timer                  0.00
 topology change timer     0.00                 gc timer                   0.04
 flags  


vif6.0 (0)
 port id                0000                    state                  disabled
 designated root        8000.feffffffffff       path cost                100
 designated bridge      8000.feffffffffff       message age timer          0.00
 designated port        8001                    forward delay timer        0.00
 designated cost           0                    hold timer                 0.00
 flags  

I wonder especially about the state "disabled".

Network related domU kernel messages:
XENBUS: Device with no driver: device/vif/0

# xm list -l
 (device (vif (backend 0) (script vif-bridge) (mac 00:16:3e:05:5f:d0)))


Any idea?
Jens

_______________________________________________
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