Differences

This shows you the differences between two versions of the page.

--- manuals:vps:kvm [2026/08/11 17:02] – Update KVM networking and explain repository-managed articles aither
+++ manuals:vps:kvm [2026/08/13 06:49] (current) – Add KVM navigation coverage and vpsAdmin documentation rules aither
@@ Line 51: / Line 51: @@
 A separate [[manuals:vps:datasets|subdataset]] is recommended for disk images.
 It lets you change ZFS properties for this workload later without affecting the
-VPS root dataset. Before creating virtual machines, reduce the root dataset's
+VPS root dataset. Prepare the recommended storage as follows:
-reference quota by the capacity intended for images, create a ''vm-images''
-subdataset with the freed capacity, and mount it in the VPS at
+  * <vpsadmin-nav id="datasets.edit.open">In the VPS details, use **Edit** on the root dataset and reduce its reference quota by the capacity intended for images.</vpsadmin-nav>
-''/srv/libvirt/images''. For example, from the standard 120 GiB allocation you
+  * <vpsadmin-nav id="datasets.create.open">Use **Create dataset** to create a ''vm-images'' subdataset with the freed capacity.</vpsadmin-nav>
-can leave 20 GiB for the root dataset and assign 100 GiB to ''vm-images''. You
+  * <vpsadmin-nav id="datasets.mount.open">Use **Mount** on ''vm-images'' and mount it in the VPS at ''/srv/libvirt/images''.</vpsadmin-nav>
-can then give the first virtual-machine disk 80 GiB and leave 20 GiB free for
-growth and snapshots.
+For example, from the standard 120 GiB allocation you can leave 20 GiB for the
+root dataset and assign 100 GiB to ''vm-images''. You can then give the first
+virtual-machine disk 80 GiB and leave 20 GiB free for growth and snapshots.
 The subdataset is [[manuals:vps:backups|snapshotted]] separately from the VPS

Knowledge base

User Tools

Site Tools

Differences

Page Tools