5f14729bbe
Enabling core dumps is a reasonably straightforward task, but is not documented clearly. This page provides as easy link to point users to when they need to debug QEMU. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2.4 KiB
Knowledge base
Usage
- Secure usage
Secure usage of the libvirt APIs
- Backing chain management
Explanation of how disk backing chain specification impacts libvirt's behaviour and basic troubleshooting steps of disk problems.
- Virtio-FS
Share a filesystem between the guest and the host
- 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
- Domain state capture
Comparison between different methods of capturing domain state
- Disk locking
Ensuring exclusive guest access to disks with virtlockd or Sanlock
- Protected virtualization on s390
Running secure s390 guests with IBM Secure Execution
- Launch security
Securely launching VMs with AMD SEV
- Live full disk backup
A walkthrough of how to take effective live full disk backups.
- Merging disk image chains
Ways to reduce or consolidate disk image chains.
- KVM real time
Run real time workloads in guests on a KVM hypervisor
- PCI hotplug
Effective usage of PCI hotplug
- PCI topology
Addressing schemes for PCI devices
Internals / Debugging
- Debug logs
Configuration of logging and tips on how to file a good bug report.
- Systemtap
Explanation of how to use systemtap for libvirt tracing.
- Incremental backup internals
Incremental backup implementation details relevant for users
- VM migration internals
VM migration implementation details, complementing the info in migration
- Capturing core dumps for QEMU
How to configure libvirt to enable capture of core dumps from QEMU virtual machines