User Tools

Site Tools


manuals:vps:kvm

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
manuals:vps:kvm [2026/08/11 17:02] – Update KVM networking and explain repository-managed articles aithermanuals:vps:kvm [2026/08/17 11:09] (current) – Link source and virtualization tests and correct the shared translation ID aither
Line 1: Line 1:
-<page>navody:vps:kvm</page>+<page>manuals:vps:kvm</page>
  
 <kb-managed <kb-managed
-  source="https://github.com/vpsfreecz/vpsfree-kb-contracts/blob/master/contract/pages/manuals-vps-kvm.txt" +  source="contract/pages/manuals-vps-kvm.txt" 
-  test="https://github.com/vpsfreecz/vpsfree-kb-contracts/blob/master/tests/suite/kb/kvm.nix"+  test="kb/kvm#*"
 /> />
  
Line 30: Line 30:
 set -euo pipefail set -euo pipefail
  
-export DEBIAN_FRONTEND=noninteractive 
 apt-get update apt-get update
 apt-get install --yes \ apt-get install --yes \
Line 49: Line 48:
 ===== Disk images and ZFS ===== ===== Disk images and ZFS =====
  
-separate [[manuals:vps:datasets|subdataset]] is recommended for disk images. +Use a separate [[manuals:vps:datasets|subdataset]] for disk images. This lets 
-It lets you change ZFS properties for this workload later without affecting the +you change ZFS properties for the workload later without affecting the VPS root 
-VPS root dataset. Before creating virtual machinesreduce the root dataset's +dataset. Prepare the storage as follows: 
-reference quota by the capacity intended for imagescreate a ''vm-images'' + 
-subdataset with the freed capacityand mount it in the VPS at +  * <vpsadmin-nav id="datasets.edit.open">In the VPS detailsuse **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 The subdataset is [[manuals:vps:backups|snapshotted]] separately from the VPS
manuals/vps/kvm.1786467757.txt.gz · Last modified: by aither