diff options
author | John Snow <jsnow@redhat.com> | 2019-10-02 19:24:11 -0400 |
---|---|---|
committer | John Snow <jsnow@redhat.com> | 2019-10-17 17:53:28 -0400 |
commit | 3264ffced3d087bbe72d759639ef84fd5bd924cc (patch) | |
tree | 38e0dbe3b7156f596ae08f24f73daadc4bb1be66 /qapi/block-core.json | |
parent | 4a189fdfafe388f05cd7f5b58e2654b7cfd6dfb0 (diff) |
dirty-bitmaps: remove deprecated autoload parameter
This parameter has been deprecated since 2.12.0 and is eligible for
removal. Remove this parameter as it is actually completely ignored;
let's not give false hope.
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-id: 20191002232411.29968-1-jsnow@redhat.com
Diffstat (limited to 'qapi/block-core.json')
-rw-r--r-- | qapi/block-core.json | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/qapi/block-core.json b/qapi/block-core.json index f66553aac7..b274aef713 100644 --- a/qapi/block-core.json +++ b/qapi/block-core.json @@ -2052,10 +2052,6 @@ # Qcow2 disks support persistent bitmaps. Default is false for # block-dirty-bitmap-add. (Since: 2.10) # -# @autoload: ignored and deprecated since 2.12. -# Currently, all dirty tracking bitmaps are loaded from Qcow2 on -# open. -# # @disabled: the bitmap is created in the disabled state, which means that # it will not track drive changes. The bitmap may be enabled with # block-dirty-bitmap-enable. Default is false. (Since: 4.0) @@ -2064,7 +2060,7 @@ ## { 'struct': 'BlockDirtyBitmapAdd', 'data': { 'node': 'str', 'name': 'str', '*granularity': 'uint32', - '*persistent': 'bool', '*autoload': 'bool', '*disabled': 'bool' } } + '*persistent': 'bool', '*disabled': 'bool' } } ## # @BlockDirtyBitmapMergeSource: |