Hi!
I built a xen 3.3.0 kernel on a Debian GNU/Linux 4.0 r4a (AMD64). When I
boot the system without xen everything works fine. When I boot it with
xen the network is not working. Here are the outputs of `ifconfig -a`
for the system with and without xen:
Without xen (everything is as it should be):
-----------------------------------------------------
# ifconfig -a
eth0 Protokoll:Ethernet Hardware Adresse <anonymized>
inet Adresse:192.168.2.105 Bcast:192.168.2.255
Maske:255.255.255.0
inet6 Adresse: fe80::21e:8cff:fece:7f/64
Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:283 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:31321 (30.5 KiB) TX bytes:5393 (5.2 KiB)
Interrupt:177
eth1 Protokoll:UNSPEC Hardware Adresse <anonymized>
BROADCAST MULTICAST 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
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Protokoll: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 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:5176 (5.0 KiB) TX bytes:5176 (5.0 KiB)
sit0 Protokoll:IPv6-nach-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
-----------------------------------------------------
Only eth0 is used, because eth1 is an onbord WLAN card that is disabled
in the bios (when I use ifconfig without the -a option, this interface
is not listed).
With xen (no network interfaces except lo and the tmpbridge which is not
connected to any network interface):
-----------------------------------------------------
# ifconfig -a
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:4660 (4.5 KiB) TX bytes:4660 (4.5 KiB)
tmpbridge Protokoll:Ethernet Hardware Adresse 00:00:00:00:00:00
BROADCAST MULTICAST 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
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
-----------------------------------------------------
I was not able to detect the problem from the logfiles. Which further
information do you need to detect the problem or what should I try out?
Thanks, Ingo!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi! maybe your ethernet device is not supported by the kernel you use with xen. Please post information about that. Please post the lspci output and the content of /etc/network/interfaces Ingo Rauner:> Hi! > > I built a xen 3.3.0 kernel on a Debian GNU/Linux 4.0 r4a (AMD64). When > I boot the system without xen everything works fine. When I boot it > with xen the network is not working. Here are the outputs of `ifconfig > -a` for the system with and without xen: > Without xen (everything is as it should be): > ----------------------------------------------------- > # ifconfig -a > eth0 Protokoll:Ethernet Hardware Adresse <anonymized> > inet Adresse:192.168.2.105 Bcast:192.168.2.255 > Maske:255.255.255.0 > inet6 Adresse: fe80::21e:8cff:fece:7f/64 > Gültigkeitsbereich:Verbindung > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:283 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:1000 > RX bytes:31321 (30.5 KiB) TX bytes:5393 (5.2 KiB) > Interrupt:177 > > eth1 Protokoll:UNSPEC Hardware Adresse <anonymized> > BROADCAST MULTICAST 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 > Kollisionen:0 Sendewarteschlangenlänge:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > lo Protokoll: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 Metric:1 > RX packets:66 errors:0 dropped:0 overruns:0 frame:0 > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:5176 (5.0 KiB) TX bytes:5176 (5.0 KiB) > > sit0 Protokoll:IPv6-nach-IPv4 NOARP MTU:1480 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > ----------------------------------------------------- > Only eth0 is used, because eth1 is an onbord WLAN card that is > disabled in the bios (when I use ifconfig without the -a option, this > interface is not listed). > > With xen (no network interfaces except lo and the tmpbridge which is > not connected to any network interface): > ----------------------------------------------------- > # ifconfig -a > lo Protokoll:Lokale Schleife inet Adresse:127.0.0.1 > Maske:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:60 errors:0 dropped:0 overruns:0 frame:0 > TX packets:60 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:4660 (4.5 KiB) TX bytes:4660 (4.5 KiB) > > tmpbridge Protokoll:Ethernet Hardware Adresse 00:00:00:00:00:00 > BROADCAST MULTICAST 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 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > ----------------------------------------------------- > > I was not able to detect the problem from the logfiles. Which further > information do you need to detect the problem or what should I try out? > > Thanks, Ingo! > > _______________________________________________ > 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
Ingo Rauner wrote:> Hi! > > I built a xen 3.3.0 kernel on a Debian GNU/Linux 4.0 r4a (AMD64). When > I boot the system without xen everything works fine. When I boot it > with xen the network is not working. Here are the outputs of `ifconfig > -a` for the system with and without xen: > Without xen (everything is as it should be): > ----------------------------------------------------- > # ifconfig -a > eth0 Protokoll:Ethernet Hardware Adresse <anonymized> > inet Adresse:192.168.2.105 Bcast:192.168.2.255 > Maske:255.255.255.0 > inet6 Adresse: fe80::21e:8cff:fece:7f/64 > Gültigkeitsbereich:Verbindung > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:283 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:1000 > RX bytes:31321 (30.5 KiB) TX bytes:5393 (5.2 KiB) > Interrupt:177 > > eth1 Protokoll:UNSPEC Hardware Adresse <anonymized> > BROADCAST MULTICAST 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 > Kollisionen:0 Sendewarteschlangenlänge:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > lo Protokoll: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 Metric:1 > RX packets:66 errors:0 dropped:0 overruns:0 frame:0 > TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:5176 (5.0 KiB) TX bytes:5176 (5.0 KiB) > > sit0 Protokoll:IPv6-nach-IPv4 NOARP MTU:1480 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > ----------------------------------------------------- > Only eth0 is used, because eth1 is an onbord WLAN card that is > disabled in the bios (when I use ifconfig without the -a option, this > interface is not listed). > > With xen (no network interfaces except lo and the tmpbridge which is > not connected to any network interface): > ----------------------------------------------------- > # ifconfig -a > lo Protokoll:Lokale Schleife inet Adresse:127.0.0.1 > Maske:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:60 errors:0 dropped:0 overruns:0 frame:0 > TX packets:60 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:4660 (4.5 KiB) TX bytes:4660 (4.5 KiB) > > tmpbridge Protokoll:Ethernet Hardware Adresse 00:00:00:00:00:00 > BROADCAST MULTICAST 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 > Kollisionen:0 Sendewarteschlangenlänge:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > ----------------------------------------------------- > > I was not able to detect the problem from the logfiles. Which further > information do you need to detect the problem or what should I try out? > > Thanks, Ingo! >I have a similar problem. I have researched enough to realize that my OpenSuse 10.3 and Xen 3.3 have some compatibility issues (mainly in the location of network scripts like ifup and ifdown). If I switch from network-bridge to network-route for Xen, the interfaces come up as expected. If I modify the network-bridge script, I can get the interface to come up. I have to manually insert the route. Ken Cobler> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
When I built xen, the kernel sources provided by xensource were downloaded automatically. So I am using a Linux 2.6.18.8 kernel without distribution dependent patches except the patches by xensource for using the kernel with xen (that''s how I understood the description from xensource). With Debian I am using Linux 2.6.18-6-amd64 (with Debian GNU/Linux 4.0 r4a patches of course). lspci # always the same with and without xen - the ethernet controller is the 4th one from bottom ---------------------------------------- 00:00.0 Host bridge: Intel Corporation Unknown device 29c0 (rev 02) 00:01.0 PCI bridge: Intel Corporation Unknown device 29c1 (rev 02) 00:1a.0 USB Controller: Intel Corporation Unknown device 2937 (rev 02) 00:1a.1 USB Controller: Intel Corporation Unknown device 2938 (rev 02) 00:1a.2 USB Controller: Intel Corporation Unknown device 2939 (rev 02) 00:1a.7 USB Controller: Intel Corporation Unknown device 293c (rev 02) 00:1b.0 Audio device: Intel Corporation Unknown device 293e (rev 02) 00:1c.0 PCI bridge: Intel Corporation Unknown device 2940 (rev 02) 00:1c.4 PCI bridge: Intel Corporation Unknown device 2948 (rev 02) 00:1c.5 PCI bridge: Intel Corporation Unknown device 294a (rev 02) 00:1d.0 USB Controller: Intel Corporation Unknown device 2934 (rev 02) 00:1d.1 USB Controller: Intel Corporation Unknown device 2935 (rev 02) 00:1d.2 USB Controller: Intel Corporation Unknown device 2936 (rev 02) 00:1d.7 USB Controller: Intel Corporation Unknown device 293a (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation Unknown device 2916 (rev 02) 00:1f.2 IDE interface: Intel Corporation Unknown device 2920 (rev 02) 00:1f.3 SMBus: Intel Corporation Unknown device 2930 (rev 02) 00:1f.5 IDE interface: Intel Corporation Unknown device 2926 (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0611 (rev a2) 02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364 (rev 12) 03:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03) 03:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03) 05:03.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) ---------------------------------------- Content of /etc/network/interfaces ---------------------------------------- # The loopback network interface auto lo iface lo inet loopback ---------------------------------------- Is it possible to provide e.g. the kernel sources of Debian to the build scripts of xen? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m not very familiar with Debian, but there seem to be no network configuration of eth0. Have you tried to put something like --------------- auto eth0 iface eth0 inet static address xxx.xxx.xxx.xxx --------------- in your /etc/network/interfaces ? Ingo Rauner schrieb:> When I built xen, the kernel sources provided by xensource were > downloaded automatically. So I am using a Linux 2.6.18.8 kernel > without distribution dependent patches except the patches by xensource > for using the kernel with xen (that''s how I understood the description > from xensource). With Debian I am using Linux 2.6.18-6-amd64 (with > Debian GNU/Linux 4.0 r4a patches of course). > > lspci # always the same with and without xen - the ethernet controller > is the 4th one from bottom > ---------------------------------------- > 00:00.0 Host bridge: Intel Corporation Unknown device 29c0 (rev 02) > 00:01.0 PCI bridge: Intel Corporation Unknown device 29c1 (rev 02) > 00:1a.0 USB Controller: Intel Corporation Unknown device 2937 (rev 02) > 00:1a.1 USB Controller: Intel Corporation Unknown device 2938 (rev 02) > 00:1a.2 USB Controller: Intel Corporation Unknown device 2939 (rev 02) > 00:1a.7 USB Controller: Intel Corporation Unknown device 293c (rev 02) > 00:1b.0 Audio device: Intel Corporation Unknown device 293e (rev 02) > 00:1c.0 PCI bridge: Intel Corporation Unknown device 2940 (rev 02) > 00:1c.4 PCI bridge: Intel Corporation Unknown device 2948 (rev 02) > 00:1c.5 PCI bridge: Intel Corporation Unknown device 294a (rev 02) > 00:1d.0 USB Controller: Intel Corporation Unknown device 2934 (rev 02) > 00:1d.1 USB Controller: Intel Corporation Unknown device 2935 (rev 02) > 00:1d.2 USB Controller: Intel Corporation Unknown device 2936 (rev 02) > 00:1d.7 USB Controller: Intel Corporation Unknown device 293a (rev 02) > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) > 00:1f.0 ISA bridge: Intel Corporation Unknown device 2916 (rev 02) > 00:1f.2 IDE interface: Intel Corporation Unknown device 2920 (rev 02) > 00:1f.3 SMBus: Intel Corporation Unknown device 2930 (rev 02) > 00:1f.5 IDE interface: Intel Corporation Unknown device 2926 (rev 02) > 01:00.0 VGA compatible controller: nVidia Corporation Unknown device > 0611 (rev a2) > 02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown > device 4364 (rev 12) > 03:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 > AHCI Controller (rev 03) > 03:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 > AHCI Controller (rev 03) > 05:03.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) > ---------------------------------------- > > Content of /etc/network/interfaces > ---------------------------------------- > # The loopback network interface > auto lo > iface lo inet loopback > ---------------------------------------- > > Is it possible to provide e.g. the kernel sources of Debian to the > build scripts of xen?_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I''m not very familiar with Debian, but there seem to be no network > configuration of eth0. Have you tried to put something like > > --------------- > auto eth0 > iface eth0 inet static > address xxx.xxx.xxx.xxx > --------------- > > in your /etc/network/interfaces ?If I do so, ifup prints the following errors: --------------- SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. --------------- I think the ethernet device is not supported by the kernel, as you mentioned before (maybe the device is to new for the kernel version provided by xensource). How can I build a different kernel to use it with xen? I have not found any patches at xen.org that can be apply to e.g. my Debian kernel to use it as a Dom0. Is there a how to or something like that? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I managed to get my xen-dom0-kernel working with my nvidia mcp67 chipset by changing the sources manually. I just searched the changelogs and patches at kernel.org... perhaps this will work for you too, but it''s not very simple ;) For Centos 5.2 there is a patched 2.6.18 kernel available wich will work with far more hardware than the kernel from xen.org. Kernels > 2.6.18 are available for Ubuntu and some Fedora releases, but that''s imo a very bad solution. On my hardware the Ubuntu kernel was running, but the cpu scaling was broken. Ingo Rauner schrieb:>> I''m not very familiar with Debian, but there seem to be no network >> configuration of eth0. Have you tried to put something like >> >> --------------- >> auto eth0 >> iface eth0 inet static >> address xxx.xxx.xxx.xxx >> --------------- >> >> in your /etc/network/interfaces ? > > If I do so, ifup prints the following errors: > --------------- > SIOCSIFADDR: No such device > eth0: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > eth0: ERROR while getting interface flags: No such device > Failed to bring up eth0. > --------------- > > I think the ethernet device is not supported by the kernel, as you > mentioned before (maybe the device is to new for the kernel version > provided by xensource). How can I build a different kernel to use it > with xen? I have not found any patches at xen.org that can be apply to > e.g. my Debian kernel to use it as a Dom0. Is there a how to or > something like that?_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users