similar to: kexec to syslinux

On Tue, Feb 14, 2017 at 10:58 AM, H. Peter Anvin <hpa at zytor.com> wrote: > On 02/08/17 06:33, Jorge Almeida via Syslinux wrote: >> Is it possible to kexec to the syslinux interface, thus bypassing the >> hw initialization? >> What would be the kexec command? >> >> kexec -l ??? --append=??? --initrd=??? >> > > It is theoretically possible but

> Is it possible to kexec to the syslinux interface, thus bypassing the > hw initialization? > What would be the kexec command? > > kexec -l ??? --append=??? --initrd=??? > > TIA > > Jorge Almeida FWIW... Other bootloaders include (or can generate) a binary file that behaves as a (linux) kernel. Such binary file(s) can potentially be used for chainloading

Hi, I bought a USB hard drive, got Mandriva installed on it, and made it bootable with extlinux. Works great on machines that can boot from USB. I also created a boot cd using the instructions in the wiki. This is working too. The only problem with the boot cd is that I had to copy the kernel, initrd, etc. to the cd. This means that whenever I install a new kernel I'll have to create and

New module which check if the PLoP Boot Loader already has booted a CDROM or USB drive by checking for the presence of the PLoP INT13h hook. The following assembly code (NASM) can detect the PLoP INT13h hook: mov eax,'PoLP' ; Reverse of 'PLoP' mov ebp,'DKHC' ; Reverse of 'CHKD' int 13h cmp eax,' sey' ; Reverse of 'yes ' jz

On 02/08/17 06:33, Jorge Almeida via Syslinux wrote: > Is it possible to kexec to the syslinux interface, thus bypassing the > hw initialization? > What would be the kexec command? > > kexec -l ??? --append=??? --initrd=??? > It is theoretically possible but is likely to break on many systems. To boot it from a raw disk (the normal operation for Syslinux) would require a

> Daniel Kiper <daniel.kiper at oracle.com> writes: > > > Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default > > Linux infrastructure and require some support from firmware and/or hypervisor. > > To cope with that problem kexec firmware infrastructure was introduced. > > It allows a developer to use all kexec/kdump features of given firmware

> Daniel Kiper <daniel.kiper at oracle.com> writes: > > > Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default > > Linux infrastructure and require some support from firmware and/or hypervisor. > > To cope with that problem kexec firmware infrastructure was introduced. > > It allows a developer to use all kexec/kdump features of given firmware

Hi Shao Miller, I found another ISO that doesn't work with MEMDISK-ISO. It is the ISO of the PloP bootmanager. It is a ISO which uses floppy emulation. When I boot it with MEMDISK-ISO (run from Syslinux), my PC instantly reboots. When I extract the floppy image from the ISO and boot this file with MEMDISK, it works fine. Grub4dos iso emulation works fine for this iso. When using Grub4dos

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

Hi all, I was messing around with kexec and it seems to work just fine on KVM, but for Xen domU images, it doesn't work at all. Daniel, I saw some patches from you back in September 2012 for adding this support for Dom0, but they don't seem to have gone into the kernel (but other patches went into kexec-tools at that time.) You mention that domU support is "easy" after your

I have updated syslinux in Parted Magic's test version to the 5.10 release. With 4.06 I booted plop like this: LINUX /boot/plpbt/plpbt.bin Now it says /boot/plpbt/plpbt.bin... ok Booting kernel failed: Invalid argument Other "extras" like IPXE, HDT, memtest86+, chntpw, Super Grub Disk, etc... all work with 5.10. Revert to 4.06 and plop works again. Is this a problem with syslinux

Hello, trying to update to the latest kexec version I'm blocked by the lack of basename() and vfscanf() in klibc. I've noticed it only recently because I'm building almost exclusively for arm. This commit intruduced the issue: http://git.kernel.org/cgit/utils/kernel/kexec/kexec-tools.git/commit/kexec/arch/i386/x86-linux-setup.c?id=3bf0213789d56054f601c5a06372f78567aacdd9 Has

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

On Wed, Feb 08, 2017 at 06:33:35AM -0800, Jorge Almeida via Syslinux wrote: > Is it possible to kexec to the syslinux interface, thus bypassing the > hw initialization? > What would be the kexec command? > > kexec -l ??? --append=??? --initrd=??? > Question seen, but not understood. To me is syslinux a bootloader, started by (Hardware) BootROM and it starts a Linux kernel.

The following series improves kexec in a Xen PVonHVM guest. It is available via git: git://github.com/olafhering/linux.git xen-kexec-XS_RESET_WATCHES-3.0 A new xenstored command XS_RESET_WATCHES has been added in xen-unstable.hg changeset 23839:42a45baf037d. The command removes all watches and transactions for the guest. The following patches make use of the new command to wipe all existing

Add xs_reset_watches function to shutdown watches from old kernel after kexec boot. The old kernel does not unregister all watches in the shutdown path. They are still active, the double registration can not be detected by the new kernel. When the watches fire, unexpected events will arrive and the xenwatch thread will crash (jumps to NULL). An orderly reboot of a hvm guest will destroy the

https://bugs.freedesktop.org/show_bug.cgi?id=62848 Priority: medium Bug ID: 62848 Assignee: nouveau at lists.freedesktop.org Summary: xorg not start after kexec when use nouveau QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: SuloevDmitry at gmail.com