docs/interop/nbd.rst

5 ``block/nbd.c``), an internal NBD server (see ``blockdev-nbd.c``), and an
6 external NBD server tool (see ``qemu-nbd.c``). The common code is placed
16 -------------------
23 ------------------
30     qemu:dirty-bitmap:<dirty-bitmap-export-name>
32 Each dirty-bitmap metadata context defines only one flag for extents
41     qemu:allocation-depth
43 In the allocation depth context, the entire 32-bit value represents a
44 depth of which layer in a thin-provisioned backing chain provided the
45 data (0 for unallocated, 1 for the active layer, 2 for the first
46 backing layer, and so forth).
49 in addition to the specific ``qemu:allocation-depth`` and
50 ``qemu:dirty-bitmap:<dirty-bitmap-export-name>``:
54 ``qemu:dirty-bitmap:``
55   returns list of all available dirty-bitmap metadata contexts
58 -------------------
63 easier to plan for cross-version interoperability.  Note that in
79   ``NBD_OPT_STARTTLS`` with TLS Pre-Shared Keys (PSK),
80   ``NBD_CMD_BLOCK_STATUS`` for ``qemu:dirty-bitmap:``, ``NBD_CMD_CACHE``
82   ``NBD_FLAG_CAN_MULTI_CONN`` for shareable read-only exports,
85   ``NBD_CMD_BLOCK_STATUS`` for ``qemu:allocation-depth``