docs/interop/bitmaps.rst

22 administer QEMU directly via QMP.
96   length limited. (QMP protocol may restrict messages to less than 64MiB.)
113 Dirty Bitmap objects can be queried with the QMP command `query-block
114 <qemu-qmp-ref.html#index-query_002dblock>`_, and are visible via the
115 `BlockDirtyInfo <qemu-qmp-ref.html#index-BlockDirtyInfo>`_ QAPI structure.
134 <qemu-qmp-ref.html#index-DirtyBitmapStatus>`_. A bitmap historically had
165 Basic QMP Usage
168 The primary interface to manipulating bitmap objects is via the QMP
169 interface. If you are not familiar, see the :doc:`qmp-spec` for the
170 protocol, and :doc:`qemu-qmp-ref` for a full reference of all QMP
193 <qemu-qmp-ref.html#index-block_002ddirty_002dbitmap_002dadd>`_:
202  .. code-block:: QMP
223  .. code-block:: QMP
240 <qemu-qmp-ref.html#index-block_002ddirty_002dbitmap_002dremove>`_:
257  .. code-block:: QMP
272 <qemu-qmp-ref.html#index-block_002ddirty_002dbitmap_002dclear>`_:
283  .. code-block:: QMP
298 <qemu-qmp-ref.html#index-block_002ddirty_002dbitmap_002denable>`_:
312  .. code-block:: QMP
327 <qemu-qmp-ref.html#index-block_002ddirty_002dbitmap_002ddisable>`_:
350  .. code-block:: QMP
365 <qemu-qmp-ref.html#index-block_002ddirty_002dbitmap_002dmerge>`_:
396  .. code-block:: QMP
412 <qemu-qmp-ref.html#index-query_002dblock>`_:
427  .. code-block:: QMP
473 Transactions are a QMP feature that allows you to submit multiple QMP commands
477 See `transaction <qemu-qmp.ref.html#index-transaction>`_ in the QMP reference
485 it's easy to ensure that no guest writes occur between individual QMP
487 individual QMP commands that may allow guest writes to occur between each
490 For example, using only individual QMP commands, we could:
531 The usages for these commands are identical to their respective QMP commands,
543 <qemu-qmp-ref.html#index-blockdev_002dbackup>`_ QMP command to create both
546 The command is a background job, which has its own QMP API for querying and
548 <qemu-qmp-ref.html#Background-jobs>`_.
560 <qemu-qmp-ref.html#index-blockdev_002dadd>`_ or `blockdev-create
561 <qemu-qmp-ref.html#index-blockdev_002dcreate>`_ command.
568 .. code-block:: QMP
655 .. code-block:: QMP
712    - Using QMP commands with the VM paused as in the `Justification`_ section,
734    .. code-block:: QMP
752    .. code-block:: QMP
807    .. code-block:: QMP
826    .. code-block:: QMP
904    .. code-block:: QMP
923    .. code-block:: QMP
984    .. code-block:: QMP
1016    .. code-block:: QMP
1100    .. code-block:: QMP
1132    .. code-block:: QMP
1196 launched, either by an individual QMP command or a QMP transaction, the user
1231    .. code-block:: QMP
1247 #. Attempt to create an incremental backup via QMP:
1249    .. code-block:: QMP
1265    .. code-block:: QMP
1292    .. code-block:: QMP
1313    .. code-block:: QMP
1332    .. code-block:: QMP
1348    .. code-block:: QMP
1365 QMP commands like `blockdev-backup
1366 <qemu-qmp-ref.html#index-blockdev_002dbackup>`_
1389    .. code-block:: QMP
1419    .. code-block:: QMP
1425    .. code-block:: QMP
1441    .. code-block:: QMP
1496 it's possible to instruct them to complete or fail together as a group. QMP
1517    .. code-block:: QMP
1549    .. code-block:: QMP
1555    .. code-block:: QMP
1582    .. code-block:: QMP