qemu: really remove last traces of Xenner support

We have twice previously attempted to remove Xenner
support

  commit de9be0ab4d
  Author: Daniel P. Berrange <berrange@redhat.com>
  Date:   Wed Aug 22 17:29:01 2012 +0100

    Remove xenner support

  commit 92572c3d71
  Author: Ján Tomko <jtomko@redhat.com>
  Date:   Wed Feb 18 16:33:50 2015 +0100

    Remove code handling the QEMU_CAPS_DOMID capability

This change really does remove the last traces of it
in the capabilities handling code

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>

docs/drvqemu.html.in

@@ -8,9 +8,7 @@
 
     <p>
       The libvirt KVM/QEMU driver can manage any QEMU emulator from
-      version 0.12.0 or later. It can also manage Xenner, which
-      provides the same QEMU command line syntax and monitor
-      interaction.
+      version 0.12.0 or later.
     </p>
 
     <h2><a name="project">Project Links</a></h2>
@@ -43,12 +41,6 @@
         node. If both are found, then KVM fullyvirtualized, hardware accelerated
         guests will be available.
       </li>
-      <li>
-        <strong>Xenner hypervisor</strong>: The driver will probe <code>/usr/bin</code>
-        for the presence of <code>xenner</code> and <code>/dev/kvm</code> device
-        node. If both are found, then Xen paravirtualized guests can be run using
-        the KVM hardware acceleration.
-      </li>
     </ul>
 
     <h2><a name="uris">Connections to QEMU driver</a></h2>
@@ -647,9 +639,5 @@ $ virsh domxml-to-native qemu-argv demo.xml
   &lt;/devices&gt;
 &lt;/domain&gt;</pre>
 
-    <h3>Xen paravirtualized guests with hardware acceleration</h3>
-
-
-
   </body>
 </html>