From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KNeLU-0002hU-5a
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 21:49:48 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KNeLR-0002hI-RF
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 21:49:46 -0400
Received: from [199.232.76.173] (port=38050 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KNeLR-0002hF-Lb
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 21:49:45 -0400
Received: from mail2.shareable.org ([80.68.89.115]:34394)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1KNeLR-0006CX-71
	for qemu-devel@nongnu.org; Mon, 28 Jul 2008 21:49:45 -0400
Received: from jamie by mail2.shareable.org with local (Exim 4.63)
	(envelope-from <jamie@shareable.org>) id 1KNeLM-00078W-Ak
	for qemu-devel@nongnu.org; Tue, 29 Jul 2008 02:49:40 +0100
Date: Tue, 29 Jul 2008 02:49:40 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [PATCH] qcow3 - arbitrary metadata
Message-ID: <20080729014939.GA27149@shareable.org>
References: <a38baa500807281256s7aa6c69em344c655145956b24@mail.gmail.com>
	<488E2752.7030008@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <488E2752.7030008@codemonkey.ws>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Anthony Liguori wrote:
> Can you provide more information about what the metadata is used for and 
> why it's so important for the metadata to be in the image verses in a 
> separate file?

Yeah, I have the opposite problem - too much in the same file :-)

I want to be able to savevm, but some of my VMs don't have any qcow2
images (because I don't trust them for mission-critical VMs since
recent discussion, or because they are floppy-only or CD-only VMs with
no hard disk).

To enable savevm, at least according to docs, I have to have a qcow2
image somewhere.  So I add a redundant minimum-size unpartitioned
qcow2 hard disk and hope nobody minds...

That seems a bit hackish.  It would be nice if savevm could just write
to a named file and loadvm could read it.

-- Jamie