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@lists.xensource.com
http://lists.xensource.com/xen-users
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@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] De la part de Jens Seidel
Envoyé : 25 septembre 2007 08:48
À : xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Luc, On Wed, Sep 26, 2007 at 12:51:21PM -0400, Boudreau Luc wrote:> See this : vif = [ '''' ] > > That''s a bad sign. "RTFM" as they say. http://bits.xensource.com/Xen/docs/user.pdfdon''t know what you try to say but I read the documentation carefully. Probably you noticed that I supplied no MAC address and assumed that udev creates eth1, eth2, ... instead of eth0. This is *not* true! No ethernet at all is created in domU! I tested various settings with OpenSuse''s 3.0.3 rpms (including a fixed MAC) and always failed! I compiled that''s why Xen 3.1 (is this a stable version? http://xen.xensource.com/ provides a link to 3.0 in "Get Started with Xen!", the 3.1 source doesn''t contain a changelog and its Readme mentions only 3.0, also a FAQ(?) didn''t mentioned 3.1 as released version!?) Version 3.1 was also funny: My dom0 network did no longer worked (even without a domU). The output of ifconfig and route looked good to me (I also deactivated the firewall for tests), nevertheless I was not able to resolve it. Doesn''t Xen bridging also initiates connections between eth0 and vif0.0? How can I check these? After switching from bridge setup to NAT it worked well! So my problem is now solved. Jens _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> 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?Do you have the Xen frontend network driver (xennet) installed and properly loaded on your domU system?> Network related domU kernel messages: > XENBUS: Device with no driver: device/vif/0This usually indicates that something with xennet is wrong... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Sep 27, 2007 at 08:53:04AM +0100, Fischer, Anna wrote:> > 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? > > Do you have the Xen frontend network driver (xennet) installed and > properly loaded on your domU system? > > > Network related domU kernel messages: > > XENBUS: Device with no driver: device/vif/0 > > This usually indicates that something with xennet is wrong...Ah, didn''t know this ... I tried to install Debian using the network installer image containing a kernel and an initrd. Because I didn''t know whether I need to have kernel modules in the Debian domU initrd I copied /lib/modules/2.6.18-xen/ from OpenSuse 10.2 (dom0) into the initrd. (Now I think I understand that I have to provide each domU software modules such as ext2, ext3, ... and a few XEN specific modules such as xennet but no modules for raw hardware access (usb-ohci, eth drivers ...), right? Is this documented somewhere?) I did this step (extenting initrd) multiple times (using: # mkdir initrd # cat ../debian-installer/i386/initrd | cpio --extract --make-directories # cp -r /lib/modules/2.6.18-xen/ lib/modules/ # find | cpio -o -H newc | gzip -9 > ../initrd.gz ) so I really doubt that I did something wrong. Exactly the same steps worked with Xen 3.1 (at least after switching to NAT instead of bridge as my network was completely inaccessible with Xen 3.1). Sorry, I don''t want to reinstall the Xen 3.0 RPMs as I have it currently working but maybe OpenSuse RPMs are not working? It is unlikely as I searched for similar trouble without success. Thanks, Jens _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users