# Bug reporting

The Red Hat Bugzilla Server should be used to report bugs and request features against libvirt. Before submitting a ticket, check the existing tickets to see if the bug/feature is already tracked.

## General libvirt bug reports

If you are using official libvirt binaries from a Linux distribution check below for distribution specific bug reporting policies first. For general libvirt bug reports, from self-built releases, CVS snapshots and any other non-distribution supported builds, enter tickets under the `Virtualization Tools` product and the `libvirt` component.

- View libvirt tickets
- New libvirt ticket

## Linux Distribution specific bug reports

- If you are using official binaries from a Fedora distribution, enter tickets against the `Fedora` product and the `libvirt` component.
  - View Fedora libvirt tickets
  - New Fedora libvirt ticket
- If you are using official binaries from Red Hat Enterprise Linux distribution, tickets against the `Red Hat Enterprise Linux 5` product and the `libvirt` component.
  - View Red Hat Enterprise Linux libvirt tickets
  - New Red Hat Enterprise Linux libvirt ticket
- If you are using official binaries from another Linux distribution first follow their own bug reporting guidelines.

## How to file high quality bug reports

To increase the likelihood of your bug report being addressed it is important to provide as much information as possible. When filing libvirt bugs use this checklist to see if you are providing enough information:

- The version number of the libvirt build, or date of the CVS checkout
- The hardware architecture being used
- The name of the hypervisor (Xen, QEMU, KVM)
- The XML config of the guest domain if relevant
- For Xen hypervisor, the XenD logfile from /var/log/xen
- For QEMU/KVM, the domain logfile from /var/log/libvirt/qemu

If requesting a new feature attach any available patch to the ticket and also email the patch to the libvirt mailing list for discussion