similar to: where is kernel and initrd?

I?ve got a 512M machine and a 330M ( uncompressed ) initrd image. How can I mount the ramdisk? Normal booting seems to want to copy the entire initrd image into a Ramdisk, thus requiring 2X the memory. So what happens is the kernel boots correctly and I get, RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 330000 blocks [ 1 disk ] into ram disk And then I never see the light of day after

I?ve got a 512M machine and a 330M ( uncompressed ) initrd image. How can I mount the ramdisk? Normal booting seems to want to copy the entire initrd image into a Ramdisk, thus requiring 2X the memory. So what happens is the kernel boots correctly and I get, RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 330000 blocks [ 1 disk ] into ram disk And then I never see the light of day after

Hi all If I use nfsroot boot the xen dom0, I find it works well if not use initrd-2.6.32.9.img. what does "initrd-2.6.32.9.img" contains? Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello all Now I may be way of whack here, so please forgive me. I''m trying to merge xen with redhat''s config-netboot. The idea being a kinda stateless domU. For those that haven''t seen you share a rootfs and then bind mount all the individual files over then top, and the redhat gui builds all the pxeboot config and stuff for you if you want a diskless client. I

Can someone point me to instructions on how to build a pxeboot/initrd.img with updated drivers. I would like to pxe boot and install rh8 on a newer machine, and the pxeboot files that come with rh8 (2.4.20-8) don't support my e1000 NIC. I believe that the newer 2.4.20-28.8 drivers will, but I'm having trouble finding instructions in rebuilding the pxeboot initrd.img + vmlinuz to

Hi, I have a user that is experiencing problems pxe booting several identical servers. pxelinux.0 is from syslinux 3.63 and the TFTP server is 0.42 running on CentOS 5.2. After loading pxelinux.0, the client will then start transferring vmlinuz and initrd.img via tftp. More than half the time, the transfer will get stuck and then eventually print a timeout message. I ran tcpdump and I can see

I tried to convert / to ext3, so I went ahead and entered rootflags=noload,journal=355 on the LILO prompt. The kernel failed to mount /: EXT3-fs error (device ramdisk(1,0)): ext3_get_inode_loc: bad inode number: 355 The boot device is a scsi hard disk, so initrd is used to load the scsi driver, before mounting /. So, it looks like the kernel rootflags= arg gets applied to the ramdisk, not the

Hi, to install current PC models (with new Intel NICs) via Kickstart/PXE, I wanted to add the newest e1000e-Treiber to initrd.img. With this modified image, the Kickstart kernel crashes with the following error messages: [...] md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (20480 != 32768) 6062080

Hi, had a few problems with using xen: First: built a xen from source (tgz) and make dist ... then made initrd with mkinitrd and modules=all in the mkinitrd.conf -> initrd.img was 14mb and set it up in the grub with module /initrd.... on boot it loads the initrd like: Loading ramdisk into ram .... done but then NO MODULES in the initrd are being loaded by the kernel, though initrd

Hi, I would like to do a network install using PIXES boot, however the ethernet device was not supported by centos installation (RTL8110SC). How do i add this module into the initrd? I know i can use: mkinitrd --with=r8169 `uname -r`, but i did not know what is the standard modules included in the installation initrd of Centos. Thanks! --beast

I'm trying to create a single floppy based boot disk that will, depending on what the user enters, boot redHat, SUSE or Debian. Does anyone have any sample syslinux.cfg files that might allow me to boot via nfs? Also, I'm having trouble fitting init into initrd.img any ideas? Thanks -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster

Hello, I would like to know if initrd is here to stay, now that klibc and initramfs are ready. As the multipath-tools maintainer, I'm facing the choice to 1) put the multipath configuration tool in the initrd * dynamic binary is possible * storage hba drivers as modules loaded * no klibc limitations (no mntent for libsysfs ...) 2) put the multipath configuration tool in the initramfs *

Sorry for my ignorance but....I''ve installed a debian lenny dom0 with a xen kernel, then I''ve configured two domX. I''ve noticed that there isn''t a kernel installed for these ones. I run aptitude to update packages, I''ve updatede the dom0 kernel but....the others? _______________________________________________ Xen-users mailing list

retitle 502123 xen-utils-unstable: Debian patch breaks paravirtualized guest initrd thanks I see that this bug is still present in pkg-xen svn: http://svn.debian.org/wsvn/pkg-xen/trunk/xen-unstable/debian/patches/tools-python-xen-xm-relative-path.diff?op=file Perhaps I wasn?t clear how severe this problem is. Using the current Debianized xen-utils-unstable, it is impossible to boot any

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

tag 502123 patch severity 502123 serious thanks Confirmed. This regression was introduced by a copy-and-paste error in debian/patches/tools-python-xen-xm-relative-path.diff (svn://svn.debian.org/pkg-xen -r531). Please apply this fix. --- debian/changelog 2008-12-04 16:50:04.000000000 -0500 +++ debian/changelog 2008-12-04 16:59:09.000000000 -0500 @@ -1,3 +1,10 @@ +xen-unstable

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1346945306 -7200 # Node ID 8a2eef481d3ab3ca5692dd0083c95cf314fe1da3 # Parent 19d367bf07b7687b831c212a57a70e73ea14d3b7 pygrub: always append --args If a bootloader entry in menu.lst has no additional kernel command line options listed and the domU.cfg has ''bootargs="--args=something"'' the additional

Got to minimize (barely) my filesystem and kernel and fit it into my usb key (256mb) My kernel was compiles with scsi and usb support built-in. My problem now is i can't mount my root filesystem when i tried to boot. kernel somehow takes time before being able to recognize my usb as a valid scsi device thus displaying VFS: Cannot open root device 08:01 this is my lilo.conf boot=/dev/sda

Howdy, I know that syslinux doesn't currently support this, but does anyone here know how I might go about getting some sort of boot process together that would have a single firmware image as opposed to seperate files for initrd, kernel, and root fs? Thanks.

Hello ! Maybe passing argument root=/dev/ram0 or root=/dev/rd/0 would help ? I use isolinux and it works in the isolinux.cfg sylvain > Message: 3 > Date: Fri, 13 Sep 2002 14:11:38 -0300 (ADT) > From: Geddes <jgeddes at unb.ca> > To: syslinux at zytor.com > Subject: [syslinux] Unable to mount root fs > > > Hey all, > > I'am able to use pxelinux to