Hi my dom0 runs openSuSE 10.2. Creating several domUs worked fine when using image files. Now I am trying to install an openSuSE 10.2 System on an NFS root. What I did so far is: Make a dirinstall of openSuSE 10.2 to /mnt/dirinstall Mount the NFS root to /nfs Move anything from /mnt/dirinstall to /nfs Umount the NFS root Here''s my domU config file: kernel = ''/boot/vmlinuz-xen'' ramdisk = ''/boot/initrd-xen'' root = ''/dev/nfs'' nfs_server = ''10.2.50.21'' nfs_root = ''/xenvm1'' memory = 512 vcpus = 1 builder = ''linux'' name = ''x-dktest'' vif = [ ''bridge=xenbr0, ip=10.2.50.41'' ] localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = '' TERM=xterm'' /etc/exports on NFS (v3) Server looks like this: /xenvm1 10.2.50.0/255.255.255.0(rw,sync,no_root_squash,no_all_squash) In dom0 (10.2.50.31) I can mount the NFS share with no problem. If I start the domU and connect to it with xm console, I get this: .... NET: Registered protocol family 1 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 184k freed Time: xen clocksource has been installed. Boot logging started on /dev/tty1(/dev/console) at Thu Mar 8 11:38:55 2007 Creating device nodes with udev netfront: Initialising virtual ethernet driver. Loading xennet netfront: device eth0 has flipping receive path. Loading xenblk Loading jbd Loading mbcache Loading ext3 Mounting root 10.2.50.21:/xenvm1 mount server reported tcp not available, falling back to udp mount: RPC: Remote system error - Network is unreachable umount: /dev: device is busy umount: /dev: device is busy umount: /dev/pts: device is busy umount: /dev/pts: device is busy Kernel panic - not syncing: Attempted to kill init! In the archives I found a mail saying to put hostnames for domU, dom0 and NFS Server on all machines. But that did not make a difference. If there''s a howto out there on how to do this, I did not find it yet. I''d be glad if someone could help me out here. Thanks in advance, Dominik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> root = ''/dev/nfs'' > nfs_server = ''10.2.50.21'' > nfs_root = ''/xenvm1''Am I right that my kernel needs CONFIG_ROOT_NFS in order for this to work?> memory = 512 > vcpus = 1 > builder = ''linux'' > name = ''x-dktest'' > vif = [ ''bridge=xenbr0, ip=10.2.50.41'' ]Am I right that my kernel needs CONFIG_IP_PNP in order for this to work? This may be a reason, as the standard openSuSE kernel does not set those options and does not even build them as modules. Regards Dominik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>>> root = ''/dev/nfs'' >>> nfs_server = ''10.2.50.21'' >>> nfs_root = ''/xenvm1'' >> Am I right that my kernel needs CONFIG_ROOT_NFS in order for >> this to work? > > I should think this is necessary. >>> memory = 512 >>> vcpus = 1 >>> builder = ''linux'' >>> name = ''x-dktest'' >>> vif = [ ''bridge=xenbr0, ip=10.2.50.41'' ] >> Am I right that my kernel needs CONFIG_IP_PNP in order for >> this to work? > > Not quite sure about the necessity of this, but possibly.So my new kernel has these options but domU still says the exact same thing (yes, I did copy the new modules into the lib dir on the nfs root). Any ideas? Regards Dominik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Dominik Klein > Sent: 08 March 2007 13:53 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Installing a domU on NFS > > >>> root = ''/dev/nfs'' > >>> nfs_server = ''10.2.50.21'' > >>> nfs_root = ''/xenvm1'' > >> Am I right that my kernel needs CONFIG_ROOT_NFS in order for > >> this to work? > > > > I should think this is necessary. > >>> memory = 512 > >>> vcpus = 1 > >>> builder = ''linux'' > >>> name = ''x-dktest'' > >>> vif = [ ''bridge=xenbr0, ip=10.2.50.41'' ] > >> Am I right that my kernel needs CONFIG_IP_PNP in order for > >> this to work? > > > > Not quite sure about the necessity of this, but possibly. > > So my new kernel has these options but domU still says the exact same > thing (yes, I did copy the new modules into the lib dir on > the nfs root).You probably need those modules in the initrd, because until you have connection to your NFS volume, you can''t really use any of it''s content, so you have a "chicken and egg problem" - which is solved by either compiling them in as built-in''s to the kernel, or by using an initrd that contains the necessary modules to get past the initial boot point. -- Mats> > Any ideas? > > Regards > Dominik > > _______________________________________________ > 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
> You probably need those modules in the initrd, because until you have > connection to your NFS volume, you can''t really use any of it''s content, > so you have a "chicken and egg problem" - which is solved by either > compiling them in as built-in''s to the kernel, or by using an initrd > that contains the necessary modules to get past the initial boot point.ROOT_NFS is compilable as a module, IP_PNP is not. I''ll give it a try and report here. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dominik Klein schrieb:>> You probably need those modules in the initrd, because until you have >> connection to your NFS volume, you can''t really use any of it''s content, >> so you have a "chicken and egg problem" - which is solved by either >> compiling them in as built-in''s to the kernel, or by using an initrd >> that contains the necessary modules to get past the initial boot point. > > ROOT_NFS is compilable as a module, IP_PNP is not. I''ll give it a try > and report here.Well this seems wrong information. Both is not compilable as a module in my kernel version 2.6.18 Besides, from what I understood, the kernel that is started initially is the one from /boot in dom0 - isnt it? Any more ideas? Regards Dominik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Dominik Klein > Sent: 08 March 2007 15:42 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Installing a domU on NFS > > Dominik Klein schrieb: > >> You probably need those modules in the initrd, because > until you have > >> connection to your NFS volume, you can''t really use any of > it''s content, > >> so you have a "chicken and egg problem" - which is solved by either > >> compiling them in as built-in''s to the kernel, or by using > an initrd > >> that contains the necessary modules to get past the > initial boot point. > > > > ROOT_NFS is compilable as a module, IP_PNP is not. I''ll > give it a try > > and report here. > > Well this seems wrong information. Both is not compilable as > a module in > my kernel version 2.6.18So, you''re saying that the ROOT_NFS option doesn''t produce a module, nor does IP_PNP? In that case, you shouldn''t need to modify your initrd.> > Besides, from what I understood, the kernel that is started > initially is > the one from /boot in dom0 - isnt it?Yes, that''s correct. [Or, rather, that''s ONE place you could take it from, it all depends on your configuration file]. But you previously posted the configuration file, and that points to /boot/vmlinuz-xen, so that''s the kernel used. -- Mats> > Any more ideas? > > Regards > Dominik > > _______________________________________________ > 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 Thu, Mar 08, 2007 at 04:42:17PM +0100, Dominik Klein wrote:> Well this seems wrong information. Both is not compilable as a module in > my kernel version 2.6.18Yes, you will need to enable it since it isn''t enabled by default.> Besides, from what I understood, the kernel that is started initially is > the one from /boot in dom0 - isnt it?Yes - and it is that kernel which needs it enabled in. By default the Xen kernel which is installed by "make world && make install" doesn''t have NFS_ROOT setup. Neither do many of the kernels packaged by distributions. (eg. Debian Etch has a range of Xen kernels but none of them have NFS_ROOT compiled in). By happy coincidence I wrote a guide on getting NFS_ROOT working on a Debian machine yesterday evening and it just got published: http://www.debian-administration.org/articles/505 In short: 1. Get the Xen source, so you can rebuild a xen kernel and install it to /boot 2. Setup NFS server. 3. Create Xen configuration file beneath /etc/xen No need to use an initrd image in the common cases, unless you need funky hardware support. Just compile NFS into the kernel rather than as a module and you''ll be fine. Hope that helps a little. Steve -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Kernel panic - not syncing: Attempted to kill init! > > In the archives I found a mail saying to put hostnames for domU, dom0 > and NFS Server on all machines. But that did not make a difference. > > If there''s a howto out there on how to do this, I did not find it yet.This has definitely come up before. Every time I''ve seen someone suggest a fix for this, it involves making certain that the domU kernel has NFSROOT support in the kernel, either compiled in or through initrd. (never could make this work myself). Joe. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> By default the Xen kernel which is installed by "make world && make > install" doesn''t have NFS_ROOT setup. Neither do many of the kernels > packaged by distributions. (eg. Debian Etch has a range of Xen kernels > but none of them have NFS_ROOT compiled in). > > By happy coincidence I wrote a guide on getting NFS_ROOT working > on a Debian machine yesterday evening and it just got published: > > http://www.debian-administration.org/articles/505So I think I have got everything I need, but it still does not work. /mnt/etc # cat fstab 10.2.50.21:/xenvm1 / nfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /proc sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /etc/xen/vm # cat x-dktest kernel = ''/boot/vmlinuz-2.6.18.2dk2-34-xen'' ramdisk = ''/boot/initrd-2.6.18.2dk2-34-xen'' vif = [ ''bridge=xenbr0, ip=10.2.50.41'' ] dhcp = ''off'' netmask = ''255.255.255.0'' gateway = ''10.2.50.10'' ip = ''10.2.50.41'' hostname = ''x-dktest'' root = ''/dev/nfs'' nfs_server = ''10.2.50.21'' nfs_root = ''/xenvm1'' memory = 512 vcpus = 1 builder = ''linux'' name = ''x-dktest'' localtime = 0 on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' extra = '' TERM=xterm'' /etc/xen/vm # uname -a Linux ACD-xen01 2.6.18.2dk2-34-xen #3 SMP Thu Mar 8 16:44:33 CET 2007 i686 i686 i386 GNU/Linux /etc/xen/vm # zgrep ROOT_NFS /proc/config.gz CONFIG_ROOT_NFS=y /etc/xen/vm # zgrep IP_PNP /proc/config.gz CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y /etc/xen/vm # ls /mnt/lib/modules/ 2.6.18.2-34-default 2.6.18.2-34-xen 2.6.18.2dk2-34-xen 2.6.18.2dk-34-xen Error Message is this: NET: Registered protocol family 1 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vif/0 Time: xen clocksource has been installed. IP-Config: Device `eth0'' not found. Freeing unused kernel memory: 200k freed Boot logging started on /dev/tty1(/dev/console) at Mon Mar 12 07:26:10 2007 Creating device nodes with udev netfront: Initialising virtual ethernet driver. Loading xennet netfront: device eth0 has flipping receive path. Loading xenblk Loading jbd Loading mbcache Loading ext3 Mounting root 10.2.50.21:/xenvm1 mount server reported tcp not available, falling back to udp mount: RPC: Remote system error - Network is unreachable umount: /dev: device is busy umount: /dev: device is busy umount: /dev/pts: device is busy umount: /dev/pts: device is busy Kernel panic - not syncing: Attempted to kill init! What I''m curious about is the line "IP-Config: Device `eth0'' not found." which seems to be a problem. But it is actually attached to the correct bridge. See here (this is after booting the vm while it hangs with kernel panic): /etc/xen/vm # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 511 4 r----- 1519.3 x-dktest 9 512 1 r----- 102.6 /etc/xen/vm # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.000423c0b340 no vif0.0 bond0 vif9.0 /etc/xen/vm # xm network-list 9 Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path 0 0 00:16:3e:4c:38:23 0 4 6 520 /521 /local/domain/0/backend/vif/9/0 Any ideas appreciated. Thanks in advance, Dominik _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Maybe this is interesting from /var/log/xen/xend.log ? [2007-03-12 08:26:04 xend 4131] DEBUG (DevController:143) Waiting for devices vif. [2007-03-12 08:26:04 xend 4131] DEBUG (DevController:149) Waiting for 0. [2007-03-12 08:26:04 xend 4131] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2007-03-12 08:26:04 xend 4131] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vif/9/0/hotplug-status. [2007-03-12 08:26:04 xend 4131] DEBUG (DevController:478) hotplugStatusCallback 1. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I could solve this by compiling "xennet" directly into the kernel. As a module, it would not find eth0 inside domU. This is done by setting CONFIG_XEN_NETDEV_FRONTEND=y Regards Dominik Dominik Klein schrieb:>> By default the Xen kernel which is installed by "make world && make >> install" doesn''t have NFS_ROOT setup. Neither do many of the kernels >> packaged by distributions. (eg. Debian Etch has a range of Xen kernels >> but none of them have NFS_ROOT compiled in). >> >> By happy coincidence I wrote a guide on getting NFS_ROOT working >> on a Debian machine yesterday evening and it just got published: >> >> http://www.debian-administration.org/articles/505 > > So I think I have got everything I need, but it still does not work. > > /mnt/etc # cat fstab > 10.2.50.21:/xenvm1 / nfs defaults 0 0 > proc /proc proc defaults 0 0 > sysfs /proc sysfs noauto 0 0 > usbfs /proc/bus/usb usbfs noauto 0 0 > devpts /dev/pts devpts mode=0620,gid=5 0 0 > > /etc/xen/vm # cat x-dktest > kernel = ''/boot/vmlinuz-2.6.18.2dk2-34-xen'' > ramdisk = ''/boot/initrd-2.6.18.2dk2-34-xen'' > vif = [ ''bridge=xenbr0, ip=10.2.50.41'' ] > dhcp = ''off'' > netmask = ''255.255.255.0'' > gateway = ''10.2.50.10'' > ip = ''10.2.50.41'' > hostname = ''x-dktest'' > root = ''/dev/nfs'' > nfs_server = ''10.2.50.21'' > nfs_root = ''/xenvm1'' > memory = 512 > vcpus = 1 > builder = ''linux'' > name = ''x-dktest'' > localtime = 0 > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart'' > extra = '' TERM=xterm'' > > /etc/xen/vm # uname -a > Linux ACD-xen01 2.6.18.2dk2-34-xen #3 SMP Thu Mar 8 16:44:33 CET 2007 > i686 i686 i386 GNU/Linux > > /etc/xen/vm # zgrep ROOT_NFS /proc/config.gz > CONFIG_ROOT_NFS=y > > /etc/xen/vm # zgrep IP_PNP /proc/config.gz > CONFIG_IP_PNP=y > CONFIG_IP_PNP_DHCP=y > CONFIG_IP_PNP_BOOTP=y > CONFIG_IP_PNP_RARP=y > > /etc/xen/vm # ls /mnt/lib/modules/ > 2.6.18.2-34-default 2.6.18.2-34-xen 2.6.18.2dk2-34-xen 2.6.18.2dk-34-xen > > Error Message is this: > NET: Registered protocol family 1 > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vif/0 > Time: xen clocksource has been installed. > IP-Config: Device `eth0'' not found. > Freeing unused kernel memory: 200k freed > Boot logging started on /dev/tty1(/dev/console) at Mon Mar 12 07:26:10 2007 > Creating device nodes with udev > netfront: Initialising virtual ethernet driver. > Loading xennet > netfront: device eth0 has flipping receive path. > Loading xenblk > Loading jbd > Loading mbcache > Loading ext3 > Mounting root 10.2.50.21:/xenvm1 > mount server reported tcp not available, falling back to udp > mount: RPC: Remote system error - Network is unreachable > umount: /dev: device is busy > umount: /dev: device is busy > umount: /dev/pts: device is busy > umount: /dev/pts: device is busy > Kernel panic - not syncing: Attempted to kill init! > > What I''m curious about is the line "IP-Config: Device `eth0'' not found." > which seems to be a problem. But it is actually attached to the correct > bridge. See here (this is after booting the vm while it hangs with > kernel panic): > > /etc/xen/vm # xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 511 4 r----- 1519.3 > x-dktest 9 512 1 r----- 102.6 > > > /etc/xen/vm # brctl show > bridge name bridge id STP enabled interfaces > xenbr0 8000.000423c0b340 no vif0.0 > bond0 > vif9.0 > > /etc/xen/vm # xm network-list 9 > Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path > 0 0 00:16:3e:4c:38:23 0 4 6 520 /521 > /local/domain/0/backend/vif/9/0 > > Any ideas appreciated. > > Thanks in advance, > Dominik_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Mar-12 12:33 UTC
RE: [solved] Re: [Xen-users] Installing a domU on NFS
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Dominik Klein > Sent: 12 March 2007 12:20 > To: xen-users@lists.xensource.com > Subject: [solved] Re: [Xen-users] Installing a domU on NFS > > I could solve this by compiling "xennet" directly into the > kernel. As a > module, it would not find eth0 inside domU. > > This is done by setting > CONFIG_XEN_NETDEV_FRONTEND=yGlad you managed to solve it! That sounds like a good solution, but adding it manually to the initrd image would also have worked, I bet. Since you DO NEED this module all the time, it''s not bad to have it in the kernel as a built-in, but I''m just mentioning the initrd solution for completeness. -- Mats> > Regards > Dominik > > Dominik Klein schrieb: > >> By default the Xen kernel which is installed by "make > world && make > >> install" doesn''t have NFS_ROOT setup. Neither do many of > the kernels > >> packaged by distributions. (eg. Debian Etch has a range > of Xen kernels > >> but none of them have NFS_ROOT compiled in). > >> > >> By happy coincidence I wrote a guide on getting NFS_ROOT working > >> on a Debian machine yesterday evening and it just got published: > >> > >> http://www.debian-administration.org/articles/505 > > > > So I think I have got everything I need, but it still does not work. > > > > /mnt/etc # cat fstab > > 10.2.50.21:/xenvm1 / nfs defaults 0 0 > > proc /proc proc defaults 0 0 > > sysfs /proc sysfs noauto 0 0 > > usbfs /proc/bus/usb usbfs noauto 0 0 > > devpts /dev/pts devpts mode=0620,gid=5 0 0 > > > > /etc/xen/vm # cat x-dktest > > kernel = ''/boot/vmlinuz-2.6.18.2dk2-34-xen'' > > ramdisk = ''/boot/initrd-2.6.18.2dk2-34-xen'' > > vif = [ ''bridge=xenbr0, ip=10.2.50.41'' ] > > dhcp = ''off'' > > netmask = ''255.255.255.0'' > > gateway = ''10.2.50.10'' > > ip = ''10.2.50.41'' > > hostname = ''x-dktest'' > > root = ''/dev/nfs'' > > nfs_server = ''10.2.50.21'' > > nfs_root = ''/xenvm1'' > > memory = 512 > > vcpus = 1 > > builder = ''linux'' > > name = ''x-dktest'' > > localtime = 0 > > on_poweroff = ''destroy'' > > on_reboot = ''restart'' > > on_crash = ''restart'' > > extra = '' TERM=xterm'' > > > > /etc/xen/vm # uname -a > > Linux ACD-xen01 2.6.18.2dk2-34-xen #3 SMP Thu Mar 8 > 16:44:33 CET 2007 > > i686 i686 i386 GNU/Linux > > > > /etc/xen/vm # zgrep ROOT_NFS /proc/config.gz > > CONFIG_ROOT_NFS=y > > > > /etc/xen/vm # zgrep IP_PNP /proc/config.gz > > CONFIG_IP_PNP=y > > CONFIG_IP_PNP_DHCP=y > > CONFIG_IP_PNP_BOOTP=y > > CONFIG_IP_PNP_RARP=y > > > > /etc/xen/vm # ls /mnt/lib/modules/ > > 2.6.18.2-34-default 2.6.18.2-34-xen 2.6.18.2dk2-34-xen > 2.6.18.2dk-34-xen > > > > Error Message is this: > > NET: Registered protocol family 1 > > Using IPI No-Shortcut mode > > XENBUS: Device with no driver: device/vif/0 > > Time: xen clocksource has been installed. > > IP-Config: Device `eth0'' not found. > > Freeing unused kernel memory: 200k freed > > Boot logging started on /dev/tty1(/dev/console) at Mon Mar > 12 07:26:10 2007 > > Creating device nodes with udev > > netfront: Initialising virtual ethernet driver. > > Loading xennet > > netfront: device eth0 has flipping receive path. > > Loading xenblk > > Loading jbd > > Loading mbcache > > Loading ext3 > > Mounting root 10.2.50.21:/xenvm1 > > mount server reported tcp not available, falling back to udp > > mount: RPC: Remote system error - Network is unreachable > > umount: /dev: device is busy > > umount: /dev: device is busy > > umount: /dev/pts: device is busy > > umount: /dev/pts: device is busy > > Kernel panic - not syncing: Attempted to kill init! > > > > What I''m curious about is the line "IP-Config: Device > `eth0'' not found." > > which seems to be a problem. But it is actually attached to > the correct > > bridge. See here (this is after booting the vm while it hangs with > > kernel panic): > > > > /etc/xen/vm # xm list > > Name ID Mem(MiB) VCPUs > State Time(s) > > Domain-0 0 511 4 > r----- 1519.3 > > x-dktest 9 512 1 > r----- 102.6 > > > > > > /etc/xen/vm # brctl show > > bridge name bridge id STP enabled interfaces > > xenbr0 8000.000423c0b340 no vif0.0 > > bond0 > > vif9.0 > > > > /etc/xen/vm # xm network-list 9 > > Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path > > 0 0 00:16:3e:4c:38:23 0 4 6 520 /521 > > /local/domain/0/backend/vif/9/0 > > > > Any ideas appreciated. > > > > Thanks in advance, > > Dominik > > > > _______________________________________________ > 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
> That sounds like a good solution, but adding it manually to the initrd > image would also have worked, I bet.xennet was in my initrd. I could even see it load, but that was AFTER IP-Config complained about not finding eth0 (see below in the boot message I supplied earlier).>>> IP-Config: Device `eth0'' not found. >>> Freeing unused kernel memory: 200k freed >>> Boot logging started on /dev/tty1(/dev/console) at Mon Mar >> 12 07:26:10 2007 >>> Creating device nodes with udev >>> netfront: Initialising virtual ethernet driver. >>> Loading xennet >>> netfront: device eth0 has flipping receive path. >>> Loading xenblk >>> Loading jbd >>> Loading mbcache >>> Loading ext3 >>> Mounting root 10.2.50.21:/xenvm1 >>> mount server reported tcp not available, falling back to udp >>> mount: RPC: Remote system error - Network is unreachable >>> umount: /dev: device is busy >>> umount: /dev: device is busy >>> umount: /dev/pts: device is busy >>> umount: /dev/pts: device is busy >>> Kernel panic - not syncing: Attempted to kill init!_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Kraska, Joe A \(US SSA\)
2007-Mar-12 20:55 UTC
RE: [solved] Re: [Xen-users] Installing a domU on NFS
> I could solve this by compiling "xennet" directly into the kernel. Asa> module, it would not find eth0 inside domU. > > This is done by setting > CONFIG_XEN_NETDEV_FRONTEND=yThanks for that. I was looking for this. Dumb question: how does one know what the kernel config tags will be when they''re not actually in the config file already as a choice (n,y,m)? Joe. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Dumb question: how does one know what the kernel config tags will be > when they''re not actually in the config file already as a choice > (n,y,m)?Take a look at /proc/config.gz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users