From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjpM2-0001Fd-7w for qemu-devel@nongnu.org; Fri, 22 Nov 2013 06:57:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VjpLt-0006F6-Pq for qemu-devel@nongnu.org; Fri, 22 Nov 2013 06:56:58 -0500 Received: from mail-ee0-x236.google.com ([2a00:1450:4013:c00::236]:54713) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VjpLt-0006F2-HM for qemu-devel@nongnu.org; Fri, 22 Nov 2013 06:56:49 -0500 Received: by mail-ee0-f54.google.com with SMTP id e51so561933eek.13 for ; Fri, 22 Nov 2013 03:56:48 -0800 (PST) Sender: Paolo Bonzini Message-ID: <528F467B.2000202@redhat.com> Date: Fri, 22 Nov 2013 12:56:43 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1385072461-31317-1-git-send-email-lersek@redhat.com> <1385072499-31367-1-git-send-email-lersek@redhat.com> <528F2385.50300@redhat.com> <528F4419.6010504@redhat.com> In-Reply-To: <528F4419.6010504@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [edk2] [edk2 PATCH] OvmfPkg: split the variable store to a separate file List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: edk2-devel@lists.sourceforge.net Cc: Laszlo Ersek , qemu-devel@nongnu.org, crobinso@redhat.com Il 22/11/2013 12:46, Laszlo Ersek ha scritto: >> Also, I see a command line compatibility problem, especially if one >> > wants OVMF.fd to become the default firmware. > I don't understand. If you use the un-split build, you use the original > command line (single -pflash or -drive if=pflash option). > > If you use the split build, then you: > - extend the first -drive if=pflash option with ",readonly" -- this is > optional but recommended, > - you add a second option after the first, pointing it to NVVARSTORE.fd > (ie. its VM-specific, private copy). Suppose OVMF.fd is already the default. To add a non-volatile store, you would have to do one of the following: * -pflash /path/to/OVMF.fd -pflash NVVARSTORE.fd Or alternatively, pc and q35 could use the current semantics forever. UEFI-by-default will be tied to a separate machine type (pc-uefi, or q35-uefi, or a different chipset) where -bios will also create a cfi_pflash01 device and all pflash drives will be mapped below the BIOS's. So you would have one of the following: * -M pc -pflash /path/to/OVMF.fd -pflash NVVARSTORE.fd * -M pc-uefi -pflash NVVARSTORE.fd > You don't specify OVMF.fd twice. I meant the first time is inside QEMU, the second is on the command line. > I think I don't fully understand your point. I probably didn't express it well, also because I have no real idea to offer (I don't like the "-M pc-uefi" either). Paolo