On Mon, Aug 03, 2020 at 03:00:46PM +0200, Peter Krempa wrote: [...]
What to attach? -~~~~~~~~~~~~~~~ +---------------
Now you should go and reproduce the bug. Once you're finished, attach:
- ``/var/log/libvirt/libvirtd.log`` or whatever path you set for the daemon logs. -- If the problem is related to a domain attach - ``/var/log/libvirt/qemu/$dom.log`` then. Or substitute ``qemu`` with whatever - hypervisor you are using. +- If the problem is related to a domain named ``$dom`` attach: + + - ``/var/log/libvirt/qemu/$dom.log`` (Or substitute ``qemu`` with whatever + hypervisor you are using.) + - The XML configuration of the vm/domain obtained by ``virsh dumpxml $dom`` + +- If the problem involves a crash of ``libvirtd`` or any other component also
nit: s/component/component,/
+ attach the core dump backtrace if possible (e.g. using ``coredumpctl``).
s/core dump backtrace/backtrace from a coredump/
- If you are asked for client logs, ``/tmp/libvirt_client.log``. +- Ideally don't tear down the environment in case additionall information is
nit: s/additionall/additional/ With at least the typo fixed: Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
+ required.
-- 2.26.2
-- /kashyap