Lines Matching refs:cluster
6 (host) clusters. A cluster is the unit in which all allocations are done,
17 The first cluster of a qcow2 image contains the file header::
40 within a cluster (1 << cluster_bits is the cluster size).
44 as the maximum cluster size and won't be able to open images
45 with larger cluster sizes.
54 the maximum L1 table size. With a 2 MB cluster
55 size, it is unable to populate a virtual cluster
56 beyond 2 EB (61 bits); with a 512 byte cluster
74 starts. Must be aligned to a cluster boundary.
78 starts. Must be aligned to a cluster boundary.
88 starts. Must be aligned to a cluster boundary.
277 the first cluster. It is not allowed to store other data here, so that an
345 starts. Must be aligned to a cluster boundary.
360 header starts in bytes. Must be aligned to a cluster
365 to the nearest multiple of the cluster size. Any
382 qcow2 cluster aligned. Its value is currently never used in the
417 | QCow2 cluster payload |
453 Host cluster management
457 for each host cluster. A refcount of 0 means that the cluster is free, 1 means
467 blocks and are exactly one cluster in size.
476 table size. With a 2 MB cluster size and a default refcount_order of
478 the worst case, with a 512 cluster size and refcount_order of 6, it is
481 Given an offset into the image file, the refcount of its cluster can be
497 refcount block starts. Must be aligned to a cluster
506 Bit 0 - x: Reference count of the cluster. If refcount_bits implies a
519 exactly one cluster in size.
522 size; for a given L1 table size, a larger cluster size is required for
524 cluster must currently map to a host offset below 64 PB (56 bits)
526 use). Additionally, as cluster size increases, the maximum host
527 offset for a compressed cluster is reduced (a 2M cluster size requires
551 table starts. Must be aligned to a cluster boundary. If the
575 mapping for guest cluster offsets), so this bit should be 1
580 Bit 0: If set to 1, the cluster reads as all zeros. The host
581 cluster offset can be used to describe a preallocation,
582 but it won't be used for reading data from this cluster,
583 nor is data read from the backing file if the cluster is
591 9 - 55: Bits 9-55 of host cluster offset. Must be aligned to a
592 cluster boundary. If the offset is 0 and bit 63 is clear,
593 the cluster is unallocated. The offset may only be 0 with
594 bit 63 set (indicating a host cluster offset of 0) when an
602 Bit 0 - x-1: Host cluster offset. This is usually _not_ aligned to a
603 cluster or sector boundary! If cluster_bits is
610 in the next contiguous host cluster.
614 stops when it has produced a cluster of data.
616 Another compressed cluster may map to the tail of the final
617 sector used by this compressed cluster.
619 If a cluster is unallocated, read requests shall read the data from the backing
631 same size. They are contiguous and start from the beginning of the cluster.
644 in the previous section, with the exception of bit 0 of the standard cluster
654 host cluster offset field must contain a valid
667 cluster offset field may or may not be set.
702 snapshot starts. Must be aligned to a cluster boundary.
720 If there is VM state, it starts at the first cluster
722 regular guest cluster (i.e. VM state is stored like guest
788 a cluster boundary.
884 9 - 55: Bits 9 - 55 of the host cluster offset. Must be aligned to
885 a cluster boundary. If the offset is 0, the cluster is
887 cluster should be treated during reads.
914 If the size of the bitmap data is not a multiple of the cluster size then the
915 last cluster of the bitmap data contains some unused tail bits. These bits must