492c4628a1
Provide debug log configuration insight in our kbase. There are two modifications of the document compared to the wiki version: 1) The link for reporting a bug agains libvirt was modified to use the gitlab issue tracker. 2) The link to URI specification details is changed to 'https' protocol. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
1.7 KiB
Knowledge base
- Debug logs
Configuration of logging and tips on how to file a good bug report.
- 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
- Launch security
Securely launching VMs with AMD SEV
- Domain state capture
Comparison between different methods of capturing domain state
- 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.
- 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.
- Virtio-FS
Share a filesystem between the guest and the host
- KVM real time
Run real time workloads in guests on a KVM hypervisor
- Incremental backup internals
Incremental backup implementation details relevant for users