similar to: pxelinux.cfg/default config issues

"H. Peter Anvin" wrote: > > Manuel Tuthill wrote: > >>"Something like"?! What does it actually *say*? > > > > > > Sorry for the confusion but the entire config file reas as > > > > ******** > > default std > > > > label std > > kernel linuz > > append root=/dev/nfs

Hi, I know this isn't the right list for this but I figured that at least you guy's have done some similar things. After messing about with PXElinux, I'm only a hairs breath away from finishing. My problem comes from program files that the Kernel boots to, so init=/sbin/init or init=/bin/bash. If I boot to bash the console of the remote PC just dies right after the section

Hello all, I understand that during PXE boot, it goes into the pxelinux.cfg and it states: 1. "it will search for the config file using its own IP address in upper case hexadecimal, e.g. 192.0.2.91 -> C000025B (you can use the included progam "gethostip" to compute the hexadecimal IP address for any host.) If that file is not found, it will remove one hex digit and try

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

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

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

Greetings. I have seen some postings asking if pxelinux can support the network booting of the virtual machine kernel known as Xen but i cannot find any positive answers. As has been reported pxegrub combined with nfsroot can be used, but for me nfsroot is an inconvenience. Has anyone been able to use pxelinux to boot a Xen kernel? Many Thanks Mike

Hi, I am trying to boot the PXEclient via pxeserver and I am getting an error "file not found", following are me setup in the /tftpboot: /tftpboot: initrd.img linuz pxelinux.0 /tftpboot/pxelinux.cfg default (lower case) in the default file: # This is the default pxelinux config file. LABEL test KERNEL vmlinuz APPEND

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

Hi I am trying to set up a thin client. I have managed to set up DHCP and TFTP on a Fedora Core 6 server but the problem is when PXELinux on the client tries to load the configuration file. I get the message: Trying to load: pxelinux.cfg/01-00-0c-29-ca-7a-ce Trying to load: pxelinux.cfg/0A000014 etc.. Trying to load: pxelinux.cfg/default Unable to locate configuration file If I use a TFTP

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'm trying to boot RedHat 9.0 on a diskless PC from a head machine running Redhat 9.0. The network appears to be setup correctly. I can boot the installation disk image fine using pxelinux. What I am trying to setup is a number of different Linux systems each with its own root directory on the head machine. I am hoping that I don't have to modify the kernel for any of these systems.

the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs

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:

any comments? if nothing else, is there any way to atomically setup bridge? not on list, please cc. ---------- Forwarded message ---------- Date: Wed, 12 Jan 2005 21:08:15 -0000 From: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> To: Adam Sulmicki <adam@cfar.umd.edu>, xen-devel@lists.sourceforge.net Subject: RE: [Xen-devel] nfsroot and brige > hello, > it seems like a catch-22 to

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 \

Hello all, I would like to seek advise on the following; I have configured linux NFSroot images for a bunch of servers and am able to boot and run stuff happily; one nuance that bothers me is that, for instance, my Fedora6 (x64) (kernel 2.6.22), (and noticed also in some other distros - Fedora8, Ubuntu710), the client boots but DOES NOT seem to pick up the hostname I pass it through the DCHP

I have several machines, same hardware and config, but one tiny little change.. the hostname. Each one of these diskless machines needs its own hostname. Presently my pxelinux.cfg is setup like: prompt 1 default Gentoo timeout 10 label Gentoo kernel boot/kernel-3.16.5-gentoo APPEND root=/dev/nfs rw ip=dhcp nfsroot=192.168.1.10:/RAID/diskless/XXXXX-mythtv-0.27-fixes,tcp,rsize=131072

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