From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38546) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZHYXC-0006lv-6m for qemu-devel@nongnu.org; Tue, 21 Jul 2015 10:28:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZHYX7-0006Jw-5E for qemu-devel@nongnu.org; Tue, 21 Jul 2015 10:28:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52764) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZHYX7-0006Jj-0L for qemu-devel@nongnu.org; Tue, 21 Jul 2015 10:28:37 -0400 References: <1437143854-2826-1-git-send-email-kraxel@redhat.com> <55AE0821.5040701@redhat.com> <55AE4D60.3000908@redhat.com> <55AE52A3.1060108@redhat.com> From: Paolo Bonzini Message-ID: <55AE570F.30602@redhat.com> Date: Tue, 21 Jul 2015 16:28:31 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL for-2.4 0/7] update ipxe roms, fix efi support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Gerd Hoffmann , Stefan Hajnoczi , QEMU Developers On 21/07/2015 16:25, Peter Maydell wrote: >> > >> > Well, it did say "This pull finally fixes the efi boot support. ipxe is >> > updated to the latest master, two non-upstream commits needed to make >> > efi work are added on top, and the build process is tweaked a bit". > Right, but if you want us to switch from "we just mirror > upstream ipxe" to "we have our own ipxe" then it's probably > better to start with that, rather than by submitting a pullreq > that can't be applied until we switch our ipxe workflow. > > Do we really need this for 2.4, or can we wait and sort > this out afterwards? It feels a bit late in the release > cycle to start doing this kind of thing to me. Well, it is a bugfix. shim.efi doesn't work with upstream iPXE, and hence doesn't work with the ROMs currently distributed by QEMU (Fedora applies the patches already). The patches have missed 2.3 and 2.4 because Gerd has been sending them again upstream every month. That said, I see your point. It's probably not of utmost importance as long as OVMF remains non-free and hence not shipped by most distributions. Paolo