16.01.2018 00:26, John Snow wrote:
On 01/11/2018 10:15 AM, Vladimir Sementsov-Ogievskiy wrote:
11.01.2018 17:43, Eric Blake wrote:
On 01/11/2018 08:26 AM, Vladimir Sementsov-Ogievskiy wrote:
# @autoload: the bitmap will be automatically loaded when the image it
is stored
# in is
On 01/11/2018 10:15 AM, Vladimir Sementsov-Ogievskiy wrote:
> 11.01.2018 17:43, Eric Blake wrote:
>> On 01/11/2018 08:26 AM, Vladimir Sementsov-Ogievskiy wrote:
>>
>>> # @autoload: the bitmap will be automatically loaded when the image it
>>> is stored
>>> # in is opened. This flag
11.01.2018 17:43, Eric Blake wrote:
On 01/11/2018 08:26 AM, Vladimir Sementsov-Ogievskiy wrote:
# @autoload: the bitmap will be automatically loaded when the image it
is stored
# in is opened. This flag may only be specified for persistent
# bitmaps. Default is false for
On 01/11/2018 08:26 AM, Vladimir Sementsov-Ogievskiy wrote:
> # @autoload: the bitmap will be automatically loaded when the image it
> is stored
> # in is opened. This flag may only be specified for persistent
> # bitmaps. Default is false for block-dirty-bitmap-add.
>
Hi all!
I've just noted that there is an unfortunate contradiction between qcow2
spec and qapi.
In qcow2 we have:
1: auto
The bitmap must reflect all changes of the virtual
disk by any application that would write to this qcow2
file (including writes, snapshot switching, etc.). The
type
