similar to: Error: ramdisk

Hi,   I am trying to build dom0 iso. I have following in my isolinux.cfg file. I see error: "Invalid or corrupt image file".   --- default 1 prompt 1 timeout 300 display menu.txt label 1   kernel boot/vmlinuz.vm   append boot/xen.gz  ramdisk_size=131072 initrd=boot/ramdisk.gz root=/dev/ram0 ---   The image I check is valid. xen.gz is actually xen-3.4.2.gz: xen.gz: gzip compressed data,

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

I''m trying to boot a PV guest using the "old method" of passing kernel= and ramdisk= and it appears to work fine with a "small" initrd but not with a "large" one. (Small is 4MB, large is 154MB.) I''m sure both of the initrd''s are properly gzip''ed etc. Unpacked, the large one approaches 400M. By doing some kernel startup debugging,

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

Hello, I have a problem with a 2.5.62 kernel and ramdisk. I am using isolinux to create a cd that loads some of its partition in ramdisk. The script involves mounting a ramdisk (e2fs) on /fake/ramdisk, copying part of the cd to that mount point, unmounting it, and remounting it on /fake/needwrite. The problem is that, although the content of /fake/needwrite gets correctly copied, the content of

Hi all, I want to have a warmboot nonvolatile ramdisk to put and start XP from ram. That means that the ramdisk and its content have to survive a reboot on a "normal computer"! (No battery ...hihi) First I make a try with Microsoft ramdrive.sys and switch /e in config.sys from Dos 6.22 and with qemm386.sys but that doesnt work for me. Qemm (8, 97)does not work together with harddrive

On Fri, Jan 22, 2016 at 11:02 AM, Ed Heron <Ed at heron-ent.com> wrote: > I'm still running CentOS 5 with Xen. > > We recently replaced a virtual host system board with an Intel > S1400FP4, so the host went from a 4 core Xeon with 32G RAM to a 6 core > Xeon with 48G RAM, max 96G. The drives are SSD. > > I was recently asked to move an InterBase server from

I'm having loads of problems with recordings, as in crappy audio quality and lost pieces of the recordings. I've been searching for a solution and the solutions i find on the interwebs include a ramdisk, for local recording, or another machine, handling the recording. I guess the ramdisk would be the "easy" solution and the external machine would be little harder to set up. I do

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 Xen Security Advisory CVE-2012-4544 / XSA-25 Xen domain builder Out-of-memory due to malicious kernel/ramdisk ISSUE DESCRIPTION ================= The Xen PV domain builder contained no validation of the size of the supplied kernel or ramdisk either before or after decompression. This could cause the toolstack to consume all available RAM

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, Dovecot 1.2.5, centos 5.4. We are using NFS for mail, but indexes are local and on a ramdisk. However I'm getting logs such as: Mar 02 11:47:14 POP3(USERDELETED): Error: Timeout while waiting for lock for transaction log file /ramdisk/indexes/DOMAINDELETED/USERDELETED/.INBOX/dovecot.index.log Our NFS is rather busy, and we having other warnings to that affect, but wouldn't

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-4544,CVE-2012-2625 / XSA-25 version 2 Xen domain builder Out-of-memory due to malicious kernel/ramdisk UPDATES IN VERSION 2 ==================== Clarify that XSA-25 is reporting, via the Xen.org security process, both CVE-2012-4544 and CVE-2012-2625. Also we would like to

OS: FreeBSD 6.2-RELEASE Environment = VMWare (Version 5) and Computer (CPU=Intel P4 2.4G, Memory=Kingston 1G DDR400, Storage=2G CF) create a less-than 100MB of image (image for ramdisk, mfs root) The loader.rc { load kernel // The kernel used 6.2 GENERIC load -t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=95k } above config can boot normal. create

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:

This one about pvops kernel 2.6.32.24 under Xen 4.0.1 on top of Ubuntu 10.10 Desktop http://bderzhavets.wordpress.com/2010/10/15/set-up-xen-4-0-1-libvirt-0-8-3-on-top-of-ubuntu-10-10-desktop/ Boris. --- On Thu, 10/21/10, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-users] Re: [Fedora-xen] another xen build and pvops kernel To:

On Fri, 2016-01-22 at 14:56 -0600, NightLightHosts Admin wrote: > On Fri, Jan 22, 2016 at 11:02 AM, Ed Heron <Ed at heron-ent.com> wrote: > > I'm still running CentOS 5 with Xen. > > > > We recently replaced a virtual host system board with an Intel > > S1400FP4, so the host went from a 4 core Xeon with 32G RAM to a 6 core > > Xeon with 48G RAM, max

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