From: "Richard W.M. Jones" <rjones@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: 吴兴博 <wuxb45@gmail.com>,
qemu-devel@nongnu.org, "Kirill Batuzov" <batuzovk@ispras.ru>
Subject: Re: [Qemu-devel] disk image: self-organized format or raw file
Date: Tue, 12 Aug 2014 19:39:22 +0100 [thread overview]
Message-ID: <20140812183921.GG14001@redhat.com> (raw)
In-Reply-To: <53EA1FBB.2000909@redhat.com>
On Tue, Aug 12, 2014 at 08:07:55AM -0600, Eric Blake wrote:
> On 08/12/2014 07:45 AM, 吴兴博 wrote:
>
> [please don't top-post on technical lists]
>
> > Thanks for your information. It's really helpful.
> > I think adding a bitmap alongside the raw file ( or just within that file)
>
> Umm, how do you propose to add a bitmap within a raw file? The moment
> the file contains metadata, it is no longer raw, but some other format.
> You'd need a way to reliably delineate the portion of the file that
> contains the bitmap and therefore must not be exposed to the guest.
There was an MSFT format where they used raw but added metadata after
the end of the raw file data.
https://en.wikipedia.org/wiki/VHD_%28file_format%29
This is crazy BTW - I'm not advocating we do it :-)
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
next prev parent reply other threads:[~2014-08-12 18:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 23:38 [Qemu-devel] disk image: self-organized format or raw file 吴兴博
2014-08-12 0:52 ` Fam Zheng
2014-08-12 10:46 ` 吴兴博
2014-08-12 11:19 ` Fam Zheng
[not found] ` <CABPa+v1a7meoEtjLkwygjuZEABTqd8q3efGWJvAsAr-mLTQb-A@mail.gmail.com>
[not found] ` <20140812113916.GB2803@T430.redhat.com>
2014-08-12 12:03 ` 吴兴博
2014-08-12 12:21 ` Fam Zheng
2014-08-12 13:08 ` Kirill Batuzov
2014-08-12 13:23 ` Eric Blake
2014-08-12 13:45 ` 吴兴博
2014-08-12 14:07 ` Eric Blake
2014-08-12 14:14 ` 吴兴博
2014-08-12 15:30 ` Eric Blake
2014-08-12 16:22 ` Xingbo Wu
2014-08-13 1:29 ` Fam Zheng
2014-08-13 15:42 ` Kevin Wolf
2014-08-12 18:39 ` Richard W.M. Jones [this message]
2014-08-12 18:46 ` Daniel P. Berrange
2014-08-12 18:52 ` Richard W.M. Jones
2014-08-12 19:23 ` Xingbo Wu
2014-08-12 20:14 ` Richard W.M. Jones
2014-08-13 15:54 ` Kevin Wolf
2014-08-13 16:38 ` Xingbo Wu
2014-08-13 18:32 ` Kevin Wolf
2014-08-13 21:04 ` Xingbo Wu
2014-08-13 21:35 ` Eric Blake
2014-08-14 2:42 ` Xingbo Wu
2014-08-14 9:06 ` Kevin Wolf
2014-08-14 20:53 ` Xingbo Wu
2014-08-15 10:46 ` Kevin Wolf
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=20140812183921.GG14001@redhat.com \
--to=rjones@redhat.com \
--cc=batuzovk@ispras.ru \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wuxb45@gmail.com \
/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).