From: Eric Blake <eblake@redhat.com>
To: 吴兴博 <wuxb45@gmail.com>, "Kirill Batuzov" <batuzovk@ispras.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] disk image: self-organized format or raw file
Date: Tue, 12 Aug 2014 08:07:55 -0600 [thread overview]
Message-ID: <53EA1FBB.2000909@redhat.com> (raw)
In-Reply-To: <CABPa+v0L84CDmj0C3btzjnDGmVCLoNW3Z2Bz5z6mBf-DGQyhAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
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.
> would be suffice to distinguish between present or in backing file.
> The idea in FVD looks similar to 'addcow'---use bitmap but delegating
> allocation to FS. However FVD seems to have been ignored by community.
Care to give a pointer to a URL describing the FVD format?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-08-12 14:08 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 [this message]
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
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=53EA1FBB.2000909@redhat.com \
--to=eblake@redhat.com \
--cc=batuzovk@ispras.ru \
--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 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.