From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1ILRjA-0007nJ-RJ
	for qemu-devel@nongnu.org; Wed, 15 Aug 2007 18:52:37 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1ILRj9-0007lb-6Q
	for qemu-devel@nongnu.org; Wed, 15 Aug 2007 18:52:36 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1ILRj8-0007lN-So
	for qemu-devel@nongnu.org; Wed, 15 Aug 2007 18:52:34 -0400
Received: from rv-out-0910.google.com ([209.85.198.190])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <t4m5yn@gmail.com>) id 1ILRj8-0008HC-H0
	for qemu-devel@nongnu.org; Wed, 15 Aug 2007 18:52:34 -0400
Received: by rv-out-0910.google.com with SMTP id g11so27804rvb
	for <qemu-devel@nongnu.org>; Wed, 15 Aug 2007 15:52:32 -0700 (PDT)
Message-ID: <59abf66e0708151552r6192f7e1he7ebe5bffd49525f@mail.gmail.com>
Date: Wed, 15 Aug 2007 19:52:32 -0300
From: "=?ISO-8859-1?Q?Jorge_Luc=E1ngeli_Obes?=" <t4m5yn@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: [Qemu-devel] Making qemu images executable (and store command line
	arguments in them =P)
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: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org

I've been giving some thought to Anthony's idea:

http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage

However, maybe I'm just too much on vacations, but I don't seem to
come up with a nice way of doing this. Everything keeps coming back to
creating a new 'container' image format and then implementing block
layer functions that only add the number of sectors occupied by the
command-line to the read and write calls made by QEMU, and then just
relay those calls to the image-specific functions. That doesn't sound
very efficient.

The '#!' trick works nice with scripts, but I don't see it playing
very well with images. =BFComments? =BFPointers?

Cheers,
Jorge