diff --git a/docs/bugs.html.in b/docs/bugs.html.in index 560dfa44095c9df9f01b4268bdbfb3ef146f7451..39b6725eec4c0e3e20f359606f97451570bc3aa6 100644 --- a/docs/bugs.html.in +++ b/docs/bugs.html.in @@ -9,22 +9,47 @@
- The Red Hat Bugzilla Server - should be used to report bugs and request features in libvirt. - Before submitting a ticket, check the existing tickets to see if - the bug/feature is already tracked. + If you are using libvirt binaries from a Linux distribution + check below for distribution specific bug reporting policies + first.
- If you are using official libvirt binaries from a Linux distribution
- check below for distribution specific bug reporting policies first.
+ The Red Hat Bugzilla Server
+ should be used to report bugs and request features in libvirt.
+ Before submitting a ticket, check the existing tickets to see if
+ the bug/feature is already tracked.
+
For general libvirt bug reports, from self-built releases, GIT snapshots
and any other non-distribution supported builds, enter tickets under
the Virtualization Tools
product and the libvirt
component.
+ It's always a good idea to file bug reports, as the process of + filing the report always makes it easier to describe the + problem, and the bug number provides a quick way of referring to + the problem. However, not everybody in the community pays + attention to bugzilla, so after you file a bug, asking questions + and submitting patches on the libvirt + mailing lists will increase your bug's visibility and + encourage people to think about your problem. Don't hesitate to + ask questions on the list, as others may know of existing + solutions or be interested in collaborating with you on finding + a solution. Patches are always appreciated, and it's likely + that someone else has the same problem you do! +
++ If you decide to write code, though, before you begin please + read the contributor guidelines, + especially the first point: "Discuss any large changes on the + mailing list first. Post patches early and listen to feedback." + Few development experiences are more discouraging than spending + a bunch of time writing a patch only to have someone point out a + better approach on list. +
Fedora
product and the libvirt
- component.
+ If you are using binaries from Fedora, enter
+ tickets against the Fedora
product and
+ the libvirt
component.
Red Hat Enterprise Linux 5
product and
- the libvirt
component.
-
+
+ If you are using binaries from Red Hat Enterprise
+ Linux, enter tickets against the Red Hat Enterprise
+ Linux product that you're using (e.g., Red Hat Enterprise
+ Linux 6) and the libvirt
component. Red Hat
+ bugzilla has additional guidance about getting support if
+ you are a Red Hat customer.
+
+ If you are using binaries from another Linux distribution + first follow their own bug reporting guidelines. +
++ Finally, if you are a contributor to another Linux + distribution and would like to have your procedure for + filing bugs mentioned here, please mail the libvirt + development list. +
- It may also happen that the libvirt daemon itself crashes or get stuck,
+ It may also happen that the libvirt daemon itself crashes or gets stuck,
in the first case run it (as root) under gdb, and reproduce the sequence
leading to the crash, similary to a normal program provide the
"bt" backtrace information to where gdb will have stopped.
- But if libvirtd get stuck, for example seems to stop processing
+ But if libvirtd gets stuck, for example seems to stop processing
commands, try to attach to the faulty daemon and issue a gdb command
"thread apply all bt" to show all the threads backtraces, as in:
# ps -o etime,pid `pgrep libvirt` @@ -106,10 +142,5 @@ (gdb)-
- If requesting a new feature attach any available patch to the ticket - and also email the patch to the libvirt mailing list for discussion -
-