All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow3 - arbitrary metadata
Date: Mon, 28 Jul 2008 16:39:46 -0500	[thread overview]
Message-ID: <488E3CA2.2000502@codemonkey.ws> (raw)
In-Reply-To: <a38baa500807281419y280edce0gf16fe9984176fc7a@mail.gmail.com>

Nathaniel McCallum wrote:
> On Mon, Jul 28, 2008 at 5:17 PM, Anthony Liguori 
> <anthony@codemonkey.ws <mailto:anthony@codemonkey.ws>> wrote:
>
>     Nathaniel McCallum wrote:
>
>         On Mon, Jul 28, 2008 at 4:50 PM, Anthony Liguori
>         <anthony@codemonkey.ws <mailto:anthony@codemonkey.ws>
>         <mailto:anthony@codemonkey.ws <mailto:anthony@codemonkey.ws>>>
>         wrote:
>
>            Something that would be pretty interesting, but also terribly
>            hacky, would be to have an option that would allow one to use a
>            disk with an offset.  For instance:
>
>            qemu-system-x86_64 -drive file=foo.img,offset=4096,if=ide
>
>
>         I assume this technique is more "mergable"
>
>
>     Than forking the qcow format?  Definitely, although I'm not
>     convinced there isn't a better way to do it that is even less hacky.
>
>
> I'd love to know what that other option could be.   Adding an offset 
> option is going to touch a lot of files...

Actually, it wouldn't.  You just need to modify the RAW block driver to 
add an offset to any of the operations that would seek within the file.  
There's no clear way to pass individual arguments to a particular block 
format though so that would make it somewhat hairy.

Regards,

Anthony Liguori

  reply	other threads:[~2008-07-28 21:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 19:56 [Qemu-devel] [PATCH] qcow3 - arbitrary metadata Nathaniel McCallum
2008-07-28 20:08 ` Anthony Liguori
2008-07-28 20:24   ` Nathaniel McCallum
2008-07-28 20:36     ` Paul Brook
2008-07-28 20:52       ` Anthony Liguori
2008-07-28 20:50     ` Anthony Liguori
2008-07-28 21:12       ` Nathaniel McCallum
2008-07-28 21:17         ` Anthony Liguori
2008-07-28 21:19           ` Nathaniel McCallum
2008-07-28 21:39             ` Anthony Liguori [this message]
2008-07-29  1:49   ` Jamie Lokier
2008-07-29  2:11     ` Jorge Lucángeli Obes
2008-07-29  2:48       ` Nathaniel McCallum
2008-07-29  3:05         ` Jorge Lucángeli Obes
2008-07-29  3:13     ` Anthony Liguori
2008-07-29  6:44       ` Jamie Lokier
2008-07-29 13:38         ` Anthony Liguori
2008-07-29 16:05           ` Jamie Lokier
2008-07-29  8:48     ` Daniel P. Berrange
2008-07-28 23:04 ` Laurent Vivier
2008-07-29  1:25   ` Nathaniel McCallum
2008-07-29  3:06     ` Anthony Liguori
2008-07-29  3:22       ` Nathaniel McCallum
2008-07-29  6:40         ` maht
2008-07-29  6:44           ` maht
2008-07-29  7:48     ` Laurent Vivier

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=488E3CA2.2000502@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.