You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix issue 1706.
Now basedisk is immediately renamed/converted to diffdisk
(not a diff despite the name) by the VM driver,
except when basedisk is an ISO9660 image.
Decoupling diffdisk from basedisk will eliminate the overhead of differencing I/O
and save some disk space.
I cannot remember why I designed the disk to be split into basedisk and diffdisk.
Maybe it was to allow `limactl factory-reset` to retain the initial state,
although the command was apparently never implemented in that way.
Maybe it was to allow multiple instances to share the same basedisk,
although it was never implemented in that way, either.
Signed-off-by: Akihiro Suda <[email protected]>
Copy file name to clipboardExpand all lines: website/content/en/docs/dev/internals.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,11 @@ Ansible:
44
44
-`ansible-inventory.yaml`: the Ansible node inventory. See [ansible](#ansible).
45
45
46
46
disk:
47
-
-`basedisk`: the base image
48
-
-`diffdisk`: the diff image (QCOW2)
47
+
-`basedisk`: the historical base image. Can be missing since Lima v2.0.
48
+
- The main `limactl` process prepares this `basedisk`, however, a [VM driver](./drivers.md) may convert and rename `basedisk` to `diffdisk` immediately.
49
+
-`diffdisk`: the image, historically a QCOW2 diff from `basedisk`.
50
+
-`diffdisk` is a misnomer; it does not necessarily have a reference to `basedisk`.
51
+
Notably, when a `basedisk` is an ISO9660 image, or the VM driver does not support differencing, `diffdisk` is an independent image.
0 commit comments