From: "Carlos A. M. dos Santos" <unixmania@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4][RFC] Add logic to QEMU to read command line options from qcow2 images
Date: Fri, 10 Aug 2007 10:26:15 -0300 [thread overview]
Message-ID: <e71790db0708100626g23f91329m3171c4e8b4b59db9@mail.gmail.com> (raw)
In-Reply-To: <46BBE0B5.8050303@filteredperception.org>
On 8/10/07, dmc <dmc@filteredperception.org> wrote:
> Brian Wheeler wrote:
> > On Thu, 2007-08-09 at 15:32 -0500, Anthony Liguori wrote:
> >> Avi Kivity wrote:
> >>> Anthony Liguori wrote:
> >>>> If you're looking for a low-end solution, another possibility would
> >>>> be having a "new" file format which consisted of:
> >>>>
> >>>> #!/path/to/qemu [<args> ...] <nl>
> >>>> <standard disk image>
> >>>>
> >>>> And then make the appropriate changes to QEMU such that it can skip
> >>>> the first line in a disk image file. This has a few nice side
> >>>> effects. The disk image is directly executable and it makes it very
> >>>> clear to the user that they have to trust the disk image. The other
> >>>> nice thing is that it would work with file formats other than qcow2.
> >>> Well, it would be nice to align the disk image to a sector boundary
> >>> (or, better, a page boundary). But yes, a very good idea.
> >> That has the very nice side effect of allowing you to edit the command
> >> line with a text editor provided you don't cross the sector boundary.
> >> Filling with spaces would be pretty nice.
> >>
> >
> >
> > Its a bad idea. Either have a line terminated file, or a pure binary
> > file, but don't mix them. Besides firing up an editor to modify it
> > being a royal pain, mystery breakages will occur when someone has their
> > editor set to "insert mode" (which is the default) vs "overwrite mode"
> > and doesn't notice those extra spaces moving beyond the 512-byte mark.
>
> how about xml appended to image file, and size of xml appended to that?
> And a tool to easily extract/replace the xml. Just my $0.02...
Keep it *simple*, please!
--
Carlos A. M. dos Santos
next prev parent reply other threads:[~2007-08-10 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59abf66e0708081124g14901b01i841b70d17ae1e097@mail.gmail.com>
2007-08-08 19:52 ` [Qemu-devel] [PATCH 4/4][RFC] Add logic to QEMU to read command line options from qcow2 images Jorge Lucángeli Obes
2007-08-08 20:24 ` Daniel P. Berrange
2007-08-09 14:54 ` Anthony Liguori
2007-08-09 15:07 ` Daniel P. Berrange
2007-08-09 20:16 ` Avi Kivity
2007-08-09 20:25 ` Anthony Liguori
2007-08-09 20:30 ` Avi Kivity
2007-08-09 20:32 ` Anthony Liguori
2007-08-09 20:39 ` Avi Kivity
2007-08-09 20:44 ` Brian Wheeler
2007-08-09 20:49 ` Anthony Liguori
2007-08-10 3:51 ` dmc
2007-08-10 13:26 ` Carlos A. M. dos Santos [this message]
2007-08-09 20:55 ` Brian Wheeler
2007-08-10 0:48 ` Anthony Liguori
2007-08-11 17:11 ` andrzej zaborowski
2007-08-11 18:06 ` Philip Boulain
2007-08-11 19:08 ` Christian Brunschen
2007-08-11 19:53 ` Anthony Liguori
2007-08-11 19:52 ` Anthony Liguori
2007-08-11 21:28 ` Philip Boulain
2007-08-11 23:17 ` Anthony Liguori
2007-08-13 5:34 ` Jorge Lucángeli Obes
2007-08-13 15:15 ` [kvm-devel] " Anthony Liguori
2007-08-11 19:49 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e71790db0708100626g23f91329m3171c4e8b4b59db9@mail.gmail.com \
--to=unixmania@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).