similar to: mddisk(ramdisk) root system that image size limit ?

I have a build process (which worked at release 7.3) that makes a bootable ISO using a ramdisk image as the boot volume. At release 8 it panics right after reporting the real memory size with: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode ... [thread pid 0 tid 0 ] Stopped at pmap_enter+0x19a: moveq (%rcx),%r14 (I have the text frozen on

Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a

Hi, there's a regression going from 6.2 to 6.3, where it will panic upon booting the kernel within vm_fault. This problem has been discussed before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of May. It affects multiple (but identical) systems, here's an verbose boot leading to the panic. Please note that 6.2 was running fine on these machines, they also boot

Hi. I've made a new attempt at build Dovecot. The build and then install processes appeared to work find. Then when I try to run Dovecot it reports the error: /share/MD0_DATA/optware/opt/sbin/dovecot: error while loading shared libraries: libdovecot.so.0: cannot open shared object file: No such file or directory To get a better idea of what's going on, I added

Hi, I am a long time OpenBSD user trying FreeBSD. I am attempting to upgrade my system from FreeBSD RELEASE 4.7 to "STABLE" This is my first post to this list so please be gentle : ) I followed http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html But when I get to "21.4.9 Install the New System Binaries" This happens: root@smeagol /usr/src # make

Covert common_utils_tests to use oUnit as testing framework, replacing the hand-made assert in favour of structured unit tests and better error reporting. common_utils_tests is now built only when the oUnit module has been found. --- mllib/Makefile.am | 17 ++++- mllib/common_utils_tests.ml | 155 +++++++++++++++++++++++++++----------------- 2 files changed, 108 insertions(+), 64

Hi All, I am using Centos4.0 and running Squid Reverse Proxy for image caching , i have configured RAMDISK of 265 MB for one cache folder in preproduction environment for testing now i have upgraded RAM upto 8GB, but when i change ramdisk_size parameter in grub.conf and rebooted the server when i tried to format and mount it doesn't work. Can anyone please help me how to increase RAMDISK

Hi, are there any plannings to integrate a kind of ramdisk funktionality into ext3? I imagine a dynamic ramdisk into which only modified files of a read-only mounted ext3 are copied in order to have read-write access without really writing (because the filesystem is on a compact flash disk, for example). Regards, Daniel -- <> d.vollbrecht@scram.de -> <http://www.scram.de>

I know this is not a question for syslinux itself, but a question for syslinux usage on Linux. I use pxelinux to boot Linux. I know I can use "root=/dev/nfs nfsroot=ip:/dir" to mount the NFS as root file system. But it needs me to prepare several different directories for different clients and each directory should include a initrd.gz copy (e.g., cp/mv/mkdir utilities, etc). My

Hi, I''m trying to boot XEN via network, so I''m trying to create a rootfilesystem over a RAM disk for XEN. Has anyone done that before? Thanks, Gianluca _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I have been messing with QCOW on Xen and I''ve come to the conclusion that nobody actually uses it otherwise it would work. Has anyone gotten QCOW2 and Xen to work reliably? I have 40 PV VMs that are identical (initially) and would like to move from separate disk images to one base image sitting in a ramdisk and the COW images hosted on an iSCSI storage device. The VMs would boot off the

I have written simple minded script to create domU on ramdisk from three small but -well proofed- distros : Tinycore Slitaz and Puppy . Single cmdline xm create (no config file) to start them for easy demo . http://sourceforge.net/projects/toysbox/files/LearnEmbeddedLinux/CreateDomUin3minutes.html/download or read it here:

<..trying again after changing outgoing e-mail options to avoid bad headers...> I'm trying to use syslinux 3.08-pre11 on a Gateway E4000 with the (sample) config file below, and the ramdisk images fail to boot if selected as a menu option, but do boot if I press ESC and type the command line manually. The two options are for the same floppy image, but the first is compressed, the

Way are not a ramdisk included with the images from jailtime.org That seems this is needed _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

This patch (against unstable) makes sure that the skel/etc/init.d/rcS file is executable before building the final ramdisk image. This should fix the problem some people are having with their ramdisk builds. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com _______________________________________________ Xen-devel mailing list

Hi, I am trying to install Xen on my Gentoo x86_64 Dual-Core AMD Opteron machine. But its failing with the following error. RAMDISK: Couldn''t find the valid RAM disk image starting at 0. VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot oprtion Kernel panic not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I'm supporting a number of consumer devices (e.g. small NAS devices) in Debian. They typically don't export the serial console and don't have any other output devices. We perform the installation via SSH on such devices and start SSH automatically when the system boots so people can login. This works pretty well but sometimes a device stops to boot for no good reason. This is

On Centos 4.x 32 I want to create like a 64Mbyte ramdisk. Is there a problem putting 30k to 80k empty files on a ramdisk? Is there a simple howto on creating a ramdisk that anyone knows of off the top of there head? Matt

Hello! I'd like to load a ramdisk with syslinux, but from another disk. And I've found this in the syslinux faq: "An initrd is loaded from a DOS file if the option "initrd=filename" (where filename is the filename of the initrd image; the file must be located in the root directory on the boot floppy)"

Erik Groth wrote: > Thanks for helping me out. > Skipping the "load_ramdisk" part fixed the "RAMDISK: couldn't find valid > RAM disk image" problem, but the "Kernel panic: Unable to mount root fs > on 01:00" part is still there, what can cause this problem? 01:00 is a > valid device right? > 01:00 is /dev/ram0 -- I would guess that your kernel