From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1VYdxn-000369-T1 for mharc-grub-devel@gnu.org; Tue, 22 Oct 2013 11:33:43 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53297) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYdxi-00035f-0Z for grub-devel@gnu.org; Tue, 22 Oct 2013 11:33:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VYdxd-0004FN-2v for grub-devel@gnu.org; Tue, 22 Oct 2013 11:33:37 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:40164) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VYdxc-0004DU-TL for grub-devel@gnu.org; Tue, 22 Oct 2013 11:33:33 -0400 Received: from mjg59 by cavan.codon.org.uk with local (Exim 4.72) (envelope-from ) id 1VYdx4-0003KV-Dp; Tue, 22 Oct 2013 16:32:58 +0100 Date: Tue, 22 Oct 2013 16:32:58 +0100 From: Matthew Garrett To: "Woodhouse, David" Subject: Re: EFI and multiboot2 devlopment work for Xen Message-ID: <20131022153258.GA12260@srcf.ucam.org> References: <20131021125756.GA3626@debian70-amd64.local.net-space.pl> <20131021135437.GD1283@fenchurch.internal.datastacks.com> <20131021185758.GD3626@debian70-amd64.local.net-space.pl> <1382433990.1657.66.camel@hastur.hellion.org.uk> <5266620602000078000FCA48@nat28.tlf.novell.com> <1382435127.1657.70.camel@hastur.hellion.org.uk> <526668A502000078000FCA7B@nat28.tlf.novell.com> <20131022134252.GA27302@phenom.dumpdata.com> <20131022144309.GA18547@phenom.dumpdata.com> <1382455537.8512.11.camel@shinybook.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1382455537.8512.11.camel@shinybook.infradead.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 93.93.128.6 Cc: "grub-devel@gnu.org" , "keir@xen.org" , Ian Campbell , "stefano.stabellini@eu.citrix.com" , Daniel Kiper , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xen.org" , Jan Beulich , "ross.philipson@citrix.com" , "boris.ostrovsky@oracle.com" , "Maliszewski, Richard L" X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Oct 2013 15:33:42 -0000 On Tue, Oct 22, 2013 at 03:25:39PM +0000, Woodhouse, David wrote: > Oh, ignore that. You want the *actual* PE executable entry point, as it > would get invoked by a real UEFI firmware. There are two problems with this: 1) The kernel will only boot if it's signed with a key in db, not a key in MOK. 2) grub will read the kernel, but the kernel will have to read the initramfs using EFI calls. That means your initramfs must be on a FAT partition. If you're happy with those limitations then just use the chainloader command. If you're not, use the linuxefi command. -- Matthew Garrett | mjg59@srcf.ucam.org