similar to: PV-GRUB chainloading Grub2

Hello, I made an interesting observation related to the "Clocksource tsc unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found: Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status change 6001 Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status change 2001 Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status change

On Tue, 17 Dec 2019 at 23:19, Gregory Lee Bartholomew < gregory.lee.bartholomew at gmail.com> wrote: > On Tue, 2019-12-17 at 22:46 +0100, David Bala?ic via Syslinux wrote: > > Hi! > > I have bootable (USB flash) disk, that _appears_ to be using syslinux. > > (the word syslinux is in the PBR, in the hexdump). > > How can I chainload it? The payload seems to be a

Hello everyone, I am trying to chainload grub2 using both pxechain.com and pxechn.c32 and in both cases once grub2 loads it fails to find the grub config file on the server. My setup is as follows: 1. DHCP (192.168.1.2) server points to a multi pxe server menu on itself. The entry in the dhcp config file is: *class "installerator-pxeclients" { match if substring (option

Inspired from a similar patch posted on grub-devel for Grub2 I immersed myself into the code of Grub Legacy and came up with this absurdedly simple patch to allow syslinux or other bootloaders residing in logical partition to be chainloaded from GRUB Legacy (0.9x). Hoping it to be of help, regards Fulvio Scapin -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi! I have bootable (USB flash) disk, that _appears_ to be using syslinux. (the word syslinux is in the PBR, in the hexdump). How can I chainload it? The payload seems to be a file that I tried load with COMBOOT, COM32 etc, but nothing works (they report that the file is not in proper format, wrong magic number or simply crash). How to proceed? is there a 100% way to confirm that it is really

Hello, I have the following scenario: - GPT Partitioned USB disk with syslinux (or extlinux) on the first partition and a menu to boot each partition; all of them are iso9660 images of different linux distros, - Before dumping every iso image into its partition space on the USB disk I need to remaster it changing something on its initrd to be able to coexist with other linux distros on the

Hi, This is off topic for this list, but someone on this list may be able to point me in the right direction. For a couple of years I have been using ISOLINUX + MEMDISK and Smart Boot Manager to chainload a CD-ROM boot after loading a floppy image into RAM with MEMDISK. My problem now is that Smart Boot Manager does not support/detect SATA optical drives used in new hardware. Does anyonw

Hi, I am having troubles with chainloading and hopefully someone can provide me with some guidance. Here's what I am trying to do: * the media is a USB key * I have created a GPT on it * I have created an EFI partition, where I have installed the EFI flavor of syslinux, the various .c32 files required for chainloading and the configuration file which tells syslinux what to chainload

I have a number of syslinux based USB sticks which can be booted from PCs that support USB boot. I also have a number of PCs that do not support USB Boot. They are running Windows 2000 and Windows XP typically from ntfs formatted single partition drives. Is there a way to chainload syslinux residing on a plugged in usb stick from boot.ini? I've seen instructions for how to do this for OSs on

Hi syslinux list, Some months ago, hpa was kind enough to help me troubleshoot booting Extlinux in a system with the following particulars: * Windows Vista x64 bootloader in the MBR and Vista installed in /dev/sda1 * Extlinux 3.72 installed in the first sector of /dev/sda2 and Foresight Linux installed in /dev/sda2 (at the time I tried, 3.72 was the default bootloader in Foresight) The problem

On 6 June 2015 at 14:03, Didier Spaier via Syslinux <syslinux at zytor.com> wrote: > > > On 06/06/2015 12:19, Stoppa, Igor via Syslinux wrote: > >> So I'd like to not put all the kernels/initrds in it, because when I >> update one of the OSes, I would also have to update the corresponding >> kernel in the EFI partition. > > > IIRC this is not

HI. Got a question. When I assign a number of vcpus to a DomU, Are they dedicated to that VM? For example: If I have 16 vcpus available and 8 DomUs, should I assign 2 vcpus for each one? or could I assign more vcpus (i.e. 6) and the hypervisor takes care of it? Thanks -- ---------------------------------------------------------- Luis R. Romano Estudiante de Ingeniería en Computación. FCEFyN -

On 6 June 2015 at 17:22, Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, the most current (or "up-to-date") documentation about chain.c32 > at this time is located at: > http://www.syslinux.org/wiki/index.php/Chain.c32 Yes, I had a look at that, but frankly the archlinux pages were more newbie-friendly, so my research is 50% based on what I found there and for

Here is a patch that makes it possible to chainload GRUB2 core.img form chain.c32. It reuses the grub= parameter (used for chainloading GRUB Legacy stage2): - both loaded at 0x8000 - start execution at offset 0x200 (0x8200 in memory) GRUB2 allows to specify another "GRUB home dir" than the standard /boot/grub GRUB2 doesn't allow to change the configfile 'grub.cfg' name

Hello, I cannot boot with GRUB and SYSLINUX from a logical partition on my USB drive. Here is the test setup: - 4GB Flash drive with the following partitions: sdb1 Primary fat32 ~ 800MB sdb2 Primary fat32 ~ 800MB sbd3 Primary fat32 ~ 800MB sdb4 Extended partition sdb5 Logical partition ~ 800MB sdb6 Logical partition ~ 600MB - Grub files were copied to /dev/sdb1/boot/grub (Stage

I have a USB disk with syslinux files installed in /boot/syslinux, and the bootloader is installed into MBR or VBR I then extracted a *.iso file which uses syslinux as the bootloader, into root dir of the disk. The iso file contains a rescue OS or an OS installer. Now I got the directory /isolinux with files isolinux.bin and isolinux.cfg in this folder I can now boot into syslinux, but *what to

> On 2019-4-11 13:29, Lu Wei wrote: > > On 2019-4-10 1:20, Ady Ady via Syslinux wrote: > >>>>> #This item fails > >>>>> label dos > >>>>> menu label MS-^DOS 7.1 > >>>>> com32 chain.c32 msdos7=io.sys > >>> > >>> IO.SYS and COMMAND.COM are copied from a Windows98 system on another >

When chainloading one pxelinux from another (e.g., chainloading from say pxelinux 4.07 to pxelinux 6.02), can one pass parameters or somehow control the root directory and/or server IP address? Here's the need: we have a loaded-up PXE server working great under 4.07, and I'm not prepared to just switch the entire setup to a newer version of pxelinux, too many folks depending on a

Dear everyone, I have a simple and silly question. I'm using pxelinux in a small LAN - I'm using it to boot a few universal profiles based on Linux and DOS. I have a simple DOS-based "screensaver" (winter background theme with snow falling down) that I'd like to hook up as a default profile (say after 5 minutes timeout) into the PXElinux boot menu. That works - the

On 06/16/2014 10:41 AM, Gene Cumm wrote: > [...] Initially I wrote pxechn.c32 to allow further > modifications of the DHCP data [...] Awesome! In fact, this might allow us to install an automatic 'http' prefix on all subsequent requests, to avoid slow tftp --- or is that a bad idea, and/or is there a way to default all transfers to http without using pxechn and without prefixing