similar to: UEFI memdisk freeze

Dear Syslinux folks, For a firmware update I am following the Gentoo Wiki [1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk

I've been trying to use memdisk with grub2 to boot some iso images -( I've done this without any problem with pxe ) There is a memdisk.mod in /boot/grub/ and I've seen some material talking about this, but no example of a menu. After trying countless permutations - Right now I have : menuentry "Memtest-Plus 4.2" { echo `hello` insmod lvm

Hello, I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: menuentry 'boot ISO image' { linux16 /memdisk iso initrd16 /my-image.iso.gz } When selected, this starts to boot and then fails with: Ramdisk at 0x37979000, length 0x0033b298 gzip image: decompressed addr 0x7f7f7000, len

Haven't yet had a need for 10MB FDD images. The biggest I had to create was 5MB (5760kb). At that time I had to use WinImage to create the FDD image and it took me a while to figure out the correct settings. My notes state: "I'm getting 'missing FAT' errors in WinImage, and 7-zip complains about 'unexpected end'. The fix is to increasing the FDD Heads from 2 to 4 and

In other words: I'm suggesting to use WinImage as it also allows easy injection of new files *and* updating of already existing files. May I ask which vendor is distributing a DOS FW update that is 20MB? I'd like to see the files. Sometimes you just need the .bin/.rom and the actual FW update EXE and it would fit a 5MB FDD image. On Mon, Jun 18, 2018 at 2:03 PM, R S <rene.shuster at

Hello, I'm sorry to bother, but was hoping that someone might be able to help me with this situation. I have a multiboot that I've maintained now for years, with no issues running on MBR or UEFI-CSM; however, I've now been tasked with using this on newer Dell systems which do not allow any kind of MBR booting whatsoever. I finally have my menu populating, but when any ISO attempts to

Hello, I'm trying to boot a dos floppy stored on a disk image which is initially loaded over pxe using memdisk. I've created the disk image as follows: dd if=/dev/zero of=$IMGLOCATION/$IMGNAME bs=$(( 1024 * 1024 )) count=20 LOOPDEV=$(losetup --show -f $IMGLOCATION/$IMGNAME) MAJOR_MINOR=$(ls -l $LOOPDEV|awk '{print $5$6}'|sed 's/,/:/') DMSIZE=$(( $(ls -l

> Hello, > > I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: > > menuentry 'boot ISO image' { > linux16 /memdisk iso > initrd16 /my-image.iso.gz > } > > When selected, this starts to boot and then fails with: > > Ramdisk at 0x37979000, length 0x0033b298

Hi I would like to start a iso from my USB-Pendrive so I got a Hiren BootCD amd PartedMagic iso + GRUB 2 (1.98~20100115-1) on my USB-Pendrive. My problem it take up to 30sec until the ISO is booted my menu entry: linux16 /memdisk iso initrd16 /boot/iso/pmagic.iso Thanks for any hints M. Simon _________________________________________________________________

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

isdtor writes: > Gordon Messmer writes: > > On 10/21/19 6:38 AM, isdtor wrote: > > > Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style pxe config file as per ... results in a grub (legacy) prompt on the target machine. > > > > > > Have you tried using the file from the installation tree? > > > >

Hello, I'm investigating ways to boot a DOS floppy image stored on the FAT32 EFI System Partition using Syslinux and Memdisk. The system will be running Win8 using UEFI mode (GPT disks) and secure boot off. Change the Windows efi boot loader is the easy part... With the current syslinux's alpha version (6.0), is it possible to boot the syslinux's efi module from the FAT32 EFI

blktap2: fix makefile of vhd for parallel make With parallel make, libvhd might not be created before link resulting in link error. This patch guarantees it. Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp> diff --git a/tools/blktap2/vhd/Makefile b/tools/blktap2/vhd/Makefile --- a/tools/blktap2/vhd/Makefile +++ b/tools/blktap2/vhd/Makefile @@ -12,6 +12,9 @@ CFLAGS +=

Guys, I'm trying to compile the Xen 4.0.0 via debian/rules makefile but I got this: administrativo at sid01:~/xen/xen-4/xen-4.0.0$ make -f debian/rules build-tools ..... make -C lib all make[7]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib' make[7]: Nothing to be done for `all'. make[7]: Leaving directory

I was wondering if someone can shed some light on why vhd files created with qemu-img don''t really work right with vhd-util and consequentially blktap in general. To validate the incompatiblity its simple enough to do qemu-img create -f vpc test.vhd 40g vhd-util snapshot -n child.vhd -p test.vhd Which will show the below and then the headers don''t display the BATMAP summary:

Add ''-C'' (nocow) option to vhd-util create. Btrfs has terrible performance when hosting VM images, even more when the guest in those VM are also using btrfs as file system. One way to mitigate this bad performance is to turn off COW attributes on VM files (since having copy on write for this kind of data is not useful). According to ''chattr'' manpage, NOCOW

Hi there, I''m running several VMs within Xen, and now I''m trying to create/revert snapshots of my VMs. Along with Xen and blktap2, another utility, vhd-util is also delivered, and according to its description, i guess I can use it to create/revert VM snapshots. To create a snapshot is actually easy, I just call |vhd-util snapshot -n aSnapShot.vhd -p theVMtoBackup.vhd | But

Im a long time PXE boot fan. I use it for wimbooting windows PE, linux images via http, and memtest mainly. Ive got it nicely customised with my own graphics etc. Then UEFI booting came along. Till now ive been content simply setting bios's to CSM mode and doing my thing.... Ive had another go at EFI PXE booting and can now get the menus and grahics from syslinux working, but I cannot get

I have try to resize one vhd file with vhd-util, i did some test... For example i have try: vhd-util resize -n /mnt/vm/disks/ring-12.disk1.vhd -s 6000 but output always: options: <-n name> <-j journal> <-s size (in MB)> [-h help] I not understand what i wrong, someone can help me please? -- View this message in context:

Hi all, I`m evaluating methods for nightly "snapshot" a physical win2003 to xcp vm. I know it would be a lot easier and reliable just to to one convert one time and start to generate real vm snapshots, but at this time I cannot use this method. I tested the sequence: disk2vdh -> xenconvert (to xcp), but a big deal of using this method is that xenconvert does not send