From: Peter Krempa Date: Wed, 4 Nov 2020 16:31:57 +0000 (+0100) Subject: docs: kbase: Reorder some articles in the 'Usage' section X-Git-Tag: v6.10.0-rc1~154 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9ce41c8896295c94b7990070a04fff7dfd2f5891;p=thirdparty%2Flibvirt.git docs: kbase: Reorder some articles in the 'Usage' section Historically we've added them in chronological order, but certain articles are more likely to be needed and thus are easier to find when placed earlier. Signed-off-by: Peter Krempa Reviewed-by: Michal Privoznik --- diff --git a/docs/kbase/index.rst b/docs/kbase/index.rst index f9e42f211f..1494be1e77 100644 --- a/docs/kbase/index.rst +++ b/docs/kbase/index.rst @@ -5,37 +5,37 @@ Knowledge base Usage ----- -`Disk locking `__ - Ensuring exclusive guest access to disks with - `virtlockd `__ or - `Sanlock `__ - `Secure usage `__ Secure usage of the libvirt APIs -`Protected virtualization on s390 `__ - Running secure s390 guests with IBM Secure Execution +`Backing chain management `__ + Explanation of how disk backing chain specification impacts libvirt's + behaviour and basic troubleshooting steps of disk problems. -`Launch security `__ - Securely launching VMs with AMD SEV +`Virtio-FS `__ + Share a filesystem between the guest and the host -`Domain state capture `__ - Comparison between different methods of capturing domain state +`Security with QEMU passthrough `__ + Examination of the security protections used for QEMU and how they need + configuring to allow use of QEMU passthrough with host files/devices. `RPM deployment `__ Explanation of the different RPM packages and illustration of which to pick for installation -`Backing chain management `__ - Explanation of how disk backing chain specification impacts libvirt's - behaviour and basic troubleshooting steps of disk problems. +`Domain state capture `__ + Comparison between different methods of capturing domain state -`Security with QEMU passthrough `__ - Examination of the security protections used for QEMU and how they need - configuring to allow use of QEMU passthrough with host files/devices. +`Disk locking `__ + Ensuring exclusive guest access to disks with + `virtlockd `__ or + `Sanlock `__ -`Virtio-FS `__ - Share a filesystem between the guest and the host +`Protected virtualization on s390 `__ + Running secure s390 guests with IBM Secure Execution + +`Launch security `__ + Securely launching VMs with AMD SEV `KVM real time `__ Run real time workloads in guests on a KVM hypervisor