[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 00/23] x86: multiboot2 protocol support


  • To: xen-devel@xxxxxxxxxxxxx
  • From: PGNet Dev <pgnet.dev@xxxxxxxxx>
  • Date: Fri, 30 Oct 2015 08:44:53 -0700
  • Delivery-date: Fri, 30 Oct 2015 15:45:07 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.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.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.