similar to: "RAMDISK" problem

Hi Xen developers, We are hitting a DomU Linux kernel panic and we''d like to find a solution for it. We are porting our virtual appliance to Amazon''s AWS. Our kernel is 2.6.27.57. We know it is old but we have to stay with it for now. The problem is when the kernel (64-bit) boots up in EC2 ( a large instance with 7.5 GB memory), the kernel crashes when hitting the BUG in

I am having a problem with setting up diskless clients under CentOS 5.2. I have everything working under CentOS 4.7. This is an adaptation of the (somewhat old) Diskless Linux with PXE HOWTO by Gerd v. Egidy, originally at the URL http://www.intra2net.com/opensource/diskless-howto/, which is now defunt (there is a mirror of it at http://blog.chinaunix.net/u/2389/showart_82438.html). What I am

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

--32u276st3Jlj2kUU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all (two) klibc hackers! 8) Here's the stuff I've been using to build an initramfs image and run it on one of my machines. Unfortunately, the "init" script contains hard coded information about where to find the root, etc, but it should give people a working base to start from. It

isoconfig.sys file below - Only change from past is adding stuff after the bz28.7 kernel. DEFAULT vesamenu.c32 Prompt 0 menu color screen 37;40 #80ffffff #00000000 menu color border 30;44 #40000000 #00000000 menu color title 1;33;44 #c0fdd017 #00000000 menu color unsel 37;44 #90ffffff #00000000 menu color hotkey 1;37;44 #ffffffff #00000000 menu color sel 7;37;40

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have done some additional testing, and gotten it a bit close to what I was looking for. I had to modify the cat.c to eliminate the printing of the arguments and file name, and added a Press Enter to return menu line. With the below isolinux.cfg the options do display the files, and pressing enter than returns to the vesamenu. DEFAULT

I have syslinux booting slax off of a usb stick but in the process I think I may have found a bug in syslinux im using version syslinux-3.31 my syslinux.cfg use to look as follows <== beginning display boot/splash.cfg default slax autoexec=startx prompt 1 timeout 40 F1 boot/splash.txt F2 boot/splash2.txt F3 boot/splash.cfg label slax kernel boot/vmlinuz append vga=769 changes=slaxsave.dat

I am running isolinux 4.02 and ramdisk_size does not seem to have an effect on the ramdisk size. No matter what I set it to in the isolinux.cfg file it seems the limit is 32768. I get the error: ram0: rw=0, want=360456, limit=32768 EXT2-fs error (device ram0): My isolinux.cfg file: LABEL EB KERNEL vmlinuxE APPEND initrd=bos.img root=/dev/ram0 rw ramdisk_size=545000 I am running the 2.6.38.2

Hi, I am trying to track down a ISOLINUX boot problem on my workhorse computer. Booting slax-6.0.0-rc5.iso from www.slax.org (a live distro) from CD gives the following messages: Loading /boot/vmlinuz ........... Loading /boot/initrd.gz ............ Ready. _ Silence. The next message should be, but does not appear: Uncompressing Linux ........... This message appears with the same CD on an old

This is my crash script for 2.4.17-rc1 and rc2 It works exactly as expected first time. Second time your system is toast with an exception error. I think it kills the daemon. I've tried it with varying ram disk sizes, up to 256Mb and in UP and SMP mode. The only thing I've seen was putting two of them into a script with the intention of having a one stop crasher didn't

There is a maximum of 255 characters of parameters you can pass to the kernel. At least that's what I recall, but I may be wrong. -----Original Message----- From: Roberto De Leo [mailto:deleo at unica.it] Sent: Thursday, October 03, 2002 5:19 PM To: syslinux at zytor.com Subject: [syslinux] maximum number of characters in APPEND Hi, I wonder whether there is a maximum number of

hi ya syslinuxerz - i've been slowly working on a making a custom bootable standalone usb-stick with X11 and kde - it's basically builds itself off of a slackware-10.1 server - create a custom initrd.gz ( /dev/ram0 ) http://linux-boot.net/Bootable/InitRD/ - create a custom rootfs.gz ( /dev/loop0 ) http://linux-boot.net/Bootable/RootFS/ - create X11 and kde loopfiles

Petr Vandrovec wrote: > Hello, > one of FreeDOS developers pointed out (in > http://www.vmware.com/community/thread.jspa?threadID=11324&messageID=109507&#109507) > that FreeDOS does not work under VMware when using ISOLINUX 3.0x. After > looking at their ISO image I downloaded syslinux-3.05, and there seems > to be bad bug: > > You have this in kernel.inc:

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

Hi, I have setup pxelinux like this, default linux label=linux kernel linux append initrd=rootfs.img ipappend 1 I have my dhcpd.conf like this, allow booting; allow bootp; group{ filename "pxelinux.cfg/pxelinux.0"; host deploy { next-server 192.168.1.254; hardware ethernet 00:0E:A6:22:28:21;

I have a Lilo.conf file, which I have tried for many hours to convert to Syslinux. I looked around on the web for references on translating some of the components. I want to convert it to Syslinux/Isolinux. Any suggestions would be greatly appreciated. When I tried to convert it I made sure that the kernel and initrd had proper DOS names and such. -Michael =:LILO.CONF:= prompt timeout=10

dear friend. i have mips board with BCM sibyte 1125CPU(use board sibyte 1250 swarm.) i use linux-kernel 2.6.12-rc1 download from linux-mips.com i use kernel 2.4.26 before this time, it's work ok at 2.4.26 with Ramdisk-busybox when i try to use ramdisk in 2.6.1x version, i found that ramdisk i not exist, i don't known how to use it again(i had try a patch for get ramdisk init to

hi everyone, I am trying to create a custom live cd but I am having some problems with isolinux. A rough sketch of my process : 1) bootstrapped a small rpm based system in /target 2) dd if=/dev/zero of=images/initrd.img bs=1k count=262144 3) /sbin/mke2fs -F -v -m0 images/initrd.img 4) mount -o loop images/initrd.img ./initrd_tmp 5) cp -av /target/* ./initrd_tmp 6) umount 7) gzip -9 <

Hello there, I might have found some bug in xen-utils-unstable (amd64). When starting some Linux in domU, the ?ramdisk? parameter of my .cfg file is overridden and has the same value as the ?image? parameter. That ends in an unbootable VM (vmlinuz is not a ramdisk ?) ?No filesystem could mount root, tried: cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(x,y)?