From Fedora Project Wiki

Revision as of 21:59, 19 October 2009 by Johannbg (talk | contribs)

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

<Component> related problems

Sample entry

As well as the information from the 'All bug reports' section, include the following information:

Debugging <component>

As root install <components> debug package. 

# debuginfo-install <component>

How to GDB component

Sample Note
Sample Tip
Sample Warning
Retrieved from "https://fedoraproject.org/w/index.php?title=How_to_debug_Libvirt_problems&oldid=131049"