libvirt/docs/kbase.html.in

52 lines
2.0 KiB
HTML
Raw Normal View History

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<body class="docs">
<h1>Knowledge base</h1>
<div class="panel">
<dl>
<dt><a href="kbase/locking.html">Disk locking</a></dt>
<dd>Ensuring exclusive guest access to disks with
<a href="kbase/locking-lockd.html">virtlockd</a> or
<a href="kbase/locking-sanlock.html">Sanlock</a></dd>
<dt><a href="kbase/secureusage.html">Secure usage</a></dt>
<dd>Secure usage of the libvirt APIs</dd>
<dt><a href="kbase/s390_protected_virt.html">Protected virtualization on s390</a></dt>
<dd>Running secure s390 guests with IBM Secure Execution</dd>
<dt><a href="kbase/launch_security_sev.html">Launch security</a></dt>
<dd>Securely launching VMs with AMD SEV</dd>
<dt><a href="kbase/domainstatecapture.html">Domain state
capture</a></dt>
<dd>Comparison between different methods of capturing domain
state</dd>
<dt><a href="kbase/rpm-deployment.html">RPM deployment</a></dt>
<dd>Explanation of the different RPM packages and illustration of
which to pick for installation</dd>
<dt><a href="kbase/backing_chains.html">Backing chain management</a></dt>
<dd>Explanation of how disk backing chain specification impacts libvirt's
behaviour and basic troubleshooting steps of disk problems.</dd>
<dt><a href="kbase/qemu-passthrough-security.html">Security with QEMU passthrough</a></dt>
<dd>Examination of the security protections used for QEMU and how they need
configuring to allow use of QEMU passthrough with host files/devices.</dd>
<dt><a href="kbase/virtiofs.html">Virtio-FS</a></dt>
<dd>Share a filesystem between the guest and the host</dd>
<dt><a href="kbase/kvm-realtime.html">KVM real time</a></dt>
<dd>Run real time workloads in guests on a KVM hypervisor</dd>
</dl>
</div>
<br class="clear"/>
</body>
</html>