From 7dc570b3806e5b0a4c9219061556ed5a4a0de80c Mon Sep 17 00:00:00 2001 From: Eric Blake Date: Fri, 11 Jan 2019 13:47:18 -0600 Subject: nbd: Remove x-nbd-server-add-bitmap Now that nbd-server-add can do the same functionality (well, other than making the exported bitmap name different than the underlying bitamp - but we argued that was not essential, since it is just as easy to create a new non-persistent bitmap with the desired name), we no longer need the experimental separate command. Signed-off-by: Eric Blake Reviewed-by: Vladimir Sementsov-Ogievskiy Message-Id: <20190111194720.15671-7-eblake@redhat.com> --- qapi/block.json | 23 ----------------------- 1 file changed, 23 deletions(-) (limited to 'qapi') diff --git a/qapi/block.json b/qapi/block.json index 3d70420..5a79d63 100644 --- a/qapi/block.json +++ b/qapi/block.json @@ -302,29 +302,6 @@ 'data': {'name': 'str', '*mode': 'NbdServerRemoveMode'} } ## -# @x-nbd-server-add-bitmap: -# -# Expose a dirty bitmap associated with the selected export. The bitmap search -# starts at the device attached to the export, and includes all backing files. -# The exported bitmap is then locked until the NBD export is removed. -# -# @name: Export name. -# -# @bitmap: Bitmap name to search for. -# -# @bitmap-export-name: How the bitmap will be seen by nbd clients -# (default @bitmap) -# -# Note: the client must use NBD_OPT_SET_META_CONTEXT with a query of -# "qemu:dirty-bitmap:NAME" (where NAME matches @bitmap-export-name) to access -# the exposed bitmap. -# -# Since: 3.0 -## - { 'command': 'x-nbd-server-add-bitmap', - 'data': {'name': 'str', 'bitmap': 'str', '*bitmap-export-name': 'str'} } - -## # @nbd-server-stop: # # Stop QEMU's embedded NBD server, and unregister all devices previously -- cgit v1.1