From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47904) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fR2Jw-0001mv-Sf for qemu-devel@nongnu.org; Thu, 07 Jun 2018 17:19:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fR2Jv-00005H-Rl for qemu-devel@nongnu.org; Thu, 07 Jun 2018 17:19:48 -0400 Date: Fri, 8 Jun 2018 00:19:40 +0300 From: "Michael S. Tsirkin" Message-ID: <20180608001843-mutt-send-email-mst@kernel.org> References: <61a301dd-8e50-8799-8328-341d6ab744f5@redhat.com> <20180606143134.GG2660@work-vm> <39bcee27-329a-61d8-47fa-678b431b0a79@redhat.com> <20180606150507.GJ2660@work-vm> <66727986-1cf1-c12e-d78c-d56cc15eaf00@redhat.com> <20180606163246.GL3064@redhat.com> <20180607103218.GC1455@redhat.com> <20180607103620.GJ28827@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] storing machine data in qcow images? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrea Bolognani Cc: Daniel =?iso-8859-1?Q?P=2E_Berrang=E9?= , "Richard W.M. Jones" , Eric Blake , Kevin Wolf , qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com, "Dr. David Alan Gilbert" , stefanha@redhat.com, Max Reitz On Thu, Jun 07, 2018 at 12:54:33PM +0200, Andrea Bolognani wrote: > On Thu, 2018-06-07 at 11:36 +0100, Daniel P. Berrang=E9 wrote: > > On Thu, Jun 07, 2018 at 11:32:18AM +0100, Richard W.M. Jones wrote: > > > Another problem which Laszlo mentioned is the varstore isn't portab= le > > > between UEFI implementations, or if the UEFI is compiled with > > > different options. You can even imagine shipping multiple > > > varstores(!) which argues for a tar-like format. > >=20 > > Could we perhaps imagine shipping the actual UEFI bios, rather > > than only the varstore. The bios blob runs in guest context, > > so there shouldn't be able security concerns from hosting > > vendors with running user provided bios. Mostly its a matter > > of confidence that the interface between bios & qemu is stable > > which feels easier than assuming varstore vs different bios is > > portable. >=20 > That sounds sensible, and further reinforces the idea that we > need way more than a single string baked into the qcow2 file. I don't think anyone said we want a single string. What was proposed is a set of key value pairs with values being binary blobs. > --=20 > Andrea Bolognani / Red Hat / Virtualization