On Fri, Oct 30, 2015 at 08:44:53AM -0700, PGNet Dev wrote: > 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?
If it supports multiboot2 with my extensions then it should work. However, I do not think it is true because all is in development state and nothing is set in stone. I am going to release next version of my patches in November. I hope then we will be able to establish main things and maybe it will be later sucked by systemd-boot. I think that you should ask systemd-boot guys what they think about that. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
