Lines Matching full:an

39                     Number of bits that are used for addressing an offset
43 Note: QEMU as of today has an implementation limit of 2 MB
53 Note: QEMU has an implementation limit of 32 MB as
59 table layouts limit an image to no more than 64 PB
60 (56 bits) of populated clusters, and an image may
96 Bitmask of incompatible features. An implementation must
97 fail to open an image if an unknown bit is set.
109 Bit 2: External data file bit. If this bit is set, an
118 An External Data File Name header extension may
127 L2 table entries use an extended format that
134 Bitmask of compatible features. An implementation can
145 Bitmask of auto-clear features. An implementation may only
146 write to an image with unknown auto-clear features if it
153 It is an error if this bit is set without the
203 2. If there are no unrecognized incompatible feature bits set, an unknown
209 3. An explicit value of 0 will have the same behavior as when the field is not
221 All compressed clusters in an image use the same compression
277 the first cluster. It is not allowed to store other data here, so that an
297 The feature name table is an optional header extension that contains the name
320 The bitmaps extension is an optional header extension. It provides the ability
427 When an encryption method is requested in the header, the image payload
475 QEMU has an implementation limit of 8 MB as the maximum refcount
481 Given an offset into the image file, the refcount of its cluster can be
529 cannot be relaxed without an incompatible layout change).
531 Given an offset into the virtual disk, the offset into the image file can be
557 63: 0 for an L2 table that is unused or requires COW, 1 if its
573 With external data files, all guest clusters have an
594 bit 63 set (indicating a host cluster offset of 0) when an
627 An image uses Extended L2 Entries if bit 4 is set on the incompatible_features
636 The size of an extended L2 entry is 128 bits so the number of entries per table
896 bitmap table. Given an offset (in bytes) into the bitmap data, the offset into
906 Given an offset byte_nr into the virtual disk and the bitmap's granularity, the
928 bitmap was ``enabled``. An unset bit means that this range was not written to.