Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt
切换分支/标签
查找文件 普通视图历史永久链接Permalink
bugs.html.in 3.3 KB
Newer Older
D
Split website out into one file per page. APply new layout and styling  
Daniel P. Berrange 已提交
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 
<?xml version="1.0"?>
<html>
  <body>

    <h1>Bug reporting</h1>

    <p>
      The <a href="http://bugzilla.redhat.com">Red Hat Bugzilla Server</a>
      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.
    </p>

    <h2>General libvirt bug reports</h2>

    <p>
      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 <code>Virtualization Tools</code> product and the <code>libvirt</code>
      component.
    </p>

    <ul>
G
Update links to bugzilla  
Garry Dolley 已提交
26 
      <li><a href="http://bugzilla.redhat.com/buglist.cgi?component=libvirt&amp;product=Virtualization%20Tools">View libvirt tickets</a></li>
D
Split website out into one file per page. APply new layout and styling  
Daniel P. Berrange 已提交
27 28 29 30 31 32 33 34 35 36 
      <li><a href="http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Virtualization%20Tools&amp;component=libvirt">New libvirt ticket</a></li>
    </ul>

    <h2>Linux Distribution specific bug reports</h2>
    <ul>
      <li>
	If you are using official binaries from a <strong>Fedora distribution</strong>, enter
	tickets against the <code>Fedora</code> product and the <code>libvirt</code>
	component.
	<ul>
G
Update links to bugzilla  
Garry Dolley 已提交
37 
	  <li><a href="http://bugzilla.redhat.com/buglist.cgi?component=libvirt&amp;product=Fedora">View Fedora libvirt tickets</a></li>
D
Split website out into one file per page. APply new layout and styling  
Daniel P. Berrange 已提交
38 39 40 41 42 43 44 45 
	  <li><a href="http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&amp;component=libvirt">New Fedora libvirt ticket</a></li>
	</ul>
      </li>
      <li>
	If you are using official binaries from <strong>Red Hat Enterprise Linux distribution</strong>,
	tickets against the <code>Red Hat Enterprise Linux 5</code> product and
	the <code>libvirt</code> component.
	<ul>
G
Update the links for RHEL libvirt bugzillas  
Garry Dolley 已提交
46 
	  <li><a href="http://bugzilla.redhat.com/buglist.cgi?component=libvirt&amp;product=Red%20Hat%20Enterprise%20Linux%205">View Red Hat Enterprise Linux libvirt tickets</a></li>
D
Split website out into one file per page. APply new layout and styling  
Daniel P. Berrange 已提交
47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 
	  <li><a href="http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%205&amp;component=libvirt">New Red Hat Enterprise Linux libvirt ticket</a></li>
	</ul>
      </li>
      <li>
	If you are using official binaries from another Linux distribution first
	follow their own bug reporting guidelines.
      </li>
    </ul>


    <h2>How to file high quality bug reports</h2>

    <p>
      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:
    </p>

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

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

  </body>
</html>