mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-22 19:32:19 +00:00
kbase: incrementalbackupinternals: Add snapshot terminology
Make it obvious what's meant by 'overlay' and 'backing image' for sake of extension of the document. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
parent
8c6dba054b
commit
19061038a7
@ -94,6 +94,21 @@ so, even if we obviously can't guarantee that.
|
|||||||
Integration with external snapshots
|
Integration with external snapshots
|
||||||
===================================
|
===================================
|
||||||
|
|
||||||
|
External snapshot terminology
|
||||||
|
-----------------------------
|
||||||
|
|
||||||
|
External snapshots on a disk level consist of layered chains of disk images. An
|
||||||
|
image in the chain can have a ``backing image`` placed below. Any chunk in the
|
||||||
|
current image which was not written explicitly is transparent and if read the
|
||||||
|
data from the backing image is passed through. An image placed on top of the
|
||||||
|
current image is called ``overlay``.
|
||||||
|
|
||||||
|
The bottommost backing image at the end of the chain is also usually described
|
||||||
|
as ``base image``.
|
||||||
|
|
||||||
|
The topmost overlay is the image which is being written to by the VM and is also
|
||||||
|
described as the ``active`` layer or image.
|
||||||
|
|
||||||
Handling of bitmaps
|
Handling of bitmaps
|
||||||
-------------------
|
-------------------
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user