From mboxrd@z Thu Jan 1 00:00:00 1970 From: PGNet Dev Subject: Re: [PATCH v2 00/23] x86: multiboot2 protocol support Date: Fri, 30 Oct 2015 08:44:53 -0700 Message-ID: <56339075.9010403@gmail.com> Reply-To: PGNet Dev Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Re: > The final goal is xen.efi binary file which could be loaded by EFI > loader, multiboot (v1) protocol (only on legacy BIOS platforms) and > multiboot2 protocol. This way we will have: > - smaller Xen code base, > - one code base for xen.gz and xen.efi, > - one build method for xen.gz and xen.efi; > xen.efi will be extracted from xen file > using objcopy; PE header will be contained > in ELF file and will precede Xen code, > - xen.efi build will not so strongly depend > on a given GCC and binutils version. As of v220, systemd provides systemd-boot (formerly gummiboot) https://wiki.archlinux.org/index.php/Boot_loaders#systemd-boot https://wiki.archlinux.org/index.php/Systemd-boot#EFI_boot and is apparently capable of booting EFISTUB kernels. Will the aforementioned goals enable direct boot using systemd-boot on EFI platforms ? Or is it possible even now? As my current test distro is Opensuse, with systemd v < 220, I've not yet tested.