similar to: [Bridge] RE: [Xen-devel] nfsroot and brige (fwd)

Hi everyone, I got the error: NET4: Unix domain sockets 1.0/smp for linux NET4.0 ds: no socket drivers loaded request_module[block-major-8]: root fs not mounted VFS: Cannot open root device ""or 08:03 Please append a correct "root"boot option The strange thing is that it tries to mount from harddisk. This I got somewhere else: "the kernel looks like it is trying to

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

Changes in xen/arch/x86/domain.c in 2.0.2 break comiple for me with: ld --oformat elf32-i386 -T x86_32/xen.lds -N \ boot/x86_32.o /home/root/xen-2.0/xen/common/common.o /home/root/xen-2.0/xen/drivers/char/driver.o /home/root/xen-2.0/xen/drivers/acpi/driver.o /home/root/xen-2.0/xen/drivers/pci/driver.o /home/root/xen-2.0/xen/arch/x86/arch.o -o /home/root/xen-2.0/xen/xen-syms

Does anyone have any good how-to's or documentation on setting up read only root NFS for pxe booting diskless computers? A few months ago I stumbled upon an official Redhat doc through a google search(not hosted by redhat and I cannot find it anywhere on the Redhat site) written by Dave Kline named "Configuring diskless clients with Red Hat Enterprise Linux" from 2011. It seemed to

Hi, I've got a task to have a small number of laptops netboot Linux over WiFi. The kernel is loaded off the USB stick of cource, it's off topic for now. The WPA-supplicant daemon is started early by dracut off initrd. It works. Mostly. The problem is that upon shutdown systemd terminates all the processes FIRST and unmounts filesystems NEXT. Guess what? Upon termination,

Hello all, I have observed a problem with a diskless PXE client I am attempting to configure. PXE/NFS/DHCP/TFTPd server is running CentOS5.1 and the Diskless workstation's root and kernel was extracted from a CentOS5.1 (custom kernel due to setting to enable Root File System support). Problem: When the diskless client boots and logs in I notice that my root user is being squashed, even if I

in Documentation/nfsroot.txt, it says: 1.) Enabling nfsroot capabilities ----------------------------- In order to use nfsroot you have to select support for NFS during kernel configuration. Note that NFS cannot be loaded as a module in this case. The configuration script will then ask you whether you want to use nfsroot, and if yes what kind of auto configuration system you want to use.

I made a diskless node centos. the pxelinux.cfg/default file : default centos label centos kernel vmlinuz-2.6.18-194.el5 append initrd=initrd-2.6.18-194.el5.nfs.img nfsroot=10.10.10.1:/srv/centos ip=dhcp rw I can successfull*y boot-strap the system with no error.* *But when i shutdown or reboot it . It will show in the screen :* *Unmounting NFS filesystems* *INIT:no more process

kinit/nfsmount.c:mount_nfs_root() should use the bootpath specified by bootp/dhcp. If the "nfsroot" option is specified then it overrides the boot server bootpath and a message indicating the override is printed. --- klibc-0.194/kinit/nfsroot.c.orig 2005-01-05 04:13:47.043897880 -0700 +++ klibc-0.194/kinit/nfsroot.c 2005-01-05 04:13:09.316633296 -0700 @@ -66,34 +66,21 @@ const int

The in-kernel nfsroot code is obsoleted by kinit. Remove it; it causes conflicts. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 161e1dc16ec1129b30b634a2a8dcbbd1937800c5 tree c30da837d746fe65d8a13ccf6f27bd381948edb4 parent 018604e070e143657abcf0cb256a1e2dda205d97 author H. Peter Anvin <hpa at zytor.com> Sat, 20 May 2006 16:24:05 -0700 committer H. Peter Anvin <hpa at

coding style fixes. FIXME: check that compiled bin the same1!! --- usr/kinit/initrd.c | 3 ++- usr/kinit/kinit.c | 12 ++++-------- usr/kinit/kinit.h | 20 ++++++++++---------- usr/kinit/name_to_dev.c | 6 +++--- usr/kinit/nfsroot.c | 5 ++--- 5 files changed, 21 insertions(+), 25 deletions(-) diff --git a/usr/kinit/initrd.c b/usr/kinit/initrd.c index

I seem to be having trouble getting the NFS root filesystem to mount after the kernel boots. As per thread from 2002 16 January (http://www.zytor.com/pipermail/syslinux/2002-January/000028.html), I double checked my DHCP config files, but to no avail. It cannot seem to attach to the mountd port on the bootserver. Here is some output from the kernel: loop: loaded (max 8 devices) Intel(R) PRO/1000

I just checked in changes to kinit, such that it is now a single 29KB executable that replaces the kernel's ipconfig and nfsroot code. The kinit code isn't very elegant, but I figured it was better to save space than to fully generalise it so that it could be extended in a sort of modular fashion. If someone wants modularity, I figure they can spend the few extra KB and run the

> Hi, > > I've got a task to have a small number of laptops netboot Linux over > WiFi. The kernel is loaded off the USB stick of cource, it's off topic > for now. > > The WPA-supplicant daemon is started early by dracut off initrd. It > works. Mostly. > > The problem is that upon shutdown systemd terminates all the processes > FIRST and unmounts filesystems

hi, i trying to install a fai installation server in a DomU for DomUs, but i have some problems with nfs. The DomUs says, that they can''t reach the NFS Server =========== Begin: Retrying nfs mount ... IP-Config: eth0 hardware address 00:16:3e:7a:25:7c mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.16.0.255 IP-Config: eth0 complete (from 172.16.0.151): address:

Hi, I'm trying to deploy some non-linux OS via pxe and I was thinking to just launch CentOS in RAM and then run dd or qemu-img or something like this in order to complete the other OS install via template imaging. My first idea was to build a custom CentOS livecd and use that in combination with pxe kernel parameters, but perhaps there's a better way to do this. Ideas? Thanks, Lucian --

Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my

Hello, I have the following problem. I am trying to pxeboot a virtual machine using Sun's Virtualbox. I am trying to experiment with the menu options of pxelinux and this is my pxelinux.cfg/default file. # generated by fai-chboot for host cdbexample with IP 172.16.31.200 default menu.c32 prompt 0 default fai-generated timeout 300 #ONTIMEOUT local MENU TITLE PXE Menu LABEL fai-generated

Hi, I've got another one... NFS error 101 with NFSROOT has been discussed a lot, and hpa gave an answer to it which appears right. It's ENETUNREACH, and I suspect my diskless box does not set its IP parameters right. PXElinux is set up as follows: label linvdr kernel kernel-linvdr append initrd=initrd-linvdr acpi=off root=/dev/nfs \