similar to: booting a domU from a cd to run a linux distro installer

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 as the screenshot [0] shows, my virtual machines aren''t showing up as running. This causes me a few problems. One being if I do xm shutdown SMGL-1 it simply powers it down, it doesn''t send the "shutdown signal" or whatever makes it go away :) I''ve done a from source install using the instructions mentioned [1].

Hello, When I upgrade syslinux from 2.13 to 3.02. my linux floppy doesn't boot anymore. steps: dd if=/dev/zero of=fdimg bs=18k count=160 mkdosfs fdimg syslinux fdimg mount -o loop fdimg /mnt cp files/* /mnt/ umount /mnt then use memdisk load fdimg the files includes: vmlinuz initrd syslinux.cfg message.txt f1.txt ... it only prompts 1 line: SYSLINUX 3.02

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, Maybe I am just not looking in the right spot but I can't figure out how to set a default menu in my isolinux.cfg. This is what it looks like: PROMPT 0 TIMEOUT 40 DEFAULT /boot/vesamenu.c32 LABEL cubez MENU LABEL Graphics mode (Compiz) - Experimental KERNEL /boot/vmlinuz APPEND vga=0x317 initrd=/boot/initrd.gz ramdisk_size=9999 root=/dev/ram0 rw chexpand=256 load=cubez

Hi Team I need to run vfio driver using qemu and I'm using below xml file for this.. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>instance</name> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu

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

Hi, I am trying to load kernel 2.6.6 on a Soekris net4521 from the network using PXE. I built my initrd with mkinitrd. RedHat nash (while running linuxrc) hangs after mounting /proc and says "Creating block devices". I am using the pxelinux.0 from the syslinux-2.10 distribution and the kernel and initrd were built on redhat 9.0. I built my kernel with BLK_DEV_RAM, RAMFS, TMPFS,

Hi Dongyang, Yan, When testing BTRFS with RAID 0 metadata on linux-3.3, we see discard ranges exceeding the end of the block device [1], potentially causing dataloss; when this occurs, filesystem writeback becomes catatonic due to continual resubmission. The reproducer is quite simple [2]. Hope this proves useful... Thanks, Daniel --- [1] attempt to access beyond end of device ram0: rw=129,

hi, I want to prepeare a CD which will use isolinux to boot so I got the source code of isolinux. Unfortunately I couldn't find enough document to satify my needs.Therefore I got the isolinux folder of Xubuntu CD and I have modified the isolinux.cfg file.My content of modified isolinux.cfg file is shown below. DEFAULT /boot/kernel-2.6.16.24-49 GFXBOOT bootlogo APPEND boot=boot

Using kernel is 2.4.30 win32 syslinux 3.52 Preparing floppy under Windows XP SP2 1) Preparing boot floppy ======= syslinux.cfg content ====================== PROMPT 0 DISPLAY warning.txt DEFAULT kernel APPEND root=/dev/ram0 rw initrd=ukmrd.gz ramdisk_size=5000 bdev=/dev/fd0 ip=192.168.422.25 ipm=255.255.255.0 ipreq=n ipg=192.168.42.1 ipdns=192.168.42.2 mnet=pcnet32 durl=http://KP/ukminstall

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've written a patch to add option-key submenus to menu.c32 and vesamenu.c32 for doing things like changing the video mode. This was inspired the the patch that SuSE applies to the syslinux family and Grub, without the ugly pseudo-PostScript spaghetti. The patch may be found at http://www.valleyhold.org/~gordons/syslinux-optmenus.diff (it's over 30K, so posting it here didn't seem

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

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,

Message: 7 Date: Wed, 15 Jun 2011 19:17:36 +0800 From: Lee Eric <openlinuxsource at gmail.com> To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> Cc: Wen Wei Tang <tangww at cn.ibm.com>, Xiao Dong Zhao <zhaoxd at cn.ibm.com>, Shu Hua SH Chen <cshchen at cn.ibm.com> Subject: Re: [syslinux] error when booting Message-ID:

I am trying to create a bootable cd from a working LFS 6.1 partition. Thank you in advance for any thoughts on this. This is the error I get: ISOLINUX 3.10 2008-08-24 Copyright (C) 1994-2005 H. Peter Anvin Could not find kernel image: lfskernel-2.6.11.12 boot : _ under /isolinux/ I have these files: isolinux.bin I've tried 3.10 and 3.09 isolinux.cfg: default livecd label livecd

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

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