Hello,
I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear in
domU.
I have 3 servers running FC3 and Xen 2 with various domUs since a year.
Everything is fine on that front.
I took one of the server, upgraded it to FC5 and did the following:
- yum install xen kernel-xen0 kernel-xenU
- grub.conf contains
title Fedora Core (2.6.15-1.2054_FC5xen0
root (hd0,0)
kernel /boot/xen.gz-2.6.15-1.2054_FC5
module /boot/vmlinuz-2.6.15-1.2054_FC5xen0 root=LABEL=/ ro console=tty0 noscsi
module /boot/initrd-2.6.15-1.2054_FC5xen0.img
- rebooted with the xen0 kernel
- kept the default xend-config.sxp to use bridging
- started xend
- copied a domU FC3 image from another server (tried also with a trustix image)
- mounted the FC3 image in loop fs and copied (cp -a)
/lib/modules/2.6.15-1.2054_FC5xenU to it
- created a domU configuration file:
kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img"
memory = 128
name = "test"
vif = [ '''' ]
disk = [ ''file:/images/fc3,sda1,w'' ]
root = "/dev/sda1 ro"
extra = "4"
- xm create -c test.conf
- everything in domU is fine except that eth0 is not seen:
ifconfig eth0
eth0: error fetching interface information: Device not found
- "ifconfig -a" shows lo and sit0 only
- on dom0:
brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no
peth0
vif0.0
vif1.0
- domU image contains valid ifcfg-eth0 configuration file
I tried to add network configuration into the domU configuration file:
ip="10.10.10.10"
netmask="255.255.255.0"
gateway="10.10.10.1"
broadcast="10.10.10.255"
and got the same results.
- I tried with and without a ramdisk image in the domU conf file (getting
desperate here)
- no errors in domU dmesg or with "xen dmesg" on dom0
I really don''t know where to go from here. I made several attempts with
variations in config files but always got the same problem. Am I missing
something obvious? Any suggestion as to what tools I can use to troubleshoot?
Any help would be greatly appreciated.
Thanks alot
Denis
---------------------------------
Lèche-vitrine ou lèche-écran ? Yahoo! Magasinage.
--0-1417282803-1143306604=:25147
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Hello,<br><br>I am trying to run Xen 3 on FC5, but I cannot have the
eth0 interface appear in domU.<br><br>I have 3 servers running FC3
and Xen 2 with various domUs since a year. Everything is fine on that
front.<br><br>I took one of the server, upgraded it to FC5 and did
the following:<br><br>- yum install xen kernel-xen0
kernel-xenU<br>- grub.conf contains<br> title Fedora Core
(2.6.15-1.2054_FC5xen0<br> root (hd0,0)<br>
kernel /boot/xen.gz-2.6.15-1.2054_FC5<br> module
/boot/vmlinuz-2.6.15-1.2054_FC5xen0 root=LABEL=/ ro console=tty0
noscsi<br> module
/boot/initrd-2.6.15-1.2054_FC5xen0.img<br>- rebooted with the xen0
kernel<br>- kept the default xend-config.sxp to use bridging<br>-
started xend<br>- copied a domU FC3 image from another server (tried also
with a trustix image)<br>- mounted the FC3 image in loop fs and copied (cp
-a) /lib/modules/2.6.15-1.2054_FC5xenU to it<br>- created a domU
configuration file:<br> kernel
"/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img"<br> memory =
128<br> name = "test"<br> vif = [
'''' ]<br> disk = [
''file:/images/fc3,sda1,w'' ]<br> root =
"/dev/sda1 ro"<br> extra = "4"<br>- xm
create -c test.conf<br>- everything in domU is fine except that eth0 is
not seen:<br> ifconfig eth0<br> eth0: error
fetching interface information: Device not found<br>- "ifconfig
-a" shows lo and sit0 only<br>- on
dom0:<br> brctl show<br>
bridge name bridge
id
STP enabled
interfaces<br>
xenbr0
8000.feffffffffff
no
peth0<br>
vif0.0<br>
vif1.0<br>- domU
image contains valid ifcfg-eth0 configuration file<br> I tried
to add network configuration into the domU configuration
file:<br>
ip="10.10.10.10"<br>
netmask="255.255.255.0"<br>
gateway="10.10.10.1"<br>
broadcast="10.10.10.255"<br> and got the
same results.<br>- I tried with and without a ramdisk image in the domU
conf file (getting desperate here)<br>- no errors in domU dmesg or with
"xen dmesg" on dom0<br><br>I really don''t know
where to go from here. I made several attempts with variations in config files
but always got the same problem. Am I missing something obvious? Any suggestion
as to what tools I can use to troubleshoot?<br>Any help would be greatly
appreciated.<br><br>Thanks
alot<br><br>Denis<br><p>
<hr size=1>Lèche-vitrine ou lèche-écran ? <a
href="http://cf.shopping.yahoo.com"><b>Yahoo!
Magasinage</b></a>.<br>
--0-1417282803-1143306604=:25147--
--===============1112595211=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
--===============1112595211==--
Hello, I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear in domU. I read nearly everything in this list that could look similar to my problem but to no avail. I have 3 servers running FC3 and Xen 2 with various domUs since a year. Everything is fine on that front. I took one of the server, upgraded it to FC5 and did the following: - yum install xen kernel-xen0 kernel-xenU - grub.conf contains title Fedora Core (2.6.15-1.2054_FC5xen0 root (hd0,0) kernel /boot/xen.gz-2.6.15-1.2054_FC5 module /boot/vmlinuz-2.6.15-1.2054_FC5xen0 root=LABEL=/ ro console=tty0 noscsi module /boot/initrd-2.6.15-1.2054_FC5xen0.img - rebooted with the xen0 kernel - kept the default xend-config.sxp to use bridging - started xend - copied a domU FC3 image from another server (tried also with a trustix image) - mounted the FC3 image in loop fs and copied (cp -a) /lib/modules/2.6.15-1.2054_FC5xenU to it - created a domU configuration file: kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img" memory = 128 name = "test" vif = [ '''' ] disk = [ ''file:/images/fc3,sda1,w'' ] root = "/dev/sda1 ro" extra = "4" - xm create -c test.conf - everything in domU is fine except that eth0 is not seen: ifconfig eth0 eth0: error fetching interface information: Device not found - "ifconfig -a" shows lo and sit0 only - on dom0: brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif1.0 - domU image contains valid ifcfg-eth0 configuration file I tried to add network configuration into the domU configuration file: ip="10.10.10.10" netmask="255.255.255.0" gateway="10.10.10.1" broadcast="10.10.10.255" and got the same results. - I tried with and without a ramdisk image in the domU conf file (getting desperate here) - no errors in domU dmesg or with "xen dmesg" on dom0 I really don''t know where to go from here. I made several attempts with variations in config files but always got the same problem. Am I missing something obvious? Any suggestion as to what tools I can use to troubleshoot? Any help would be greatly appreciated. Thanks a lot Denis _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Denis Lebeuf wrote:> Hello, > > I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear > in domU. I read nearly everything in this list that could look similar to my > problem but to no avail. > I have 3 servers running FC3 and Xen 2 with various domUs since a year. > Everything is fine on that front. > > I took one of the server, upgraded it to FC5 and did the following: > > - yum install xen kernel-xen0 kernel-xenU > - grub.conf contains > title Fedora Core (2.6.15-1.2054_FC5xen0 > root (hd0,0) > kernel /boot/xen.gz-2.6.15-1.2054_FC5 > module /boot/vmlinuz-2.6.15-1.2054_FC5xen0 root=LABEL=/ ro console=tty0 > noscsi > module /boot/initrd-2.6.15-1.2054_FC5xen0.img > - rebooted with the xen0 kernel > - kept the default xend-config.sxp to use bridging > - started xend > - copied a domU FC3 image from another server (tried also with a trustix > image) > - mounted the FC3 image in loop fs and copied (cp > -a) /lib/modules/2.6.15-1.2054_FC5xenU to it > - created a domU configuration file: > kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img" > memory = 128 > name = "test" > vif = [ '''' ] > disk = [ ''file:/images/fc3,sda1,w'' ] > root = "/dev/sda1 ro" > extra = "4" >Denis, it''s just a guess, but why don''t you try and assign a MAC address to your domU and give it another shot? Greetz, Andrej> - xm create -c test.conf > - everything in domU is fine except that eth0 is not seen: > ifconfig eth0 > eth0: error fetching interface information: Device not found > - "ifconfig -a" shows lo and sit0 only > - on dom0: > brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no peth0 > vif0.0 > vif1.0 > - domU image contains valid ifcfg-eth0 configuration file > I tried to add network configuration into the domU configuration file: > ip="10.10.10.10" > netmask="255.255.255.0" > gateway="10.10.10.1" > broadcast="10.10.10.255" > and got the same results. > - I tried with and without a ramdisk image in the domU conf file (getting > desperate here) > - no errors in domU dmesg or with "xen dmesg" on dom0 > > I really don''t know where to go from here. I made several attempts with > variations in config files but always got the same problem. Am I missing > something obvious? Any suggestion as to what tools I can use to troubleshoot? > Any help would be greatly appreciated. > > Thanks a lot > > Denis > > _______________________________________________ > 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
I have also had this problem with the FC5 domU kernel. It turns out they decided to make the xennet kernel driver a module instead of compiled in. All you need to do is in the "/etc/modprobe.conf" file of your guest, make sure it has the following line: alias eth0 xennet This means the kernel will load the xennet module for eth0. Thanks, Phil Evans. Denis Lebeuf wrote:> Hello, > > I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear > in domU. I read nearly everything in this list that could look similar to my > problem but to no avail. > > I have 3 servers running FC3 and Xen 2 with various domUs since a year. > Everything is fine on that front. > > I took one of the server, upgraded it to FC5 and did the following: > > - yum install xen kernel-xen0 kernel-xenU > - grub.conf contains > title Fedora Core (2.6.15-1.2054_FC5xen0 > root (hd0,0) > kernel /boot/xen.gz-2.6.15-1.2054_FC5 > module /boot/vmlinuz-2.6.15-1.2054_FC5xen0 root=LABEL=/ ro console=tty0 > noscsi > module /boot/initrd-2.6.15-1.2054_FC5xen0.img > - rebooted with the xen0 kernel > - kept the default xend-config.sxp to use bridging > - started xend > - copied a domU FC3 image from another server (tried also with a trustix > image) > - mounted the FC3 image in loop fs and copied (cp > -a) /lib/modules/2.6.15-1.2054_FC5xenU to it > - created a domU configuration file: > kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img" > memory = 128 > name = "test" > vif = [ '''' ] > disk = [ ''file:/images/fc3,sda1,w'' ] > root = "/dev/sda1 ro" > extra = "4" > - xm create -c test.conf > - everything in domU is fine except that eth0 is not seen: > ifconfig eth0 > eth0: error fetching interface information: Device not found > - "ifconfig -a" shows lo and sit0 only > - on dom0: > brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no peth0 > vif0.0 > vif1.0 > - domU image contains valid ifcfg-eth0 configuration file > I tried to add network configuration into the domU configuration file: > ip="10.10.10.10" > netmask="255.255.255.0" > gateway="10.10.10.1" > broadcast="10.10.10.255" > and got the same results. > - I tried with and without a ramdisk image in the domU conf file (getting > desperate here) > - no errors in domU dmesg or with "xen dmesg" on dom0 > > I really don''t know where to go from here. I made several attempts with > variations in config files but always got the same problem. Am I missing > something obvious? Any suggestion as to what tools I can use to troubleshoot? > Any help would be greatly appreciated. > > Thanks a lot > > Denis > > _______________________________________________ > 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
It works!!! Adding the line in modprobe.conf made everything work. Thank you so much. Now I can really start working... Denis> I have also had this problem with the FC5 domU kernel. It turns out > they decided to make the xennet kernel driver a module instead of > compiled in. All you need to do is in the "/etc/modprobe.conf" file of > your guest, make sure it has the following line: > > alias eth0 xennet > > This means the kernel will load the xennet module for eth0. > > Thanks, > Phil Evans. > > Denis Lebeuf wrote: > > Hello, > > > > I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface > > appear in domU. I read nearly everything in this list that could look > > similar to my problem but to no avail. > > > > I have 3 servers running FC3 and Xen 2 with various domUs since a year. > > Everything is fine on that front. > > > > I took one of the server, upgraded it to FC5 and did the following: > > > > - yum install xen kernel-xen0 kernel-xenU > > - grub.conf contains > > title Fedora Core (2.6.15-1.2054_FC5xen0 > > root (hd0,0) > > kernel /boot/xen.gz-2.6.15-1.2054_FC5 > > module /boot/vmlinuz-2.6.15-1.2054_FC5xen0 root=LABEL=/ ro console=tty0 > > noscsi > > module /boot/initrd-2.6.15-1.2054_FC5xen0.img > > - rebooted with the xen0 kernel > > - kept the default xend-config.sxp to use bridging > > - started xend > > - copied a domU FC3 image from another server (tried also with a trustix > > image) > > - mounted the FC3 image in loop fs and copied (cp > > -a) /lib/modules/2.6.15-1.2054_FC5xenU to it > > - created a domU configuration file: > > kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img" > > memory = 128 > > name = "test" > > vif = [ '''' ] > > disk = [ ''file:/images/fc3,sda1,w'' ] > > root = "/dev/sda1 ro" > > extra = "4" > > - xm create -c test.conf > > - everything in domU is fine except that eth0 is not seen: > > ifconfig eth0 > > eth0: error fetching interface information: Device not found > > - "ifconfig -a" shows lo and sit0 only > > - on dom0: > > brctl show > > bridge name bridge id STP enabled > > interfaces xenbr0 8000.feffffffffff no > > peth0 vif0.0 vif1.0 - domU image contains valid > > ifcfg-eth0 configuration file > > I tried to add network configuration into the domU configuration file: > > ip="10.10.10.10" > > netmask="255.255.255.0" > > gateway="10.10.10.1" > > broadcast="10.10.10.255" > > and got the same results. > > - I tried with and without a ramdisk image in the domU conf file (getting > > desperate here) > > - no errors in domU dmesg or with "xen dmesg" on dom0 > > > > I really don''t know where to go from here. I made several attempts with > > variations in config files but always got the same problem. Am I missing > > something obvious? Any suggestion as to what tools I can use to > > troubleshoot? Any help would be greatly appreciated. > > > > Thanks a lot > > > > Denis > > > > _______________________________________________ > > 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_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Mar 25, 2006 at 12:10:04PM -0500, cqfd wrote:> I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear in domU.> kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img"Fedora drops the file /boot/vmlinuz-2.6.15-1.2054_FC5xenU here, but maybe you renamed the file.> - everything in domU is fine except that eth0 is not seen: > ifconfig eth0 > eth0: error fetching interface information: Device not foundTried to load module xennet? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you! Thank you! Thank you! I have the exact same problem on FC5 (didn''t have this on FC4). I''ve been searching for a solution for the past 1.5 days. In FC4 it was automatic so I didn''t expect to have to load the module manually. Loading xennet enables the interface. It''s aliiiive!! On 4/5/06, Christian Horn <chorn@fluxcoil.net> wrote:> On Sat, Mar 25, 2006 at 12:10:04PM -0500, cqfd wrote: > > I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear in domU. > > > kernel = "/boot/vmlinuz-2.6.15-1.2054_FC5xenU.img" > Fedora drops the file /boot/vmlinuz-2.6.15-1.2054_FC5xenU here, but maybe > you renamed the file. > > > - everything in domU is fine except that eth0 is not seen: > > ifconfig eth0 > > eth0: error fetching interface information: Device not found > Tried to load module xennet? > > > _______________________________________________ > 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