From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54909) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQZhX-0004A1-2l for qemu-devel@nongnu.org; Wed, 06 Jun 2018 10:46:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fQZhW-0000fJ-CR for qemu-devel@nongnu.org; Wed, 06 Jun 2018 10:46:15 -0400 Date: Wed, 6 Jun 2018 17:46:05 +0300 From: "Michael S. Tsirkin" Message-ID: <20180606174412-mutt-send-email-mst@kernel.org> References: <20180528212054.GH2209@redhat.com> <20180528212510.GC4660@redhat.com> <20180529064415.GA4756@localhost.localdomain> <2b3eef00-f326-c1e6-0e4b-b7602646eec4@redhat.com> <20180606123237.2235ae4a@kitsune.suse.cz> <20180606131929.44d0fd6b@kitsune.suse.cz> <93233bff-604b-c891-90ce-64fe1eaaaab5@redhat.com> <20180606113720.GA2661@work-vm> <2c833e2c-f0bb-ea98-a703-54fb9447bd2f@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2c833e2c-f0bb-ea98-a703-54fb9447bd2f@redhat.com> Subject: Re: [Qemu-devel] storing machine data in qcow images? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: "Dr. David Alan Gilbert" , Michal =?iso-8859-1?Q?Such=E1nek?= , Kevin Wolf , ehabkost@redhat.com, qemu-block@nongnu.org, "Richard W.M. Jones" , qemu-devel@nongnu.org, stefanha@redhat.com On Wed, Jun 06, 2018 at 01:44:02PM +0200, Max Reitz wrote: > Because it's a hack, right. Storing binary data in a qcow2 file, > completely ignoring it in qemu (and being completely unusable to any > potential other users of the qcow2 format[1]) and only interpreting it > somewhere up the stack is a hack. It's just a first step and it ensures compatibility with old QEMU versions. But down the road I think we will start warning user if the machine type does not match, and possibly even get the type from there if user didn't supply it. -- MST