External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-03 11:35:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

kbase: debuglogs: Include more data to attach to bugreports

Browse Source 
Promote the 'What to attach?' section to a first level heading and
request also the XML config of a VM, coredump backtrace if something
crashed and ask to not tear down the environment for the possibility to
ask for additional data.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
This commit is contained in:
Peter Krempa 2020-08-03 12:09:21 +02:00
parent 862cf2ace4
commit 582bb2ade5
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/kbase/debuglogs.rst
View File

@ -136,13 +136,21 @@ setting which depends on the host configuration, *journald* in our case:
Logging outputs: 2:journald
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
attach the backtrace from the core dump if possible (e.g. using
``coredumpctl``).
- If you are asked for client logs, ``/tmp/libvirt_client.log``.
- Ideally don't tear down the environment in case additional information is
required.