[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Cannot have eth0 in domU
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@xxxxxxxxxxxxxxxxxxx > > http://lists.xensource.com/xen-users > > _______________________________________________ > 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |