How to debug Libvirt problems

From FedoraProject

Revision as of 22:01, 19 October 2009 by Johannbg (Talk | contribs)

Jump to: navigation, search

Contents

Identifying your problem area

Something that ensures that the component in question is at fault not some other thing..

Information to include in your report

All bug reports

In all cases, the following should be mentioned and attached to your bug report:

  • The exact command-line used to start libvirt if other than.
service libvirtd start
  • The version number of libvirt.
rpm -q libvirt
  • The output url from smolt.
smoltSendProfile -a | grep public
  • The name of the hypervisor (Xen, QEMU, KVM) your using.
  • The XML config of the guest domain
  • For Xen hypervisor, the XenD logfile from /var/log/xen
  • For QEMU/KVM, the domain logfile from /var/log/libvirt/qemu

Debugging Libvirt

Warning (medium size).png
Always review and sanitize your logs before submitting them. Often when turning on debug logging or when using debuggers in application they will show/store sensitive information such as passwords etc. simply remove or replace the sensitive string with xxxx in the logs before submitting them.

As root install <components> debug package.

# debuginfo-install <component>

How to GDB component

Note.png
Sample Note
Idea.png
Sample Tip
Warning (medium size).png
Sample Warning