Lines Matching full:the

4 QEMU supports the NBD protocol, and has an internal NBD client (see
6 external NBD server tool (see ``qemu-nbd.c``). The common code is placed
9 The NBD protocol is specified here:
12 The following paragraphs describe some specific properties of NBD
18 QEMU supports the ``base:allocation`` metadata context as defined in the
25 The ``qemu`` namespace currently contains two available metadata context
26 types.  The first is related to exposing the contents of a dirty
27 bitmap alongside the associated disk contents.  That metadata context
28 is named with the following form::
36   ``NBD_STATE_DIRTY``, set when the extent is "dirty"
38 The second is related to exposing the source of various extents within
39 the image, with a single metadata context named::
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
48 For ``NBD_OPT_LIST_META_CONTEXT`` the following queries are supported
49 in addition to the specific ``qemu:allocation-depth`` and
53   returns list of all available metadata contexts in the namespace
60 The following list documents which qemu version first implemented
61 various features (both as a server exposing the feature, and as a
62 client taking advantage of the feature when present), to make it
64 several cases, the initial release containing a feature may require
65 additional patches from the corresponding stable branch to fix bugs in
66 the operation of that feature.