From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
den@openvz.org, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v10] spec: add qcow2 bitmaps extension specification
Date: Sat, 13 Feb 2016 09:12:40 +0300 [thread overview]
Message-ID: <56BEC958.8090407@virtuozzo.com> (raw)
In-Reply-To: <20160212144916.GF4828@noname.redhat.com>
On 12.02.2016 17:49, Kevin Wolf wrote:
> Am 05.02.2016 um 09:58 hat Vladimir Sementsov-Ogievskiy geschrieben:
>> The new feature for qcow2: storing bitmaps.
>>
>> This patch adds new header extension to qcow2 - Bitmaps Extension. It
>> provides an ability to store virtual disk related bitmaps in a qcow2
>> image. For now there is only one type of such bitmaps: Dirty Tracking
>> Bitmap, which just tracks virtual disk changes from some moment.
>>
>> Note: Only bitmaps, relative to the virtual disk, stored in qcow2 file,
>> should be stored in this qcow2 file. The size of each bitmap
>> (considering its granularity) is equal to virtual disk size.
>>
>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Thanks, applied to the block branch.
>
> Kevin
Cheers! Thank you! Thanks to everyone, who spent time on reviewing and
discussing!
--
Best regards,
Vladimir
prev parent reply other threads:[~2016-02-13 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 8:58 [Qemu-devel] [PATCH v10] spec: add qcow2 bitmaps extension specification Vladimir Sementsov-Ogievskiy
2016-02-06 14:24 ` Max Reitz
2016-02-08 23:10 ` John Snow
2016-02-12 6:45 ` Denis V. Lunev
2016-02-12 13:12 ` Fam Zheng
2016-02-12 14:49 ` Kevin Wolf
2016-02-13 6:12 ` Vladimir Sementsov-Ogievskiy [this message]
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=56BEC958.8090407@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).