From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45296) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Za3eL-0001pG-Vm for qemu-devel@nongnu.org; Thu, 10 Sep 2015 11:20:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Za3eI-00026m-2i for qemu-devel@nongnu.org; Thu, 10 Sep 2015 11:20:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34027) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Za3eH-00026f-UI for qemu-devel@nongnu.org; Thu, 10 Sep 2015 11:20:30 -0400 Message-ID: <1441898426.11233.37.camel@redhat.com> From: Gerd Hoffmann Date: Thu, 10 Sep 2015 17:20:26 +0200 In-Reply-To: <55F19C96.50709@ipxe.org> References: <1441620856.27149.11.camel@redhat.com> <55ED98EA.4060101@ipxe.org> <1441637892.27149.34.camel@redhat.com> <55F19C96.50709@ipxe.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [ipxe-devel] EFI_PXE_BASE_CODE_PROTOCOL List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Brown Cc: ipxe-devel , qemu-devel Hi, > > The file is simply placed as "grub.cfg" in tftproot, next to grubx64.efi > > Thanks. From my experiments, it seems that GRUB is using the hardcoded > path /efi/boot/grub.cfg to locate the configuration file, regardless of > where grub.efi was loaded from. Hmm, probably depends on how you are building it. There are also tools like grub2-mknetdir and grub2-mkstandalone. Pretty confusing :( I'm using the binary shipped with RHEL. The centos one should show the same behavior. https://ftp.fau.de/centos/7.1.1503/os/x86_64/EFI/BOOT/ There is a pretty readable grub.cfg file too btw. Given there are no grub2 modules anywhere I suspect that binary was created with grub2-mkstandalone. HTH, Gerd