Release of libvirt-3.7.0

* docs/news.xml: update for release * po/*.po*: regenerated
vmx: Expose VMware Managed Object Reference (moref) in XML.
2025-09-19 01:44:56 +03:00 · 2017-09-04 12:14:11 +02:00 · 2017-09-04 09:48:32 +01:00 · 2017-09-02 08:06:59 -04:00 · 2017-09-02 11:09:06 +02:00 · 2017-09-02 10:54:28 +02:00
453 changed files with 598754 additions and 531469 deletions
--- a/.gnulib
+++ b/.gnulib
--- a/.travis.yml
+++ b/.travis.yml
@@ -38,7 +38,6 @@ addons:
      - libapparmor-dev
      - dnsmasq-base
      - librbd-dev
-      - w3c-dtd-xhtml

 notifications:
  irc:
--- a/configure.ac
+++ b/configure.ac
@@ -16,7 +16,7 @@ dnl You should have received a copy of the GNU Lesser General Public
 dnl License along with this library.  If not, see
 dnl <http://www.gnu.org/licenses/>.

-AC_INIT([libvirt], [3.6.0], [libvir-list@redhat.com], [], [http://libvirt.org])
+AC_INIT([libvirt], [3.7.0], [libvir-list@redhat.com], [], [http://libvirt.org])
 AC_CONFIG_SRCDIR([src/libvirt.c])
 AC_CONFIG_AUX_DIR([build-aux])
 AC_CONFIG_HEADERS([config.h])
--- a/daemon/libvirtd-config.c
+++ b/daemon/libvirtd-config.c
@@ -153,7 +153,6 @@ daemonConfigNew(bool privileged ATTRIBUTE_UNUSED)

    data->prio_workers = 5;

-    data->max_requests = 20;
    data->max_client_requests = 5;

    data->audit_level = 1;
@@ -348,8 +347,6 @@ daemonConfigLoadOptions(struct daemonConfig *data,
    if (virConfGetValueUInt(conf, "prio_workers", &data->prio_workers) < 0)
        goto error;

-    if (virConfGetValueUInt(conf, "max_requests", &data->max_requests) < 0)
-        goto error;
    if (virConfGetValueUInt(conf, "max_client_requests", &data->max_client_requests) < 0)
        goto error;

@@ -433,7 +430,7 @@ int daemonConfigLoadData(struct daemonConfig *data,
    virConfPtr conf;
    int ret;

-    conf = virConfReadMem(filedata, strlen(filedata), 0);
+    conf = virConfReadString(filedata, 0);
    if (!conf)
        return -1;

--- a/daemon/libvirtd-config.h
+++ b/daemon/libvirtd-config.h
@@ -71,7 +71,6 @@ struct daemonConfig {

    unsigned int prio_workers;

-    unsigned int max_requests;
    unsigned int max_client_requests;

    unsigned int log_level;
--- a/daemon/libvirtd.aug
+++ b/daemon/libvirtd.aug
@@ -60,7 +60,6 @@ module Libvirtd =
                        | int_entry "max_clients"
                        | int_entry "max_queued_clients"
                        | int_entry "max_anonymous_clients"
-                        | int_entry "max_requests"
                        | int_entry "max_client_requests"
                        | int_entry "prio_workers"

--- a/daemon/libvirtd.c
+++ b/daemon/libvirtd.c
@@ -615,19 +615,15 @@ daemonSetupLogging(struct daemonConfig *config,
     * Libvirtd's order of precedence is:
     * cmdline > environment > config
     *
-     * The default output is applied only if there was no setting from either
-     * the config or the environment. Because we don't have a way to determine
-     * if the log level has been set, we must process variables in the opposite
+     * Given the precedence, we must process the variables in the opposite
     * order, each one overriding the previous.
     */
    if (config->log_level != 0)
        virLogSetDefaultPriority(config->log_level);

-    if (virLogSetDefaultOutput("libvirtd.log", godaemon, privileged) < 0)
-        return -1;
-
-    /* In case the config is empty, the filters become empty and outputs will
-     * be set to default
+    /* In case the config is empty, both filters and outputs will become empty,
+     * however we can't start with empty outputs, thus we'll need to define and
+     * setup a default one.
     */
    ignore_value(virLogSetFilters(config->log_filters));
    ignore_value(virLogSetOutputs(config->log_outputs));
@@ -641,6 +637,15 @@ daemonSetupLogging(struct daemonConfig *config,
    if ((verbose) && (virLogGetDefaultPriority() > VIR_LOG_INFO))
        virLogSetDefaultPriority(VIR_LOG_INFO);

+    /* Define the default output. This is only applied if there was no setting
+     * from either the config or the environment.
+     */
+    if (virLogSetDefaultOutput("libvirtd.log", godaemon, privileged) < 0)
+        return -1;
+
+    if (virLogGetNbOutputs() == 0)
+        virLogSetOutputs(virLogGetDefaultOutput());
+
    return 0;
 }

--- a/daemon/libvirtd.conf
+++ b/daemon/libvirtd.conf
@@ -301,20 +301,10 @@
 # (notably domainDestroy) can be executed in this pool.
 #prio_workers = 5

-# Total global limit on concurrent RPC calls. Should be
-# at least as large as max_workers. Beyond this, RPC requests
-# will be read into memory and queued. This directly impacts
-# memory usage, currently each request requires 256 KB of
-# memory. So by default up to 5 MB of memory is used
-#
-# XXX this isn't actually enforced yet, only the per-client
-# limit is used so far
-#max_requests = 20
-
 # Limit on concurrent requests from a single client
 # connection. To avoid one client monopolizing the server
-# this should be a small fraction of the global max_requests
-# and max_workers parameter
+# this should be a small fraction of the global max_workers
+# parameter.
 #max_client_requests = 5

 # Same processing controls, but this time for the admin interface.
--- a/daemon/test_libvirtd.aug.in
+++ b/daemon/test_libvirtd.aug.in
@@ -42,7 +42,6 @@ module Test_libvirtd =
        { "min_workers" = "5" }
        { "max_workers" = "20" }
        { "prio_workers" = "5" }
-        { "max_requests" = "20" }
        { "max_client_requests" = "5" }
        { "admin_min_workers" = "1" }
        { "admin_max_workers" = "5" }
--- a/docs/404.html.in
+++ b/docs/404.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>404 page not found</h1>
--- a/docs/Makefile.am
+++ b/docs/Makefile.am
@@ -52,6 +52,7 @@ devhelphtml =			\
 css =         \
  generic.css \
  libvirt.css \
+  mobile.css \
  main.css

 fonts = \
@@ -198,9 +199,9 @@ MAINTAINERCLEANFILES = \

 timestamp="$(shell if test -n "$$SOURCE_DATE_EPOCH"; \
 		   then \
-		     date --date="@$$SOURCE_DATE_EPOCH"; \
+		     date -u --date="@$$SOURCE_DATE_EPOCH"; \
 		   else \
-		     date; \
+		     date -u; \
 		   fi)"

 all-am: web
@@ -228,17 +229,14 @@ $(srcdir)/hvsupport.html.in: $(srcdir)/hvsupport.pl $(api_DATA) \
 news.html.in: \
 	  $(srcdir)/news.xml \
 	  $(srcdir)/news-html.xsl
-	$(AM_V_GEN) \
-	if [ -x $(XSLTPROC) ]; then \
-	  $(XSLTPROC) --nonet \
+	$(AM_V_GEN)$(XSLTPROC) --nonet \
 	    $(srcdir)/news-html.xsl \
 	    $(srcdir)/news.xml \
 	  >$@-tmp \
 	    || { rm -f $@-tmp; exit 1; }; \
 	  sed 's/ xmlns=""//g' $@-tmp >$@ \
 	    || { rm -f $@-tmp; exit 1; }; \
-	  rm -f $@-tmp; \
-	fi
+	  rm -f $@-tmp
 EXTRA_DIST += \
 	$(srcdir)/news.xml \
 	$(srcdir)/news.rng \
@@ -251,9 +249,7 @@ MAINTAINERCLEANFILES += \

 %.html.tmp: %.html.in site.xsl subsite.xsl page.xsl \
 		$(acl_generated)
-	@if [ -x $(XSLTPROC) ] ; then \
-	  echo "Generating $@"; \
-	  name=`echo $@ | sed -e 's/.tmp//'`; \
+	$(AM_V_GEN)name=`echo $@ | sed -e 's/.tmp//'`; \
 	  dir=`dirname $@` ; \
 	  if test "$$dir" = "."; \
 	  then \
@@ -265,53 +261,37 @@ MAINTAINERCLEANFILES += \
 	  $(XSLTPROC) --stringparam pagename $$name \
 	    --stringparam timestamp $(timestamp) --nonet \
 	    $(top_srcdir)/docs/$$style $< > $@ \
-	    || { rm $@ && exit 1; }; fi
+	    || { rm $@ && exit 1; }

 %.html: %.html.tmp
-	@if test -x $(XMLLINT) && test -x $(XMLCATALOG) ; then \
-	  if $(XMLCATALOG) '$(XML_CATALOG_FILE)' \
-	    "-//W3C//DTD XHTML 1.0 Strict//EN" > /dev/null ; then \
-	  echo "Validating $@" ; \
-	  SGML_CATALOG_FILES='$(XML_CATALOG_FILE)' \
-	  $(XMLLINT) --catalogs --nonet --format --valid $< > $(srcdir)/$@ \
-	  || { rm $(srcdir)/$@ && exit 1; }; \
-	  else echo "missing XHTML1 DTD"; cat $< > $(srcdir)/$@ ; fi ; fi
+	$(AM_V_GEN)$(XMLLINT) --nonet --format $< > $(srcdir)/$@ \
+	  || { rm $(srcdir)/$@ && exit 1; }

 %.php.tmp: %.php.in site.xsl page.xsl
-	if [ -x $(XSLTPROC) ] ; then \
-	  echo "Generating $@"; \
-	  $(XSLTPROC) --stringparam pagename $(@:.tmp=) \
+	$(AM_V_GEN)$(XSLTPROC) --stringparam pagename $(@:.tmp=) \
 	    --stringparam timestamp $(timestamp) --nonet \
 	    $(top_srcdir)/docs/site.xsl $< > $@ \
-	    || { rm $@ && exit 1; }; fi
+	    || { rm $@ && exit 1; }

 %.php: %.php.tmp %.php.code.in
-	@if [ -x $(XSLTPROC) ] ; then \
-	  echo "Scripting $@"; \
-	    sed -e '/<span id="php_placeholder"><\/span>/r '"$(srcdir)/$@.code.in" \
+	$(AM_V_GEN)sed \
+	    -e '/<span id="php_placeholder"><\/span>/r '"$(srcdir)/$@.code.in" \
 	    -e /php_placeholder/d < $@.tmp > $(srcdir)/$@ \
-	    || { rm $(srcdir)/$@ && exit 1; }; fi
+	    || { rm $(srcdir)/$@ && exit 1; }

 $(apihtml_generated): html/index.html

 html/index.html: libvirt-api.xml newapi.xsl page.xsl $(APIBUILD_STAMP)
-	$(AM_V_GEN)if [ -x $(XSLTPROC) ] ; then \
-	  $(XSLTPROC) --nonet -o $(srcdir)/ \
+	$(AM_V_GEN)$(XSLTPROC) --nonet -o $(srcdir)/ \
 	  --stringparam builddir '$(abs_top_builddir)' \
 	  --stringparam timestamp $(timestamp) \
-	  $(srcdir)/newapi.xsl $(srcdir)/libvirt-api.xml ; fi && \
-	if test -x $(XMLLINT) && test -x $(XMLCATALOG) ; then \
-	  if $(XMLCATALOG) '$(XML_CATALOG_FILE)' "-//W3C//DTD XHTML 1.0 Strict//EN" \
-	    > /dev/null ; then \
-	  SGML_CATALOG_FILES='$(XML_CATALOG_FILE)' \
-	  $(XMLLINT) --catalogs --nonet --valid --noout $(srcdir)/html/*.html ; \
-	  else echo "missing XHTML1 DTD"; cat $< > $(srcdir)/$@ ; fi ; fi
+	  $(srcdir)/newapi.xsl $(srcdir)/libvirt-api.xml && \
+	  $(XMLLINT) --nonet --noout $(srcdir)/html/*.html

 $(addprefix $(srcdir)/,$(devhelphtml)): $(srcdir)/libvirt-api.xml $(devhelpxsl)
-	$(AM_V_GEN)if [ -x $(XSLTPROC) ] ; then \
-	  $(XSLTPROC) --stringparam timestamp $(timestamp) \
-	    --nonet -o $(srcdir)/devhelp/ \
-	  $(top_srcdir)/docs/devhelp/devhelp.xsl $(srcdir)/libvirt-api.xml ; fi
+	$(AM_V_GEN)$(XSLTPROC) --stringparam timestamp $(timestamp) \
+	  --nonet -o $(srcdir)/devhelp/ \
+	  $(top_srcdir)/docs/devhelp/devhelp.xsl $(srcdir)/libvirt-api.xml


 python_generated_files = \
--- a/docs/acl.html.in
+++ b/docs/acl.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Client access control</h1>
@@ -12,7 +12,7 @@

    <ul id="toc"></ul>

-    <h2><a name="intro">Access control introduction</a></h2>
+    <h2><a id="intro">Access control introduction</a></h2>

    <p>
      In a default configuration, the libvirtd daemon has three levels
@@ -42,7 +42,7 @@
      <code>getattr</code> permission.
    </p>

-    <h2><a name="drivers">Access control drivers</a></h2>
+    <h2><a id="drivers">Access control drivers</a></h2>

    <p>
      The access control framework is designed as a pluggable
@@ -83,7 +83,7 @@
      the libvirtd daemon be restarted.
    </p>

-    <h2><a name="perms">Objects and permissions</a></h2>
+    <h2><a id="perms">Objects and permissions</a></h2>

    <p>
      Libvirt applies access control to all the main object
--- a/docs/aclpolkit.html.in
+++ b/docs/aclpolkit.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Polkit access control</h1>
@@ -14,7 +14,7 @@

    <ul id="toc"></ul>

-    <h2><a name="intro">Introduction</a></h2>
+    <h2><a id="intro">Introduction</a></h2>

    <p>
      A default install of libvirt will typically use
@@ -27,7 +27,7 @@
      object.
    </p>

-    <h2><a name="perms">Permission names</a></h2>
+    <h2><a id="perms">Permission names</a></h2>

    <p>
      The libvirt <a href="acl.html#perms">object names and permission names</a>
@@ -53,7 +53,7 @@
      permissions default to deny access.
    </p>

-    <h2><a name="attrs">Object identity attributes</a></h2>
+    <h2><a id="attrs">Object identity attributes</a></h2>

    <p>
      To allow polkit authorization rules to be written to match
@@ -63,7 +63,7 @@
      of object being checked
    </p>

-    <h3><a name="object_connect">virConnectPtr</a></h3>
+    <h3><a id="object_connect">virConnectPtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -79,7 +79,7 @@
      </tbody>
    </table>

-    <h3><a name="object_domain">virDomainPtr</a></h3>
+    <h3><a id="object_domain">virDomainPtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -103,7 +103,7 @@
      </tbody>
    </table>

-    <h3><a name="object_interface">virInterfacePtr</a></h3>
+    <h3><a id="object_interface">virInterfacePtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -127,7 +127,7 @@
      </tbody>
    </table>

-    <h3><a name="object_network">virNetworkPtr</a></h3>
+    <h3><a id="object_network">virNetworkPtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -151,7 +151,7 @@
      </tbody>
    </table>

-    <h3><a name="object_node_device">virNodeDevicePtr</a></h3>
+    <h3><a id="object_node_device">virNodeDevicePtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -171,7 +171,7 @@
      </tbody>
    </table>

-    <h3><a name="object_nwfilter">virNWFilterPtr</a></h3>
+    <h3><a id="object_nwfilter">virNWFilterPtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -195,7 +195,7 @@
      </tbody>
    </table>

-    <h3><a name="object_secret">virSecretPtr</a></h3>
+    <h3><a id="object_secret">virSecretPtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -231,7 +231,7 @@
      </tbody>
    </table>

-    <h3><a name="object_storage_pool">virStoragePoolPtr</a></h3>
+    <h3><a id="object_storage_pool">virStoragePoolPtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -255,7 +255,7 @@
      </tbody>
    </table>

-    <h3><a name="object_storage_vol">virStorageVolPtr</a></h3>
+    <h3><a id="object_storage_vol">virStorageVolPtr</a></h3>
    <table class="acl">
      <thead>
        <tr>
@@ -288,7 +288,7 @@
    </table>


-    <h2><a name="user">User identity attributes</a></h2>
+    <h2><a id="user">User identity attributes</a></h2>

    <p>
      At this point in time, the only attribute provided by
@@ -307,7 +307,7 @@
    </p>


-    <h2><a name="checks">Writing access control policies</a></h2>
+    <h2><a id="checks">Writing access control policies</a></h2>

    <p>
      If using versions of polkit prior to 0.106 then it is only
@@ -358,7 +358,7 @@ polkit.addRule(function(action, subject) {
    for a more complex example.
    </p>

-    <h3><a name="exconnect">Example: restricting ability to connect to drivers</a></h3>
+    <h3><a id="exconnect">Example: restricting ability to connect to drivers</a></h3>

    <p>
      Consider a local user <code>berrange</code>
@@ -386,7 +386,7 @@ polkit.addRule(function(action, subject) {
 });
    </pre>

-    <h3><a name="exdomain">Example: restricting access to a single domain</a></h3>
+    <h3><a id="exdomain">Example: restricting access to a single domain</a></h3>

    <p>
      Consider a local user <code>berrange</code>
--- a/docs/android-chrome-192x192.png
+++ b/docs/android-chrome-192x192.png
--- a/docs/android-chrome-256x256.png
+++ b/docs/android-chrome-256x256.png
--- a/docs/api.html.in
+++ b/docs/api.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>The libvirt API concepts</h1>
@@ -9,7 +9,7 @@

    <ul id="toc"></ul>

-    <h2><a name="Objects">Objects Exposed</a></h2>
+    <h2><a id="Objects">Objects Exposed</a></h2>
    <p> As defined in the <a href="goals.html">goals section</a>, the libvirt
    API is designed to expose all the resources needed to manage the
    virtualization support of recent operating systems. The first object
@@ -121,7 +121,7 @@
      set of nodes.</p></li>
    </ul>

-    <h2><a name="Functions">Functions and Naming Conventions</a></h2>
+    <h2><a id="Functions">Functions and Naming Conventions</a></h2>
    <p> The naming of the functions present in the library is usually
      composed by a prefix describing the object associated to the function
      and a verb describing the action on that object.</p>
@@ -297,7 +297,7 @@
    <p> For more in-depth details of the storage related APIs see
      <a href="storage.html">the storage management page</a>.
    </p>
-    <h2><a name="Drivers">The libvirt Drivers</a></h2>
+    <h2><a id="Drivers">The libvirt Drivers</a></h2>
    <p>Drivers are the basic building block for libvirt functionality
    to support the capability to handle specific hypervisor driver calls.
    Drivers are discovered and registered during connection processing as
@@ -325,7 +325,7 @@
    the various functions and support found in each driver by the version
    support was added into libvirt.
    </p>
-    <h2><a name="Remote">Daemon and Remote Access</a></h2>
+    <h2><a id="Remote">Daemon and Remote Access</a></h2>
    <p>Access to libvirt drivers is primarily handled by the libvirtd
    daemon through the <a href="remote.html">remote</a> driver via an
    <a href="internals/rpc.html">RPC</a>. Some hypervisors do support
--- a/docs/api_extension.html.in
+++ b/docs/api_extension.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Implementing a new API in Libvirt</h1>
@@ -273,7 +273,7 @@
      <li>unlocks the remote driver.</li>
    </ol>

-    <h3><a name="serverdispatch">Implement the server side dispatcher</a></h3>
+    <h3><a id="serverdispatch">Implement the server side dispatcher</a></h3>

    <p>
      Implementing the server side of the remote function call is simply a
@@ -300,7 +300,7 @@

    <p class="example">See <a href="api_extension/0005-implement-the-remote-protocol.patch">0005-implement-the-remote-protocol.patch</a></p>

-    <h2><a name="internaluseapi">Use the new API internally</a></h2>
+    <h2><a id="internaluseapi">Use the new API internally</a></h2>

    <p>
      Sometimes, a new API serves as a superset of existing API, by
@@ -314,7 +314,7 @@

    <p class="example">See <a href="api_extension/0006-make-old-API-trivially-wrap-to-new-API.patch">0006-make-old-API-trivially-wrap-to-new-API.patch</a></p>

-    <h2><a name="virshuseapi">Expose the new API in virsh</a></h2>
+    <h2><a id="virshuseapi">Expose the new API in virsh</a></h2>

    <p>
      All new API should be manageable from the virsh command line
@@ -345,7 +345,7 @@

    <p class="example">See <a href="api_extension/0007-add-virsh-support.patch">0007-add-virsh-support.patch</a></p>

-    <h2><a name="driverimpl">Implement the driver methods</a></h2>
+    <h2><a id="driverimpl">Implement the driver methods</a></h2>

    <p>
      So, after all that, we get to the fun part.  All functionality in
@@ -356,7 +356,7 @@
      adding.
    </p>

-    <h3><a name="commonimpl">Implement common handling</a></h3>
+    <h3><a id="commonimpl">Implement common handling</a></h3>

    <p>
      If the new API is applicable to more than one driver, it may
@@ -373,7 +373,7 @@

    <p class="example">See <a href="api_extension/0008-support-new-xml.patch">0008-support-new-xml.patch</a></p>

-    <h3><a name="drivercode">Implement driver handling</a></h3>
+    <h3><a id="drivercode">Implement driver handling</a></h3>

    <p>
      The remaining patches should only touch one driver at a time.
--- a/docs/apple-touch-icon.png
+++ b/docs/apple-touch-icon.png
--- a/docs/apps.html.in
+++ b/docs/apps.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Applications using libvirt</h1>
@@ -11,7 +11,7 @@

    <ul id="toc"></ul>

-    <h2><a name="add">Add an application</a></h2>
+    <h2><a id="add">Add an application</a></h2>

    <p>
      To add an application not listed on this page, send a message
@@ -30,7 +30,7 @@
      <img src="logos/logo-square-powered-256.png" alt="libvirt powered"/>
    </p>

-    <h2><a name="clientserver">Client/Server applications</a></h2>
+    <h2><a id="clientserver">Client/Server applications</a></h2>

    <dl>
      <dt><a href="http://archipelproject.org">Archipel</a></dt>
@@ -50,7 +50,7 @@
      </dd>
    </dl>

-    <h2><a name="command">Command line tools</a></h2>
+    <h2><a id="command">Command line tools</a></h2>

    <dl>
      <dt><a href="http://libguestfs.org">guestfish</a></dt>
@@ -121,7 +121,7 @@
      </dd>
    </dl>

-    <h2><a name="configmgmt">Configuration Management</a></h2>
+    <h2><a id="configmgmt">Configuration Management</a></h2>

    <dl>
      <dt><a href="https://wiki.lcfg.org/bin/view/LCFG/LcfgLibvirt">LCFG</a></dt>
@@ -139,7 +139,7 @@
      </dd>
    </dl>

-    <h2><a name="continuousintegration">Continuous Integration</a></h2>
+    <h2><a id="continuousintegration">Continuous Integration</a></h2>

    <dl>
      <dt><a href="http://buildbot.net/buildbot/docs/current/Libvirt.html">BuildBot</a></dt>
@@ -163,7 +163,7 @@
      </dd>
    </dl>

-    <h2><a name="conversion">Conversion</a></h2>
+    <h2><a id="conversion">Conversion</a></h2>

    <dl>
      <dt><a href="http://libguestfs.org/virt-p2v.1.html">virt-p2v</a></dt>
@@ -194,7 +194,7 @@
      </dd>
    </dl>

-    <h2><a name="desktop">Desktop applications</a></h2>
+    <h2><a id="desktop">Desktop applications</a></h2>

    <dl>
      <dt><a href="http://virt-manager.org/">virt-manager</a></dt>
@@ -224,7 +224,7 @@
      </dd>
    </dl>

-    <h2><a name="iaas">Infrastructure as a Service (IaaS)</a></h2>
+    <h2><a id="iaas">Infrastructure as a Service (IaaS)</a></h2>

    <dl>
      <dt><a href="http://cc1.ifj.edu.pl">Cracow Cloud One</a></dt>
@@ -286,9 +286,19 @@
        perfect for setting up low-end servers in a cloud or a
        cloud where you want the most bang for the bucks.
      </dd>
+
+      <dt><a href="http://en.zstack.io/">ZStack</a></dt>
+      <dd>
+        ZStack is an open source IaaS software that aims to automate the
+        management of all resources (compute, storage, networking, etc.) in a
+        datacenter by using APIs, thus conforming to the principles of a
+        software-defined datacenter. The key strengths of ZStack in terms of
+        management are scalability, performance, and a fast, user-friendly
+        deployment.
+      </dd>
    </dl>

-    <h2><a name="libraries">Libraries</a></h2>
+    <h2><a id="libraries">Libraries</a></h2>

    <dl>
      <dt><a href="http://libguestfs.org">libguestfs</a></dt>
@@ -321,7 +331,7 @@
      </dd>
    </dl>

-    <h2><a name="livecd">LiveCD / Appliances</a></h2>
+    <h2><a id="livecd">LiveCD / Appliances</a></h2>

    <dl>
      <dt><a href="http://et.redhat.com/~rjones/virt-p2v/">virt-p2v</a></dt>
@@ -334,7 +344,7 @@
      </dd>
    </dl>

-    <h2><a name="monitoring">Monitoring</a></h2>
+    <h2><a id="monitoring">Monitoring</a></h2>
    <dl>
      <dt><a href="http://collectd.org/plugins/libvirt.shtml">collectd</a></dt>
      <dd>
@@ -353,7 +363,7 @@
      </dd>
      <dt><a href="http://honk.sigxcpu.org/projects/libvirt/#munin">Munin</a></dt>
      <dd>
-        The plugins provided by Guido G&uuml;nther allow to monitor various things
+        The plugins provided by Guido Günther allow to monitor various things
        like network and block I/O with
        <a href="http://munin.projects.linpro.no/">Munin</a>.
      </dd>
@@ -365,10 +375,10 @@
        your Xen or QEMU/KVM guests, or to integrate with your existing Nagios
        installation.
      </dd>
-      <dt><a href="http://www.pcp.io/man/man1/pmdalibvirt.1.html" shape="rect">PCP</a></dt>
+      <dt><a href="http://www.pcp.io/man/man1/pmdalibvirt.1.html">PCP</a></dt>
      <dd>
        The PCP libvirt PMDA (plugin) is part of the
-        <a href="http://pcp.io/" shape="rect">PCP</a> toolkit and provides
+        <a href="http://pcp.io/">PCP</a> toolkit and provides
        hypervisor and guest information and complete set of guest performance
        metrics. It supports pCPU, vCPU, memory, block device, network interface,
        and performance event metrics for each virtual guest.
@@ -381,7 +391,7 @@
      </dd>
    </dl>

-    <h2><a name="provisioning">Provisioning</a></h2>
+    <h2><a id="provisioning">Provisioning</a></h2>

    <dl>
      <dt><a href="http://www.ibm.com/software/tivoli/products/prov-mgr/">Tivoli Provisioning Manager</a></dt>
@@ -415,7 +425,7 @@
    </dl>


-    <h2><a name="web">Web applications</a></h2>
+    <h2><a id="web">Web applications</a></h2>

    <dl>
      <dt><a href="http://community.abiquo.com/display/AbiCloud">AbiCloud</a></dt>
@@ -468,7 +478,7 @@
      </dd>
    </dl>

-    <h2><a name="mobile">Mobile applications</a></h2>
+    <h2><a id="mobile">Mobile applications</a></h2>

    <dl>
      <dt><a href="https://market.android.com/details?id=vm.manager">VM Manager</a></dt>
@@ -479,7 +489,7 @@
      </dd>
    </dl>

-    <h2><a name="other">Other</a></h2>
+    <h2><a id="other">Other</a></h2>

    <dl>
      <dt><a href="http://cuckoosandbox.org/">Cuckoo Sandbox</a></dt>
--- a/docs/architecture.html.in
+++ b/docs/architecture.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1 >libvirt architecture</h1>
@@ -13,7 +13,7 @@

    <ul id="toc"></ul>

-    <h2><a name="Xen">Xen support</a></h2>
+    <h2><a id="Xen">Xen support</a></h2>

    <p>When running in a Xen environment, programs using libvirt have to execute
 in "Domain 0", which is the primary Linux OS loaded on the machine. That OS
@@ -46,7 +46,7 @@ connect to initialize the library. It will then fork a libvirt_proxy
 program running as root and providing read_only access to the API, this is
 then only useful for reporting and monitoring.</p>

-    <h2><a name="QEmu">QEmu and KVM support</a></h2>
+    <h2><a id="QEmu">QEmu and KVM support</a></h2>

    <p>The model for QEmu and KVM is completely similar, basically KVM is based
 on QEmu for the process controlling a new domain, only small details differs
@@ -60,7 +60,7 @@ domain, by specifying the architecture and machine type targeted.</p>
    <p>The code controlling the QEmu process is available in the
 <code>qemud/</code> directory.</p>

-    <h2><a name="drivers">Driver based architecture</a></h2>
+    <h2><a id="drivers">Driver based architecture</a></h2>

    <p>As the previous section explains, libvirt can communicate using different
 channels with the current hypervisor, and should also be able to use
--- a/docs/auditlog.html.in
+++ b/docs/auditlog.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Audit log</h1>

    <ul id="toc"></ul>

-    <h2><a name="intro">Introduction</a></h2>
+    <h2><a id="intro">Introduction</a></h2>

    <p>
      A number of the libvirt virtualization drivers (QEMU/KVM and LXC) include
@@ -17,7 +17,7 @@
      the logs will usually end up in <code>/var/log/audit/audit.log</code>
    </p>

-    <h2><a name="config">Configuration</a></h2>
+    <h2><a id="config">Configuration</a></h2>

    <p>
      The libvirt audit integration is enabled by default on any host which has
@@ -48,7 +48,7 @@
      mentioned above.
    </p>

-    <h2><a name="types">Message types</a></h2>
+    <h2><a id="types">Message types</a></h2>

    <p>
      Libvirt defines three core audit message types each of which will
@@ -90,7 +90,7 @@
      <dd>Result of the action, either <code>success</code> or <code>failed</code></dd>
    </dl>

-    <h3><a name="typecontrol">VIRT_CONTROL</a></h3>
+    <h3><a id="typecontrol">VIRT_CONTROL</a></h3>

    <p>
      Reports change in the lifecycle state of a virtual machine. The <code>msg</code>
@@ -110,7 +110,7 @@
      <dd>Namespace ID of the <code>init</code> process in a container. Only if <code>op=init</code> and <code>virt=lxc</code></dd>
    </dl>

-    <h3><a name="typemachine">VIRT_MACHINE_ID</a></h3>
+    <h3><a id="typemachine">VIRT_MACHINE_ID</a></h3>

    <p>
      Reports the association of a security context with a guest. The <code>msg</code>
@@ -126,7 +126,7 @@
      <dd>Security context for the guest disk images and other assigned host resources</dd>
    </dl>

-    <h3><a name="typeresource">VIRT_RESOURCE</a></h3>
+    <h3><a id="typeresource">VIRT_RESOURCE</a></h3>

    <p>
      Reports the usage of a host resource by a guest. The fields include will
@@ -137,7 +137,7 @@
      be generated.
    </p>

-    <h4><a name="typeresourcevcpu">Virtual CPU</a></h4>
+    <h4><a id="typeresourcevcpu">Virtual CPU</a></h4>

    <p>
      The <code>msg</code> field will include the following sub-fields
@@ -155,7 +155,7 @@
    </dl>


-    <h4><a name="typeresourcemem">Memory</a></h4>
+    <h4><a id="typeresourcemem">Memory</a></h4>

    <p>
      The <code>msg</code> field will include the following sub-fields
@@ -172,7 +172,7 @@
      <dd>Updated memory size in bytes</dd>
    </dl>

-    <h4><a name="typeresourcedisk">Disk</a></h4>
+    <h4><a id="typeresourcedisk">Disk</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -188,7 +188,7 @@
      <dd>Updated host file or device path acting as the disk backing file</dd>
    </dl>

-    <h4><a name="typeresourcenic">Network interface</a></h4>
+    <h4><a id="typeresourcenic">Network interface</a></h4>

    <p>
      The <code>msg</code> field will include the following sub-fields
@@ -221,7 +221,7 @@
      <dd>Name of the host network interface</dd>
    </dl>

-    <h4><a name="typeresourcefs">Filesystem</a></h4>
+    <h4><a id="typeresourcefs">Filesystem</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -237,7 +237,7 @@
      <dd>Updated host directory, file or device path backing the filesystem</dd>
    </dl>

-    <h4><a name="typeresourcehost">Host device</a></h4>
+    <h4><a id="typeresourcehost">Host device</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -255,7 +255,7 @@
      <dd>The path of the character device assigned to the guest, if <code>resrc=hostdev</code></dd>
    </dl>

-    <h4><a name="typeresourcetpm">TPM</a></h4>
+    <h4><a id="typeresourcetpm">TPM</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -269,7 +269,7 @@
      <dd>The path of the host TPM device assigned to the guest</dd>
    </dl>

-    <h4><a name="typeresourcerng">RNG</a></h4>
+    <h4><a id="typeresourcerng">RNG</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -285,7 +285,7 @@
      <dd>Updated path of the host entropy source for the RNG</dd>
    </dl>

-    <h4><a name="typeresourcechardev">console/serial/parallel/channel</a></h4>
+    <h4><a id="typeresourcechardev">console/serial/parallel/channel</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -301,7 +301,7 @@
      <dd>Updated path of the backing character device for given emulated device</dd>
    </dl>

-    <h4><a name="typeresourcesmartcard">smartcard</a></h4>
+    <h4><a id="typeresourcesmartcard">smartcard</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -321,7 +321,7 @@
      </dd>
    </dl>

-    <h4><a name="typeresourceredir">Redirected device</a></h4>
+    <h4><a id="typeresourceredir">Redirected device</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
@@ -337,7 +337,7 @@
      <dd>The device type, only <code>USB redir</code> allowed</dd>
    </dl>

-    <h4><a name="typeresourcecgroup">Control group</a></h4>
+    <h4><a id="typeresourcecgroup">Control group</a></h4>

    <p>
      The <code>msg</code> field will include the following sub-fields
@@ -353,7 +353,7 @@
    </dl>


-    <h4><a name="typeresourceshmem">Shared memory</a></h4>
+    <h4><a id="typeresourceshmem">Shared memory</a></h4>
    <p>
      The <code>msg</code> field will include the following sub-fields
    </p>
--- a/docs/auth.html.in
+++ b/docs/auth.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Connection authentication</h1>
@@ -14,7 +14,7 @@

    <ul id="toc"></ul>

-    <h2><a name="Auth_client_config">Client configuration</a></h2>
+    <h2><a id="Auth_client_config">Client configuration</a></h2>

    <p>
      When connecting to a remote hypervisor which requires authentication,
@@ -142,7 +142,7 @@ credentials=defgrp</pre>
      to storage VNC or SPICE login credentials
    </p>

-    <h2><a name="ACL_server_config">Server configuration</a></h2>
+    <h2><a id="ACL_server_config">Server configuration</a></h2>
    <p>
 The libvirt daemon allows the administrator to choose the authentication
 mechanisms used for client connections on each network socket independently.
@@ -153,7 +153,7 @@ currently a choice of <code>none</code>, <code>polkit</code>, and <code>sasl</co
 The SASL scheme can be further configured to choose between a large
 number of different mechanisms.
 </p>
-    <h2><a name="ACL_server_unix_perms">UNIX socket permissions/group</a></h2>
+    <h2><a id="ACL_server_unix_perms">UNIX socket permissions/group</a></h2>
    <p>
 If libvirt does not contain support for PolicyKit, then access control for
 the UNIX domain socket is done using traditional file user/group ownership
@@ -170,7 +170,7 @@ parameter. For example, setting the former to mode <code>0770</code> and the
 latter <code>wheel</code> would let any user in the wheel group connect to
 the libvirt daemon.
 </p>
-    <h2><a name="ACL_server_polkit">UNIX socket PolicyKit auth</a></h2>
+    <h2><a id="ACL_server_polkit">UNIX socket PolicyKit auth</a></h2>
    <p>
 If libvirt contains support for PolicyKit, then access control options are
 more advanced. The <code>auth_unix_rw</code> parameter will default to
@@ -204,7 +204,7 @@ ResultActive=yes</pre>
 Further examples of PolicyKit setup can be found on the
 <a href="http://wiki.libvirt.org/page/SSHPolicyKitSetup">wiki page</a>.
    </p>
-    <h2><a name="ACL_server_sasl">SASL pluggable authentication</a></h2>
+    <h2><a id="ACL_server_sasl">SASL pluggable authentication</a></h2>

    <p>
 Libvirt integrates with the cyrus-sasl library to provide a pluggable authentication
@@ -255,7 +255,7 @@ GSSAPI plugin is considered acceptably secure by modern standards:
      TLS or UNIX socket listeners.
    </p>

-    <h3><a name="ACL_server_username">Username/password auth</a></h3>
+    <h3><a id="ACL_server_username">Username/password auth</a></h3>
    <p>
 As noted above, the DIGEST-MD5 mechanism is considered obsolete and should
 not be used anymore. To provide a simple username/password auth scheme on
@@ -297,7 +297,7 @@ again:
    <pre>
 # saslpasswd2 -a libvirt -d fred
 </pre>
-    <h3><a name="ACL_server_kerberos">GSSAPI/Kerberos auth</a></h3>
+    <h3><a id="ACL_server_kerberos">GSSAPI/Kerberos auth</a></h3>
    <p>
 The plain TCP listener of the libvirt daemon defaults to using SASL for authentication.
 The libvirt SASL config also defaults to GSSAPI, so there is no need to edit the
--- a/docs/bindings.html.in
+++ b/docs/bindings.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1 >Bindings for other languages</h1>
--- a/docs/browserconfig.xml
+++ b/docs/browserconfig.xml
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="utf-8"?>
+<browserconfig>
+    <msapplication>
+        <tile>
+            <square150x150logo src="/mstile-150x150.png"/>
+            <TileColor>#b91d47</TileColor>
+        </tile>
+    </msapplication>
+</browserconfig>
--- a/docs/bugs.html.in
+++ b/docs/bugs.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>

@@ -7,7 +7,7 @@

    <ul id="toc"></ul>

-    <h2><a name="security">Security Issues</a></h2>
+    <h2><a id="security">Security Issues</a></h2>

    <p>
      If you think that an issue with libvirt may have security
@@ -19,7 +19,7 @@
      <a href="securityprocess.html">security process</a> instead.
    </p>

-    <h2><a name="bugzilla">Bug Tracking</a></h2>
+    <h2><a id="bugzilla">Bug Tracking</a></h2>

    <p>
      If you are using libvirt binaries from a Linux distribution
@@ -27,7 +27,7 @@
      first.
    </p>

-    <h2><a name="general">General libvirt bug reports</a></h2>
+    <h2><a id="general">General libvirt bug reports</a></h2>

    <p>
      The <a href="http://bugzilla.redhat.com">Red Hat Bugzilla Server</a>
@@ -69,7 +69,7 @@
      <li><a href="http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Virtualization%20Tools&amp;component=libvirt">New libvirt ticket</a></li>
    </ul>

-    <h2><a name="distribution">Linux Distribution specific bug reports</a></h2>
+    <h2><a id="distribution">Linux Distribution specific bug reports</a></h2>
    <ul>
      <li>
        If you are using binaries from <strong>Fedora</strong>, enter
@@ -107,7 +107,7 @@
    </ul>


-    <h2><a name="quality">How to file high quality bug reports</a></h2>
+    <h2><a id="quality">How to file high quality bug reports</a></h2>

    <p>
      To increase the likelihood of your bug report being addressed it is
--- a/docs/cgroups.html.in
+++ b/docs/cgroups.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Control Groups Resource Management</h1>
@@ -11,7 +11,7 @@
      for applying resource management to their virtual machines and containers.
    </p>

-    <h2><a name="requiredControllers">Required controllers</a></h2>
+    <h2><a id="requiredControllers">Required controllers</a></h2>

    <p>
      The control groups filesystem supports multiple "controllers". By default
@@ -42,7 +42,7 @@
      which use them will cease to operate.
    </p>

-    <h2><a name="currentLayout">Current cgroups layout</a></h2>
+    <h2><a id="currentLayout">Current cgroups layout</a></h2>

    <p>
      As of libvirt 1.0.5 or later, the cgroups layout created by libvirt has been
@@ -63,14 +63,14 @@
      in two, one describing systemd hosts and the other non-systemd hosts.
    </p>

-    <h3><a name="currentLayoutSystemd">Systemd cgroups integration</a></h3>
+    <h3><a id="currentLayoutSystemd">Systemd cgroups integration</a></h3>

    <p>
      On hosts which use systemd, each consumer maps to a systemd scope unit,
      while partitions map to a system slice unit.
    </p>

-    <h4><a name="systemdScope">Systemd scope naming</a></h4>
+    <h4><a id="systemdScope">Systemd scope naming</a></h4>

    <p>
      The systemd convention is for the scope name of virtual machines / containers
@@ -83,7 +83,7 @@
      The scope names map directly to the cgroup directory names.
    </p>

-    <h4><a name="systemdSlice">Systemd slice naming</a></h4>
+    <h4><a id="systemdSlice">Systemd slice naming</a></h4>

    <p>
      The systemd convention for slice naming is that a slice should include the
@@ -96,7 +96,7 @@
      by libvirt will be associated with <code>machine.slice</code> by default.
    </p>

-    <h4><a name="systemdLayout">Systemd cgroup layout</a></h4>
+    <h4><a id="systemdLayout">Systemd cgroup layout</a></h4>

    <p>
      Given this, a possible systemd cgroups layout involving 3 qemu guests,
@@ -145,7 +145,7 @@ $ROOT
          +- machine-lxc\x2dcontainer3.scope
    </pre>

-    <h3><a name="currentLayoutGeneric">Non-systemd cgroups layout</a></h3>
+    <h3><a id="currentLayoutGeneric">Non-systemd cgroups layout</a></h3>

    <p>
      On hosts which do not use systemd, each consumer has a corresponding cgroup
@@ -206,7 +206,7 @@ $ROOT
          +- container3.libvirt-lxc
    </pre>

-    <h2><a name="customPartiton">Using custom partitions</a></h2>
+    <h2><a id="customPartiton">Using custom partitions</a></h2>

    <p>
      If there is a need to apply resource constraints to groups of
@@ -255,7 +255,7 @@ $ROOT
      later in this document did not support customization per guest.
    </p>

-    <h3><a name="createSystemd">Creating custom partitions (systemd)</a></h3>
+    <h3><a id="createSystemd">Creating custom partitions (systemd)</a></h3>

    <p>
      Given the XML config above, the admin on a systemd based host would
@@ -272,7 +272,7 @@ EOF
 # systemctl start machine-testing.slice
    </pre>

-    <h3><a name="createNonSystemd">Creating custom partitions (non-systemd)</a></h3>
+    <h3><a id="createNonSystemd">Creating custom partitions (non-systemd)</a></h3>

    <p>
      Given the XML config above, the admin on a non-systemd based host
@@ -291,7 +291,7 @@ EOF
  done
 </pre>

-    <h2><a name="resourceAPIs">Resource management APIs/commands</a></h2>
+    <h2><a id="resourceAPIs">Resource management APIs/commands</a></h2>

    <p>
      Since libvirt aims to provide an API which is portable across
@@ -354,7 +354,7 @@ swap_hard_limit: unlimited
      network interfaces.
    </p>

-    <h2><a name="legacyLayout">Legacy cgroups layout</a></h2>
+    <h2><a id="legacyLayout">Legacy cgroups layout</a></h2>

    <p>
      Prior to libvirt 1.0.5, the cgroups layout created by libvirt was different
--- a/docs/compiling.html.in
+++ b/docs/compiling.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
-    <h1><a name="installation">libvirt Installation</a></h1>
+    <h1><a id="installation">libvirt Installation</a></h1>

    <ul id="toc"></ul>

-    <h2><a name="compiling">Compiling a release tarball</a></h2>
+    <h2><a id="compiling">Compiling a release tarball</a></h2>

    <p>
      libvirt uses the standard configure/make/install steps:
@@ -58,7 +58,7 @@ $ <b>sudo</b> <i>make install</i></pre>
      to update your list of installed shared libs.
    </p>

-    <h2><a name="building">Building from a GIT checkout</a></h2>
+    <h2><a id="building">Building from a GIT checkout</a></h2>

    <p>
      The libvirt build process uses GNU autotools, so after obtaining a
--- a/docs/contact.html.in
+++ b/docs/contact.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Contacting the project contributors</h1>

    <ul id="toc"></ul>

-    <h2><a name="security">Security Issues</a></h2>
+    <h2><a id="security">Security Issues</a></h2>

    <p>
      If you think that an issue with libvirt may have security
@@ -18,7 +18,7 @@
      <a href="securityprocess.html">security process</a> instead.
    </p>

-    <h2><a name="email">Mailing lists</a></h2>
+    <h2><a id="email">Mailing lists</a></h2>

    <p>
      There are three mailing-lists:
@@ -95,7 +95,7 @@
      page.
    </p>

-    <h2><a name="irc">IRC discussion</a></h2>
+    <h2><a id="irc">IRC discussion</a></h2>

    <p>
      Some of the libvirt developers may be found on IRC on the <a href="http://oftc.net">OFTC IRC</a>
--- a/docs/contribute.html.in
+++ b/docs/contribute.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Contributing to libvirt</h1>
@@ -11,7 +11,7 @@

    <ul id="toc"></ul>

-    <h2><a name="skills">Contributions required</a></h2>
+    <h2><a id="skills">Contributions required</a></h2>

    <p>
      The libvirt project is always looking for new contributors to
@@ -97,7 +97,7 @@
        these help forums.</li>
    </ul>

-    <h2><a name="comms">Communication</a></h2>
+    <h2><a id="comms">Communication</a></h2>

    <p>
      For full details on contacting other project contributors
@@ -106,7 +106,7 @@
      between contributors:
    </p>

-    <h3><a name="email">Mailing lists</a></h3>
+    <h3><a id="email">Mailing lists</a></h3>

    <p>
      The project has a number of
@@ -118,7 +118,7 @@
      to follow the traffic.
    </p>

-    <h3><a name="irc">Instant messaging / chat</a></h3>
+    <h3><a id="irc">Instant messaging / chat</a></h3>

    <p>
      Contributors to libvirt are encouraged to join the
@@ -127,7 +127,7 @@
      with others members.
    </p>

-    <h2><a name="outreach">Student / outreach coding programs</a></h2>
+    <h2><a id="outreach">Student / outreach coding programs</a></h2>

    <p>
      Since 2016, the libvirt project directly participates as an
--- a/docs/csharp.html.in
+++ b/docs/csharp.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>C# API bindings</h1>

    <ul id="toc"></ul>

-    <h2><a name="description">Description</a></h2>
+    <h2><a id="description">Description</a></h2>

    <p>
      The C# libvirt bindings are a class library.  They use a Microsoft
@@ -19,9 +19,7 @@
      to libvirt.
    </p>

-    <p>&nbsp;</p>
-
-    <h2><a name="requirements">Requirements</a></h2>
+    <h2><a id="requirements">Requirements</a></h2>

    <p>
      These bindings depend upon the libvirt libraries being installed.
@@ -31,10 +29,8 @@
      compiling libvirt for windows.
    </p>

-    <p>&nbsp;</p>
-
 <!-- 2010-10-19 JC: Commented out until we have C# tarballs to download
-    <h2><a name="getting">Getting them</a></h2>
+    <h2><a id="getting">Getting them</a></h2>

    <p>
      The latest versions of the libvirt C# bindings can be downloaded from:
@@ -46,7 +42,7 @@
    </ul>
 -->

-    <h2><a name="git">GIT source repository</a></h2>
+    <h2><a id="git">GIT source repository</a></h2>
    <p>
      The C# bindings source code is maintained in a <a
      href="http://git-scm.com/">git</a> repository available on
@@ -65,9 +61,7 @@ git clone git://libvirt.org/libvirt-csharp.git
 <a href="http://libvirt.org/git/?p=libvirt-csharp.git;a=summary">http://libvirt.org/git/?p=libvirt-csharp.git;a=summary</a>
 </pre>

-    <p>&nbsp;</p>
-
-    <h2><a name="usage">Usage</a></h2>
+    <h2><a id="usage">Usage</a></h2>

    <p>
      The libvirt C# bindings class library exposes the <b>Libvirt</b>
@@ -116,19 +110,15 @@ git clone git://libvirt.org/libvirt-csharp.git
      </li>
    </ul>

-    <p>&nbsp;</p>
-
-    <h2><a name="authors">Authors</a></h2>
+    <h2><a id="authors">Authors</a></h2>

    <p>
      The C# bindings are the work of Arnaud Champion
      &lt;<a href="mailto:arnaud.champion AT devatom.fr">arnaud.champion AT devatom.fr</a>&gt;,
-      based upon the previous work of Jarom&iacute;r &#x010C;ervenka.
+      based upon the previous work of Jaromír Červenka.
    </p>

-    <p>&nbsp;</p>
-
-    <h2><a name="notes">Test Configuration</a></h2>
+    <h2><a id="notes">Test Configuration</a></h2>

    <p>
      Testing is performed using the following configurations:
@@ -139,87 +129,85 @@ git clone git://libvirt.org/libvirt-csharp.git
      <li>Ubuntu 10.10 amd64 / Mono 2.6.7 (compiled in 64 bits)</li>
    </ul>

-    <p>&nbsp;</p>
-
-    <h2><a name="type">Type Coverage</a></h2>
+    <h2><a id="type">Type Coverage</a></h2>

    <p>
      Coverage of the libvirt types is:
    </p>
    <table class="top_table">
      <tr><th>Type</th><th>Name</th><th>Binding?</th><th>Tested?</th><th>Sample Code?</th><th>Works?</th><th>Tested .Net/Windows Works?</th><th>Tested Mono (32-bit)/Windows Works?</th><th>Tested Mono (64-bit)/Linux Works?</th></tr>
-      <tr><td>enum</td><td>virCPUCompareResult</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virConnect</td><td>Yes, an IntPtr as the struct is not public</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>enum</td><td>virCPUCompareResult</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virConnect</td><td>Yes, an IntPtr as the struct is not public</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
      <tr><td>struct</td><td>virConnectAuth</td><td>Yes</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>struct</td><td>virConnectCredential</td><td>Yes</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>enum</td><td>virConnectCredentialType</td><td>Yes</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>enum</td><td>virConnectFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virDomain</td><td>Yes, an IntPtr as the struct is not public</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virDomainBlockInfo</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>enum</td><td>virConnectFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virDomain</td><td>Yes, an IntPtr as the struct is not public</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virDomainBlockInfo</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>struct</td><td>virDomainBlockStatsInfo</td><td>Yes</td><td>Yes</td><td>virDomainStats</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>enum</td><td>virDomainCoreDumpFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainCreateFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainDeviceModifyFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>enum</td><td>virDomainCoreDumpFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainCreateFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainDeviceModifyFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>enum</td><td>virDomainEventDefinedDetailType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>struct</td><td>virDomainEventGraphicsAddress</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainEventGraphicsAddressType</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainEventGraphicsPhase</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virDomainEventGraphicsSubject</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virDomainEventGraphicsSubjectIdentity</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainEventID</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainEventIOErrorAction</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>struct</td><td>virDomainEventGraphicsAddress</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainEventGraphicsAddressType</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainEventGraphicsPhase</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virDomainEventGraphicsSubject</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virDomainEventGraphicsSubjectIdentity</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainEventID</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainEventIOErrorAction</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>enum</td><td>virDomainEventResumedDetailType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>enum</td><td>virDomainEventStartedDetailType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>enum</td><td>virDomainEventStoppedDetailType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>enum</td><td>virDomainEventSuspendedDetailType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>enum</td><td>virDomainEventType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>enum</td><td>virDomainEventUndefinedDetailType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>enum</td><td>virDomainEventWatchdogAction</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>enum</td><td>virDomainEventWatchdogAction</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>struct</td><td>virDomainInfo</td><td>Yes</td><td>Yes</td><td>virConnectSetErrorFunc, virDomainStats</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>struct</td><td>virDomainInterfaceStatsStruct</td><td>Yes</td><td>Yes</td><td>virDomainStats</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>struct</td><td>virDomainJobInfo</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainJobType</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainMemoryFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virDomainMemoryStatStruct</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainMemoryStatTags</td><td>Yes</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainMigrateFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virDomainSnapshot</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainSnapshotDeleteFlags</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainState</td><td>Yes</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virDomainXMLFlags</td><td>Yes</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>struct</td><td>virDomainJobInfo</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainJobType</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainMemoryFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virDomainMemoryStatStruct</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainMemoryStatTags</td><td>Yes</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainMigrateFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virDomainSnapshot</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainSnapshotDeleteFlags</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainState</td><td>Yes</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virDomainXMLFlags</td><td>Yes</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
      <tr><td>enum</td><td>virEventHandleType</td><td>Yes</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>struct</td><td>virInterface</td><td>Yes, an IntPtr as the struct is not public</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virInterfaceXMLFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virNWFilter</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virNetwork</td><td>Yes, an IntPtr as the struct is not public</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virNodeDevice</td><td>Yes, an IntPtr as the struct is not public</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virNodeInfo</td><td>Yes</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virSchedParameter</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virSchedParameterType</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virSecret</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virSecretUsageType</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virSecurityLabel</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virSecurityModel</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virStoragePoolBuildFlags</td><td>Yes</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virStoragePoolDeleteFlags</td><td>Yes</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virStoragePoolInfo</td><td>Yes</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virStoragePool</td><td>Yes, an IntPtr as the struct is not public</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virStoragePoolState</td><td>Yes</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virStorageVol</td><td>Yes, an IntPtr as the struct is not public</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virStorageVolDeleteFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virStorageVolInfo</td><td>Yes</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virStorageVolType</td><td>Yes</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virStream</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virStreamEventType</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virStreamFlags</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>struct</td><td>virVcpuInfo</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>enum</td><td>virVcpuState</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>struct</td><td>virInterface</td><td>Yes, an IntPtr as the struct is not public</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virInterfaceXMLFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virNWFilter</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virNetwork</td><td>Yes, an IntPtr as the struct is not public</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virNodeDevice</td><td>Yes, an IntPtr as the struct is not public</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virNodeInfo</td><td>Yes</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virSchedParameter</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virSchedParameterType</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virSecret</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virSecretUsageType</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virSecurityLabel</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virSecurityModel</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virStoragePoolBuildFlags</td><td>Yes</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virStoragePoolDeleteFlags</td><td>Yes</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virStoragePoolInfo</td><td>Yes</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virStoragePool</td><td>Yes, an IntPtr as the struct is not public</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virStoragePoolState</td><td>Yes</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virStorageVol</td><td>Yes, an IntPtr as the struct is not public</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virStorageVolDeleteFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virStorageVolInfo</td><td>Yes</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virStorageVolType</td><td>Yes</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virStream</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virStreamEventType</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virStreamFlags</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>struct</td><td>virVcpuInfo</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>enum</td><td>virVcpuState</td><td>No</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>struct</td><td>virError</td><td>Yes</td><td>Yes</td><td>virConnectSetErrorFunc, virDomainStats</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
    </table>

-    <p>&nbsp;</p>
+    <p></p>

-    <h2><a name="funccover">Function Coverage</a></h2>
+    <h2><a id="funccover">Function Coverage</a></h2>

    <p>
      Coverage of the libvirt functions is:
@@ -227,274 +215,274 @@ git clone git://libvirt.org/libvirt-csharp.git
    <table class="top_table">
      <tr><th>Name</th><th>Binding?</th><th>Type?</th><th>Tested?</th><th>Sample Code?</th><th>Working?</th><th>Tested .Net/Windows Works?</th><th>Tested Mono (32-bit)/Windows Works?</th><th>Tested Mono (64-bit)/Linux Works?</th></tr>
      <tr><td>virConnectAuthCallback</td><td>Yes</td><td>delegate</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectBaselineCPU</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectBaselineCPU</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>virConnectClose</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectCompareCPU</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventCallback</td><td>Yes</td><td>delegate</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventDeregister</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventDeregisterAny</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventGenericCallback</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventGraphicsCallback</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventIOErrorCallback</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventIOErrorReasonCallback</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventRTCChangeCallback</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectCompareCPU</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventCallback</td><td>Yes</td><td>delegate</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventDeregister</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventDeregisterAny</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventGenericCallback</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventGraphicsCallback</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventIOErrorCallback</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventIOErrorReasonCallback</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventRTCChangeCallback</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>virConnectDomainEventRegister</td><td>Yes</td><td>function</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectDomainEventRegisterAny</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainEventWatchdogCallback</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainXMLFromNative</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectDomainXMLToNative</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectFindStoragePoolSources</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectGetCapabilities</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectGetHostname</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectGetLibVersion</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectGetMaxVcpus</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectGetType</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectGetURI</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectGetVersion</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectIsEncrypted</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectIsSecure</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectDomainEventRegisterAny</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainEventWatchdogCallback</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainXMLFromNative</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectDomainXMLToNative</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectFindStoragePoolSources</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectGetCapabilities</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectGetHostname</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectGetLibVersion</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectGetMaxVcpus</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectGetType</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectGetURI</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectGetVersion</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectIsEncrypted</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectIsSecure</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
      <tr><td>virConnectListDefinedDomains</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectListDefinedInterfaces </td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectListDefinedNetworks</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectListDefinedStoragePools</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectListDefinedInterfaces </td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectListDefinedNetworks</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectListDefinedStoragePools</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
      <tr><td>virConnectListDomains</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth, virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectListInterfaces</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes, if the host handle the method</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectListNWFilters </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectListNetworks</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectListSecrets</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectListInterfaces</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes, if the host handle the method</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectListNWFilters </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectListNetworks</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectListSecrets</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
      <tr><td>virConnectListStoragePools</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpen</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>virConnectNumOfDefinedDomains</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectNumOfDefinedInterfaces</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectNumOfDefinedNetworks</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectNumOfDefinedStoragePools</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectNumOfDefinedInterfaces</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectNumOfDefinedNetworks</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectNumOfDefinedStoragePools</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
      <tr><td>virConnectNumOfDomains</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth, virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectNumOfInterfaces</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectNumOfNWFilters</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectNumOfNetworks </td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectNumOfSecrets</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectNumOfInterfaces</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectNumOfNWFilters</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectNumOfNetworks </td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectNumOfSecrets</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
      <tr><td>virConnectNumOfStoragePools</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpen</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>virConnectOpen</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpen, virEventRegisterImpl, virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>virConnectOpenAuth</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virConnectOpenReadOnly</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virConnectRef</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainAbortJob</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainAttachDevice</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainAttachDeviceFlags</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainBlockPeek</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virConnectOpenReadOnly</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virConnectRef</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainAbortJob</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainAttachDevice</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainAttachDeviceFlags</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainBlockPeek</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>virDomainBlockStats</td><td>Yes</td><td>function</td><td>Yes</td><td>virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virDomainCoreDump</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainCreate</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainCreateLinux</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainCreateWithFlags</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainCreateXML</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainDefineXML</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainDestroy</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainDetachDevice</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainDetachDeviceFlags</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainFree</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetAutostart</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetBlockInfo</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetConnect</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetID</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virDomainCoreDump</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainCreate</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainCreateLinux</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainCreateWithFlags</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainCreateXML</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainDefineXML</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainDestroy</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainDetachDevice</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainDetachDeviceFlags</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainFree</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetAutostart</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetBlockInfo</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetConnect</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetID</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
      <tr><td>virDomainGetInfo</td><td>Yes</td><td>function</td><td>Yes</td><td>virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virDomainGetJobInfo</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetMaxMemory</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetMaxVcpus</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virDomainGetJobInfo</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetMaxMemory</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetMaxVcpus</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
      <tr><td>virDomainGetName</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth, virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virDomainGetOSType</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetSchedulerParameters</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetSchedulerType</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetSecurityLabel</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetUUID</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetUUIDString</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainGetVcpus</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virDomainGetOSType</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetSchedulerParameters</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetSchedulerType</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetSecurityLabel</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetUUID</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetUUIDString</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainGetVcpus</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>virDomainGetXMLDesc</td><td>Yes</td><td>function</td><td>Yes</td><td>virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virDomainHasCurrentSnapshot</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainHasManagedSaveImage</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virDomainHasCurrentSnapshot</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainHasManagedSaveImage</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>virDomainInterfaceStats </td><td>No</td><td>function</td><td>Yes</td><td>virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virDomainIsActive</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainIsPersistent</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virDomainIsActive</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainIsPersistent</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
      <tr><td>virDomainLookupByID</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectOpenAuth, virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>virDomainLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td>virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virDomainLookupByUUID</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainLookupByUUIDString</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainManagedSave    </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainManagedSaveRemove</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainMemoryPeek</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainMemoryStats</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainMigrate</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainMigrateSetMaxDowntime</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainMigrateToURI   </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainPinVcpu</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainReboot</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainRef    </td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainRestore</td><td>Yes </td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainResume </td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainRevertToSnapshot</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSave</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSetAutostart</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSetMaxMemory   </td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSetMemory</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSetSchedulerParameters</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSetVcpus</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainShutdown</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotCreateXML</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotCurrent</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotDelete</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotFree</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotGetXMLDesc</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotListNames</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotLookupByName</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSnapshotNum</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainSuspend</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainUndefine</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virDomainUpdateDeviceFlags</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virEventAddHandleFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virEventAddTimeoutFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virDomainLookupByUUID</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainLookupByUUIDString</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainManagedSave    </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainManagedSaveRemove</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainMemoryPeek</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainMemoryStats</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainMigrate</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainMigrateSetMaxDowntime</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainMigrateToURI   </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainPinVcpu</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainReboot</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainRef    </td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainRestore</td><td>Yes </td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainResume </td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainRevertToSnapshot</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSave</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSetAutostart</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSetMaxMemory   </td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSetMemory</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSetSchedulerParameters</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSetVcpus</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainShutdown</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotCreateXML</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotCurrent</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotDelete</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotFree</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotGetXMLDesc</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotListNames</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotLookupByName</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSnapshotNum</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainSuspend</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainUndefine</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virDomainUpdateDeviceFlags</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virEventAddHandleFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virEventAddTimeoutFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
      <tr><td>virEventHandleCallback</td><td>Yes</td><td>delegate</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>virEventRegisterImpl</td><td>Yes</td><td>function</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virEventRemoveHandleFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virEventRemoveTimeoutFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virEventRemoveHandleFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virEventRemoveTimeoutFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
      <tr><td>virEventTimeoutCallback</td><td>Yes</td><td>delegate</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virEventUpdateHandleFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virEventUpdateTimeoutFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virEventUpdateHandleFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virEventUpdateTimeoutFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
      <tr><td>virFreeCallback</td><td>Yes</td><td>function</td><td>Yes</td><td>virEventRegisterImpl</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
-      <tr><td>virGetVersion</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInitialize</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceCreate</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceDefineXML</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceDestroy</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceFree</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceGetConnect</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceGetMACString</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceGetName</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceGetXMLDesc</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceIsActive</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceLookupByMACString</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceLookupByName</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceRef </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virInterfaceUndefine</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterDefineXML</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterFree</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterGetName</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterGetUUID</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterGetUUIDString</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterGetXMLDesc</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterLookupByName </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterLookupByUUID</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterLookupByUUIDString</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterRef  </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNWFilterUndefine</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkCreate</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkCreateXML</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkDefineXML</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkDestroy</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkFree</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkGetAutostart</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkGetBridgeName</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkGetConnect</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkGetName</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkGetUUID</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkGetUUIDString </td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkGetXMLDesc</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkIsActive</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkIsPersistent</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkLookupByUUID</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkLookupByUUIDString</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkRef</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkSetAutostart</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNetworkUndefine</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceCreateXML</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceDestroy</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceDettach</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceFree</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceGetName</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceGetParent</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceGetXMLDesc</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceListCaps</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceNumOfCaps</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceReAttach</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceRef</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeDeviceReset</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeGetCellsFreeMemory</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeGetFreeMemory</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeGetInfo</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeGetSecurityModel </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeListDevices</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virNodeNumOfDevices</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretDefineXML</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretFree   </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretGetConnect</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretGetUUID</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretGetUUIDString  </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretGetUsageID</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretGetUsageType</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretGetValue</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretGetXMLDesc</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretLookupByUUID</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretLookupByUUIDString</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretLookupByUsage</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretRef</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretSetValue</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virSecretUndefine</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolBuild</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolCreate</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolCreateXML </td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolDefineXML</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolDelete</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolDestroy</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolFree</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolGetAutostart</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolGetConnect</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolGetInfo</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolGetName</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolGetUUID</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolGetUUIDString</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolGetXMLDesc</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolIsActive</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolIsPersistent</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolListVolumes</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolLookupByUUID</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolLookupByUUIDString</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolLookupByVolume</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolNumOfVolumes</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolRef</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolRefresh</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolSetAutostart</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStoragePoolUndefine</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolCreateXML</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolCreateXMLFrom</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolDelete</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolFree</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolGetConnect  </td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>Maybe</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolGetInfo</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolGetKey</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolGetName</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolGetPath</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolGetXMLDesc </td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolLookupByKey</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolLookupByPath</td><td>Yes</td><td>function</td><td>Yes</td><td>&nbsp;</td><td>Yes</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolRef</td><td>Yes</td><td>function</td><td>No</td><td>&nbsp;</td><td>No</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStorageVolWipe</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamAbort  </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamEventAddCallback</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamEventCallback</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamEventRemoveCallback</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamEventUpdateCallback</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamFinish </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamFree   </td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamNew</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamRecv</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamRecvAll</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamRef</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamSend</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamSendAll</td><td>No</td><td>function</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamSinkFunc</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
-      <tr><td>virStreamSourceFunc</td><td>No</td><td>delegate</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
+      <tr><td>virGetVersion</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virInitialize</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceCreate</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceDefineXML</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceDestroy</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceFree</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceGetConnect</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceGetMACString</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceGetName</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceGetXMLDesc</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceIsActive</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceLookupByMACString</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceLookupByName</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceRef </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virInterfaceUndefine</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterDefineXML</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterFree</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterGetName</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterGetUUID</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterGetUUIDString</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterGetXMLDesc</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterLookupByName </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterLookupByUUID</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterLookupByUUIDString</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterRef  </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNWFilterUndefine</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkCreate</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkCreateXML</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkDefineXML</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkDestroy</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkFree</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkGetAutostart</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkGetBridgeName</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkGetConnect</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkGetName</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkGetUUID</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkGetUUIDString </td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkGetXMLDesc</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkIsActive</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkIsPersistent</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkLookupByUUID</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkLookupByUUIDString</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkRef</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkSetAutostart</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNetworkUndefine</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceCreateXML</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceDestroy</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceDettach</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceFree</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceGetName</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceGetParent</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceGetXMLDesc</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceListCaps</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceNumOfCaps</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceReAttach</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceRef</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeDeviceReset</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeGetCellsFreeMemory</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeGetFreeMemory</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeGetInfo</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeGetSecurityModel </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeListDevices</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virNodeNumOfDevices</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretDefineXML</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretFree   </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretGetConnect</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretGetUUID</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretGetUUIDString  </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretGetUsageID</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretGetUsageType</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretGetValue</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretGetXMLDesc</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretLookupByUUID</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretLookupByUUIDString</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretLookupByUsage</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretRef</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretSetValue</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virSecretUndefine</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolBuild</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolCreate</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolCreateXML </td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolDefineXML</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolDelete</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolDestroy</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolFree</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolGetAutostart</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolGetConnect</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolGetInfo</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolGetName</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolGetUUID</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolGetUUIDString</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolGetXMLDesc</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolIsActive</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolIsPersistent</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolListVolumes</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolLookupByUUID</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolLookupByUUIDString</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolLookupByVolume</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolNumOfVolumes</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolRef</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolRefresh</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolSetAutostart</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStoragePoolUndefine</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolCreateXML</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolCreateXMLFrom</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolDelete</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolFree</td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolGetConnect  </td><td>Yes</td><td>function</td><td>No</td><td></td><td>Maybe</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolGetInfo</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolGetKey</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolGetName</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolGetPath</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolGetXMLDesc </td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolLookupByKey</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolLookupByName</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolLookupByPath</td><td>Yes</td><td>function</td><td>Yes</td><td></td><td>Yes</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolRef</td><td>Yes</td><td>function</td><td>No</td><td></td><td>No</td><td></td><td></td><td></td></tr>
+      <tr><td>virStorageVolWipe</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamAbort  </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamEventAddCallback</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamEventCallback</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamEventRemoveCallback</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamEventUpdateCallback</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamFinish </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamFree   </td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamNew</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamRecv</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamRecvAll</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamRef</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamSend</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamSendAll</td><td>No</td><td>function</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamSinkFunc</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
+      <tr><td>virStreamSourceFunc</td><td>No</td><td>delegate</td><td></td><td></td><td></td><td></td><td></td><td></td></tr>
      <tr><td>virGetLastError</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectSetErrorFunc</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>virConnSetErrorFunc</td><td>Yes</td><td>function</td><td>Yes</td><td>virConnectSetErrorFunc</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>virErrorFunc</td><td>Yes</td><td>delegate</td><td>Yes</td><td>virConnectSetErrorFunc, virDomainInfos</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr>
--- a/docs/devguide.html.in
+++ b/docs/devguide.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>libvirt Application Development Guides</h1>
--- a/docs/docs.html.in
+++ b/docs/docs.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body class="docs">
    <div class="panel">
--- a/docs/downloads.html.in
+++ b/docs/downloads.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Downloads</h1>

    <ul id="toc"></ul>

-    <h2><a name="releases">Project modules</a></h2>
+    <h2><a id="releases">Project modules</a></h2>

    <p>
      The libvirt project maintains a number of inter-related modules beyond
@@ -435,7 +435,7 @@
      <li><a href="https://libvirt.org/sources/">libvirt.org HTTPS server</a></li>
    </ul>

-    <h2><a name="hourly">Hourly development snapshots</a></h2>
+    <h2><a id="hourly">Hourly development snapshots</a></h2>

    <p>
      Once an hour, an automated snapshot is made from the git server
@@ -450,7 +450,7 @@
      <li><a href="http://libvirt.org/sources/libvirt-git-snapshot.tar.xz">libvirt.org HTTP server</a></li>
    </ul>

-    <h2><a name="schedule">Primary release schedule</a></h2>
+    <h2><a id="schedule">Primary release schedule</a></h2>

    <p>
      The core libvirt module follows a time based plan, with releases made
@@ -462,7 +462,7 @@
      independant ad-hoc releases with no fixed time schedle.
    </p>

-    <h2><a name="numbering">Release numbering</a></h2>
+    <h2><a id="numbering">Release numbering</a></h2>

    <p>
      Since libvirt 2.0.0, a time based version numbering rule
@@ -497,7 +497,7 @@
      digits.
    </p>

-    <h2><a name="maintenance">Maintenance releases</a></h2>
+    <h2><a id="maintenance">Maintenance releases</a></h2>
    <p>
      In the git repository are several stable maintenance branches
      for the core library, matching the
@@ -525,7 +525,7 @@
      wiki page</a>.
    </p>

-    <h2><a name="git">GIT source repository</a></h2>
+    <h2><a id="git">GIT source repository</a></h2>

    <p>
      All modules maintained by the libvirt project have their primary
--- a/docs/drivers.html.in
+++ b/docs/drivers.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Internal drivers</h1>
@@ -18,7 +18,7 @@
      network and storage driver active.
    </p>

-    <h2><a name="hypervisor">Hypervisor drivers</a></h2>
+    <h2><a id="hypervisor">Hypervisor drivers</a></h2>

    <p>
      The hypervisor drivers currently supported by libvirt are:
@@ -40,7 +40,7 @@
      <li><strong><a href="drvbhyve.html">Bhyve</a></strong> - The BSD Hypervisor</li>
    </ul>

-    <h2><a name="storage">Storage drivers</a></h2>
+    <h2><a id="storage">Storage drivers</a></h2>

    <ul>
      <li><strong><a href="storage.html#StorageBackendDir">Directory backend</a></strong></li>
--- a/docs/drvbhyve.html.in
+++ b/docs/drvbhyve.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Bhyve driver</h1>
@@ -31,7 +31,7 @@ $
 Additional information on bhyve could be obtained on <a href="http://bhyve.org/">bhyve.org</a>.
 </p>

-<h2><a name="uri">Connections to the Bhyve driver</a></h2>
+<h2><a id="uri">Connections to the Bhyve driver</a></h2>
 <p>
 The libvirt bhyve driver is a single-instance privileged driver. Some sample
 connection URIs are:
@@ -43,7 +43,7 @@ bhyve+unix:///system                (local access)
 bhyve+ssh://root@example.com/system (remote access, SSH tunnelled)
 </pre>

-<h2><a name="exconfig">Example guest domain XML configurations</a></h2>
+<h2><a id="exconfig">Example guest domain XML configurations</a></h2>

 <h3>Example config</h3>
 <p>
@@ -206,9 +206,9 @@ Note the addition of &lt;bootloader&gt;.

 <p>Please refer to the <a href="#uefi">UEFI</a> section for a more detailed explanation.</p>

-<h2><a name="usage">Guest usage / management</a></h2>
+<h2><a id="usage">Guest usage / management</a></h2>

-<h3><a name="console">Connecting to a guest console</a></h3>
+<h3><a id="console">Connecting to a guest console</a></h3>

 <p>
 Guest console connection is supported through the <code>nmdm</code> device. It could be enabled by adding
@@ -253,7 +253,7 @@ device) is:</p>

 <pre>cu -l /dev/nmdm0B</pre>

-<h3><a name="xmltonative">Converting from domain XML to Bhyve args</a></h3>
+<h3><a id="xmltonative">Converting from domain XML to Bhyve args</a></h3>

 <p>
 The <code>virsh domxml-to-native</code> command can preview the actual
@@ -275,7 +275,7 @@ tweak them.</p>
 /usr/sbin/bhyve -c 2 -m 214 -A -I -H -P -s 0:0,hostbridge -s 3:0,virtio-net,tap0,mac=52:54:00:5d:74:e3 -s 2:0,virtio-blk,/home/user/vm1.img -s 1,lpc -l com1,/dev/nmdm0A vm1
 </pre>

-<h3><a name="zfsvolume">Using ZFS volumes</a></h3>
+<h3><a id="zfsvolume">Using ZFS volumes</a></h3>

 <p>It's possible to use ZFS volumes as disk devices <span class="since">since 1.2.8</span>.
 An example of domain XML device entry for that will look like:</p>
@@ -291,7 +291,7 @@ An example of domain XML device entry for that will look like:</p>
 <p>Please refer to the <a href="storage.html">Storage documentation</a> for more details on storage
 management.</p>

-<h3><a name="grubbhyve">Using grub2-bhyve or Alternative Bootloaders</a></h3>
+<h3><a id="grubbhyve">Using grub2-bhyve or Alternative Bootloaders</a></h3>

 <p>It's possible to boot non-FreeBSD guests by specifying an explicit
 bootloader, e.g. <code>grub-bhyve(1)</code>. Arguments to the bootloader may be
@@ -312,7 +312,7 @@ attempt to boot from the first partition in the disk image.</p>
 <p>Caveat: <code>bootloader_args</code> does not support any quoting.
 Filenames, etc, must not have spaces or they will be tokenized incorrectly.</p>

-<h3><a name="uefi">Using UEFI bootrom, VNC, and USB tablet</a></h3>
+<h3><a id="uefi">Using UEFI bootrom, VNC, and USB tablet</a></h3>

 <p><span class="since">Since 3.2.0</span>, in addition to <a href="#grubbhyve">grub-bhyve</a>,
 non-FreeBSD guests could be also booted using an UEFI boot ROM, provided both guest OS and
@@ -381,7 +381,15 @@ will be used. Please refer to the
 manual page and the <a href="https://wiki.freebsd.org/bhyve">bhyve wiki</a> for more details on using
 the <code>vgaconf</code> option.</p>

-<h3><a name="clockconfig">Clock configuration</a></h3>
+<p><span class="since">Since 3.7.0</span>, it's possible to use <code>autoport</code>
+to let libvirt allocate VNC port automatically (instead of explicitly specifying
+it with the <code>port</code> attribute):</p>
+
+<pre>
+    &lt;graphics type='vnc' autoport='yes'&gt;
+</pre>
+
+<h3><a id="clockconfig">Clock configuration</a></h3>

 <p>Originally bhyve supported only localtime for RTC. Support for UTC time was introduced in
 <a href="http://svnweb.freebsd.org/changeset/base/284894">r284894</a> for <i>10-STABLE</i> and
@@ -409,7 +417,7 @@ you'll need to explicitly specify 'localtime' in this case:</p>
 &lt;/domain&gt;
 </pre>

-<h3><a name="e1000">e1000 NIC</a></h3>
+<h3><a id="e1000">e1000 NIC</a></h3>

 <p>As of <a href="https://svnweb.freebsd.org/changeset/base/302504">r302504</a> bhyve
 supports Intel e1000 network adapter emulation. It's supported in libvirt
--- a/docs/drvesx.html.in
+++ b/docs/drvesx.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>VMware ESX hypervisor driver</h1>
@@ -11,7 +11,7 @@
        connect to a VMware vCenter 2.5/4.x/5.x (VPX).
    </p>

-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
@@ -20,7 +20,7 @@
      </li>
    </ul>

-    <h2><a name="prereq">Deployment pre-requisites</a></h2>
+    <h2><a id="prereq">Deployment pre-requisites</a></h2>
    <p>
        None. Any out-of-the-box installation of VPX/ESX(i)/GSX should work. No
        preparations are required on the server side, no libvirtd must be
@@ -34,7 +34,7 @@
        VMware vSphere API</a>.
    </p>

-    <h2><a name="uri">Connections to the VMware ESX driver</a></h2>
+    <h2><a id="uri">Connections to the VMware ESX driver</a></h2>
    <p>
        Some example remote connection URIs for the driver are:
    </p>
@@ -54,7 +54,7 @@ esx://example-esx.com/?no_verify=1     (ESX over HTTPS, but doesn't verify the s
    </p>


-    <h3><a name="uriformat">URI Format</a></h3>
+    <h3><a id="uriformat">URI Format</a></h3>
    <p>
        URIs have this general form (<code>[...]</code> marks an optional part).
    </p>
@@ -93,7 +93,7 @@ vpx://example-vcenter.com/folder1/dc1/folder2/example-esx.com
 </pre>


-    <h4><a name="extraparams">Extra parameters</a></h4>
+    <h4><a id="extraparams">Extra parameters</a></h4>
    <p>
        Extra parameters can be added to a URI as part of the query string
        (the part following <code>?</code>). A single parameter is formed by a
@@ -188,7 +188,7 @@ vpx://example-vcenter.com/folder1/dc1/folder2/example-esx.com
    </table>


-    <h3><a name="auth">Authentication</a></h3>
+    <h3><a id="auth">Authentication</a></h3>
    <p>
        In order to perform any useful operation the driver needs to log into
        the ESX server. Therefore, only <code>virConnectOpenAuth</code> can be
@@ -208,7 +208,7 @@ vpx://example-vcenter.com/folder1/dc1/folder2/example-esx.com
    </p>


-    <h3><a name="certificates">Certificates for HTTPS</a></h3>
+    <h3><a id="certificates">Certificates for HTTPS</a></h3>
    <p>
        By default the ESX driver uses HTTPS to communicate with an ESX server.
        Proper HTTPS communication requires correctly configured SSL
@@ -244,7 +244,7 @@ error: internal error curl_easy_perform() returned an error: Peer certificate ca
    </ul>


-    <h3><a name="connproblems">Connection problems</a></h3>
+    <h3><a id="connproblems">Connection problems</a></h3>
    <p>
        There are also other causes for connection problems than the
        <a href="#certificates">HTTPS certificate</a> related ones.
@@ -303,7 +303,7 @@ error: invalid argument in libvirt was built without the 'esx' driver
    </ul>


-    <h2><a name="questions">Questions blocking tasks</a></h2>
+    <h2><a id="questions">Questions blocking tasks</a></h2>
    <p>
        Some methods of the VI API start tasks, for example
        <code>PowerOnVM_Task()</code>. Such tasks may be blocked by questions
@@ -322,12 +322,12 @@ error: invalid argument in libvirt was built without the 'esx' driver
    </p>


-    <h2><a name="xmlspecial">Specialties in the domain XML config</a></h2>
+    <h2><a id="xmlspecial">Specialties in the domain XML config</a></h2>
    <p>
        There are several specialties in the domain XML config for ESX domains.
    </p>

-    <h3><a name="restrictions">Restrictions</a></h3>
+    <h3><a id="restrictions">Restrictions</a></h3>
    <p>
        There are some restrictions for some values of the domain XML config.
        The driver will complain if this restrictions are violated.
@@ -347,7 +347,7 @@ error: invalid argument in libvirt was built without the 'esx' driver
    </ul>


-    <h3><a name="datastore">Datastore references</a></h3>
+    <h3><a id="datastore">Datastore references</a></h3>
    <p>
        Storage is managed in datastores. VMware uses a special path format to
        reference files in a datastore. Basically, the datastore name is put
@@ -366,7 +366,7 @@ error: invalid argument in libvirt was built without the 'esx' driver
    </p>


-    <h3><a name="macaddresses">MAC addresses</a></h3>
+    <h3><a id="macaddresses">MAC addresses</a></h3>
    <p>
        VMware has registered two MAC address prefixes for domains:
        <code>00:0c:29</code> and <code>00:50:56</code>. These prefixes are
@@ -427,7 +427,7 @@ ethernet0.checkMACAddress = "false"
 </pre>


-    <h3><a name="hardware">Available hardware</a></h3>
+    <h3><a id="hardware">Available hardware</a></h3>
    <p>
        VMware ESX supports different models of SCSI controllers and network
        cards.
@@ -523,14 +523,14 @@ ethernet0.checkMACAddress = "false"
 </pre>


-    <h2><a name="importexport">Import and export of domain XML configs</a></h2>
+    <h2><a id="importexport">Import and export of domain XML configs</a></h2>
    <p>
        The ESX driver currently supports a native config format known as
        <code>vmware-vmx</code> to handle VMware VMX configs.
    </p>


-    <h3><a name="xmlimport">Converting from VMware VMX config to domain XML config</a></h3>
+    <h3><a id="xmlimport">Converting from VMware VMX config to domain XML config</a></h3>
    <p>
        The <code>virsh domxml-from-native</code> provides a way to convert an
        existing VMware VMX config into a domain XML config that can then be
@@ -621,7 +621,7 @@ Enter root password for example.com:
 </pre>


-    <h3><a name="xmlexport">Converting from domain XML config to VMware VMX config</a></h3>
+    <h3><a id="xmlexport">Converting from domain XML config to VMware VMX config</a></h3>
    <p>
      The <code>virsh domxml-to-native</code> provides a way to convert a
      domain XML config into a VMware VMX config.
@@ -675,7 +675,7 @@ ethernet0.address = "00:50:56:25:48:C7"
 </pre>


-    <h2><a name="xmlconfig">Example domain XML configs</a></h2>
+    <h2><a id="xmlconfig">Example domain XML configs</a></h2>

    <h3>Fedora11 on x86_64</h3>
 <pre>
@@ -704,7 +704,7 @@ ethernet0.address = "00:50:56:25:48:C7"
 </pre>


-    <h2><a name="migration">Migration</a></h2>
+    <h2><a id="migration">Migration</a></h2>
    <p>
        A migration cannot be initiated on an ESX server directly, a VMware
        vCenter is necessary for this. The <code>vcenter</code> query
@@ -749,7 +749,7 @@ Enter administrator password for example-vcenter.com:
 </pre>


-    <h2><a name="scheduler">Scheduler configuration</a></h2>
+    <h2><a id="scheduler">Scheduler configuration</a></h2>
    <p>
        The driver exposes the ESX CPU scheduler. The parameters listed below
        are available to control the scheduler.
@@ -780,7 +780,7 @@ Enter administrator password for example-vcenter.com:
    </dl>


-    <h2><a name="tools">VMware tools</a></h2>
+    <h2><a id="tools">VMware tools</a></h2>
    <p>
        Some actions require installed VMware tools. If the VMware tools are
        not installed in the guest and one of the actions below is to be
@@ -796,7 +796,7 @@ Enter administrator password for example-vcenter.com:
    </ul>


-    <h2><a name="links">Links</a></h2>
+    <h2><a id="links">Links</a></h2>
    <ul>
        <li>
            <a href="http://www.vmware.com/support/developer/vc-sdk/">
--- a/docs/drvhyperv.html.in
+++ b/docs/drvhyperv.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Microsoft Hyper-V hypervisor driver</h1>
@@ -9,7 +9,7 @@
    </p>


-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>
    <ul>
      <li>
        The <a href="http://www.microsoft.com/hyper-v-server/">Microsoft Hyper-V</a>
@@ -18,7 +18,7 @@
    </ul>


-    <h2><a name="uri">Connections to the Microsoft Hyper-V driver</a></h2>
+    <h2><a id="uri">Connections to the Microsoft Hyper-V driver</a></h2>
    <p>
        Some example remote connection URIs for the driver are:
    </p>
@@ -36,7 +36,7 @@ hyperv://example-hyperv.com/?transport=http  (over HTTP)
    </p>


-    <h3><a name="uriformat">URI Format</a></h3>
+    <h3><a id="uriformat">URI Format</a></h3>
    <p>
        URIs have this general form (<code>[...]</code> marks an optional part).
    </p>
@@ -49,7 +49,7 @@ hyperv://[username@]hostname[:port]/[?extraparameters]
    </p>


-    <h4><a name="extraparams">Extra parameters</a></h4>
+    <h4><a id="extraparams">Extra parameters</a></h4>
    <p>
        Extra parameters can be added to a URI as part of the query string
        (the part following <code>?</code>). A single parameter is formed by a
@@ -83,7 +83,7 @@ hyperv://[username@]hostname[:port]/[?extraparameters]
    </table>


-    <h3><a name="auth">Authentication</a></h3>
+    <h3><a id="auth">Authentication</a></h3>
    <p>
        In order to perform any useful operation the driver needs to log into
        the Hyper-V server. Therefore, only <code>virConnectOpenAuth</code> can
--- a/docs/drvlxc.html.in
+++ b/docs/drvlxc.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>LXC container driver</h1>
@@ -18,7 +18,7 @@ particular sVirt for mandatory access control, auditing of operations,
 integration with control groups and many other features.
 </p>

-<h2><a name="cgroups">Control groups Requirements</a></h2>
+<h2><a id="cgroups">Control groups Requirements</a></h2>

 <p>
 In order to control the resource usage of processes inside containers, the
@@ -32,7 +32,7 @@ init service will be required. For further information, consult the general
 libvirt <a href="cgroups.html">cgroups documentation</a>.
 </p>

-<h2><a name="namespaces">Namespace requirements</a></h2>
+<h2><a id="namespaces">Namespace requirements</a></h2>

 <p>
 In order to separate processes inside a container from those in the
@@ -47,9 +47,9 @@ configured UID/GID mapping is a pre-requisite to making containers
 secure, in the absence of sVirt confinement.</strong>
 </p>

-<h2><a name="init">Default container setup</a></h2>
+<h2><a id="init">Default container setup</a></h2>

-<h3><a name="cliargs">Command line arguments</a></h3>
+<h3><a id="cliargs">Command line arguments</a></h3>

 <p>
 When the container "init" process is started, it will typically
@@ -70,7 +70,7 @@ would use the following XML
 &lt;/os&gt;
 </pre>

-<h3><a name="envvars">Environment variables</a></h3>
+<h3><a id="envvars">Environment variables</a></h3>

 <p>
 When the container "init" process is started, it will be given several useful
@@ -108,7 +108,7 @@ Use of this is discouraged, in favour of passing arguments directly to the
 container init process via the <code>initarg</code> config element.</dd>
 </dl>

-<h3><a name="fsmounts">Filesystem mounts</a></h3>
+<h3><a id="fsmounts">Filesystem mounts</a></h3>

 <p>
 In the absence of any explicit configuration, the container will
@@ -131,7 +131,7 @@ only expose the sub-tree associated with the container</li>
 </ul>


-<h3><a name="devnodes">Device nodes</a></h3>
+<h3><a id="devnodes">Device nodes</a></h3>

 <p>
 The container init process will be started with <code>CAP_MKNOD</code>
@@ -178,7 +178,7 @@ Further block or character devices will be made available to containers
 depending on their configuration.
 </p>

-<h2><a name="security">Security considerations</a></h2>
+<h2><a id="security">Security considerations</a></h2>

 <p>
 The libvirt LXC driver is fairly flexible in how it can be configured,
@@ -190,7 +190,7 @@ isolation between a container and the host must ensure that they are
 writing a suitable configuration.
 </p>

-<h3><a name="securenetworking">Network isolation</a></h3>
+<h3><a id="securenetworking">Network isolation</a></h3>

 <p>
 If the guest configuration does not list any network interfaces,
@@ -205,7 +205,7 @@ namespace is not wanted, then applications should set the
 <code>&lt;features&gt;....&lt;/features&gt;</code> element.
 </p>

-<h3><a name="securefs">Filesystem isolation</a></h3>
+<h3><a id="securefs">Filesystem isolation</a></h3>

 <p>
 If the guest configuration does not list any filesystems, then
@@ -250,7 +250,7 @@ a bind mount to hide them. This is particularly important for the
 </p>


-<h3><a name="secureusers">User and group isolation</a></h3>
+<h3><a id="secureusers">User and group isolation</a></h3>

 <p>
 If the guest configuration does not list any ID mapping, then the
@@ -281,7 +281,7 @@ causes libvirt to activate the user namespace feature.
 </p>


-<h2><a name="activation">Systemd Socket Activation Integration</a></h2>
+<h2><a id="activation">Systemd Socket Activation Integration</a></h2>

 <p>
 The libvirt LXC driver provides the ability to pass across pre-opened file
@@ -477,7 +477,7 @@ configured to block read/write/mknod from all devices except those
 that a container is authorized to use.
 </p>

-<h2><a name="exconfig">Example configurations</a></h2>
+<h2><a id="exconfig">Example configurations</a></h2>

 <h3>Example config version 1</h3>
 <p></p>
@@ -542,7 +542,7 @@ debootstrap, whatever) under /opt/vm-1-root:
 &lt;/domain&gt;
 </pre>

-<h2><a name="capabilities">Altering the available capabilities</a></h2>
+<h2><a id="capabilities">Altering the available capabilities</a></h2>

 <p>
 By default the libvirt LXC driver drops some capabilities among which CAP_MKNOD.
@@ -590,7 +590,7 @@ Note that allowing capabilities that are normally dropped by default can serious
 affect the security of the container and the host.
 </p>

-<h2><a name="share">Inherit namespaces</a></h2>
+<h2><a id="share">Inherit namespaces</a></h2>

 <p>
 Libvirt allows you to inherit the namespace from container/process just like lxc tools
@@ -615,7 +615,7 @@ ignored.
 The use of namespace passthrough requires libvirt >= 1.2.19
 </p>

-<h2><a name="usage">Container usage / management</a></h2>
+<h2><a id="usage">Container usage / management</a></h2>

 <p>
 As with any libvirt virtualization driver, LXC containers can be
@@ -629,7 +629,7 @@ and LXC. For further details about usage of virsh consult its
 manual page.
 </p>

-<h3><a name="usageSave">Defining (saving) container configuration</a></h3>
+<h3><a id="usageSave">Defining (saving) container configuration</a></h3>

 <p>
 The <code>virsh define</code> command takes an XML configuration
@@ -640,7 +640,7 @@ document and loads it into libvirt, saving the configuration on disk
 # virsh -c lxc:/// define myguest.xml
 </pre>

-<h3><a name="usageView">Viewing container configuration</a></h3>
+<h3><a id="usageView">Viewing container configuration</a></h3>

 <p>
 The <code>virsh dumpxml</code> command can be used to view the
@@ -655,7 +655,7 @@ using the <code>--inactive</code> flag
 # virsh -c lxc:/// dumpxml myguest
 </pre>

-<h3><a name="usageStart">Starting containers</a></h3>
+<h3><a id="usageStart">Starting containers</a></h3>

 <p>
 The <code>virsh start</code> command can be used to start a
@@ -677,7 +677,7 @@ by libvirt, using the <code>virsh create</code> command.
 </pre>


-<h3><a name="usageStop">Stopping containers</a></h3>
+<h3><a id="usageStop">Stopping containers</a></h3>

 <p>
 The <code>virsh shutdown</code> command can be used
@@ -702,7 +702,7 @@ request, it can be forcibly stopped using the <code>virsh destroy</code>
 </pre>


-<h3><a name="usageReboot">Rebooting a container</a></h3>
+<h3><a id="usageReboot">Rebooting a container</a></h3>

 <p>
 The <code>virsh reboot</code> command can be used
@@ -717,7 +717,7 @@ to PID 1 inside the container.
 # virsh -c lxc:/// reboot myguest
 </pre>

-<h3><a name="usageDelete">Undefining (deleting) a container configuration</a></h3>
+<h3><a id="usageDelete">Undefining (deleting) a container configuration</a></h3>

 <p>
 The <code>virsh undefine</code> command can be used to delete the
@@ -729,7 +729,7 @@ running, this will turn it into a "transient" guest.
 # virsh -c lxc:/// undefine myguest
 </pre>

-<h3><a name="usageConnect">Connecting to a container console</a></h3>
+<h3><a id="usageConnect">Connecting to a container console</a></h3>

 <p>
 The <code>virsh console</code> command can be used to connect
@@ -752,7 +752,7 @@ as 'console0', 'console1', 'console2', etc.
 # virsh -c lxc:/// console myguest --devname console1
 </pre>

-<h3><a name="usageEnter">Running commands in a container</a></h3>
+<h3><a id="usageEnter">Running commands in a container</a></h3>

 <p>
 The <code>virsh lxc-enter-namespace</code> command can be used
@@ -764,7 +764,7 @@ and then execute an arbitrary command.
 # virsh -c lxc:/// lxc-enter-namespace myguest -- /bin/ls -al /dev
 </pre>

-<h3><a name="usageTop">Monitoring container utilization</a></h3>
+<h3><a id="usageTop">Monitoring container utilization</a></h3>

 <p>
 The <code>virt-top</code> command can be used to monitor the
@@ -776,7 +776,7 @@ host
 # virt-top -c lxc:///
 </pre>

-<h3><a name="usageConvert">Converting LXC container configuration</a></h3>
+<h3><a id="usageConvert">Converting LXC container configuration</a></h3>

 <p>
 The <code>virsh domxml-from-native</code> command can be used to convert
--- a/docs/drvnodedev.html.in
+++ b/docs/drvnodedev.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Host device management</h1>
@@ -98,7 +98,7 @@

    <ul id="toc"/>

-    <h2><a name="PCI">PCI host devices</a></h2>
+    <h2><a id="PCI">PCI host devices</a></h2>
    <dl>
      <dt><code>capability</code></dt>
      <dd>
@@ -139,7 +139,7 @@
      element will be included for each capability the device supports.
    </p>

-    <h3><a name="SRIOVCap">SR-IOV capability</a></h3>
+    <h3><a id="SRIOVCap">SR-IOV capability</a></h3>
    <p>
      Single root input/output virtualization (SR-IOV) allows sharing of the
      PCIe resources by multiple virtual environments. That is achieved by
@@ -186,7 +186,7 @@
 ...
 &lt;device&gt;</pre>

-    <h3><a name="MDEVCap">MDEV capability</a></h3>
+    <h3><a id="MDEVCap">MDEV capability</a></h3>
    <p>
      A PCI device capable of creating mediated devices will include a nested
      capability <code>mdev_types</code> which enumerates all supported mdev
@@ -252,7 +252,7 @@
  &lt;/capability&gt;
 &lt;/device&gt;</pre>

-    <h2><a name="MDEV">Mediated devices (MDEVs)</a></h2>
+    <h2><a id="MDEV">Mediated devices (MDEVs)</a></h2>
    <p>
      Mediated devices (<span class="since">Since 3.2.0</span>) are software
      devices defining resource allocation on the backing physical device which
--- a/docs/drvopenvz.html.in
+++ b/docs/drvopenvz.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>OpenVZ container driver</h1>
@@ -15,7 +15,7 @@
    undue trouble.
    </p>

-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
@@ -24,7 +24,7 @@
      </li>
    </ul>

-    <h2><a name="connections">Connections to OpenVZ driver</a></h2>
+    <h2><a id="connections">Connections to OpenVZ driver</a></h2>

    <p>
    The libvirt OpenVZ driver is a single-instance privileged driver,
@@ -40,7 +40,7 @@ openvz+tcp://example.com/system      (remote access, SASl/Kerberos)
 openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
 </pre>

-    <h2><a name="notes">Notes on bridged networking</a></h2>
+    <h2><a id="notes">Notes on bridged networking</a></h2>

    <p>
    Bridged networking enables a guest domain (ie container) to have its
@@ -49,7 +49,7 @@ openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
    the host OS.
    </p>

-    <h3><a name="host">Host network devices</a></h3>
+    <h3><a id="host">Host network devices</a></h3>

    <p>
    One or more of the physical devices must be attached to a bridge. The
@@ -60,7 +60,7 @@ openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
    physical device "eth0", or a bonding device "bond0".
    </p>

-    <h3><a name="tools">OpenVZ tools configuration</a></h3>
+    <h3><a id="tools">OpenVZ tools configuration</a></h3>

    <p>
    OpenVZ releases later than 3.0.23 ship with a standard network device
@@ -85,7 +85,7 @@ EXTERNAL_SCRIPT="/usr/sbin/vznetaddbr"
    </p>


-    <h2><a name="example">Example guest domain XML configuration</a></h2>
+    <h2><a id="example">Example guest domain XML configuration</a></h2>

    <p>
    The current libvirt OpenVZ driver has a restriction that the
--- a/docs/drvphyp.html.in
+++ b/docs/drvphyp.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>IBM PowerVM hypervisor driver (phyp)</h1>
@@ -10,7 +10,7 @@
    </p>


-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>
    <ul>
      <li>
        The <a href="http://www-03.ibm.com/systems/power/software/virtualization/index.html">IBM
@@ -19,7 +19,7 @@
    </ul>


-    <h2><a name="uri">Connections to the PowerVM driver</a></h2>
+    <h2><a id="uri">Connections to the PowerVM driver</a></h2>
    <p>
        Some example remote connection URIs for the driver are:
    </p>
@@ -38,7 +38,7 @@ phyp://user@ivm/system (IVM connection)
    </p>


-    <h3><a name="uriformat">URI Format</a></h3>
+    <h3><a id="uriformat">URI Format</a></h3>
    <p>
        URIs have this general form (<code>[...]</code> marks an
        optional part, <code>{...|...}</code> marks a mandatory choice).
--- a/docs/drvqemu.html.in
+++ b/docs/drvqemu.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>KVM/QEMU hypervisor driver</h1>
@@ -11,7 +11,7 @@
      version 0.12.0 or later.
    </p>

-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
@@ -23,7 +23,7 @@
      </li>
    </ul>

-    <h2><a name="prereq">Deployment pre-requisites</a></h2>
+    <h2><a id="prereq">Deployment pre-requisites</a></h2>

    <ul>
      <li>
@@ -43,7 +43,7 @@
      </li>
    </ul>

-    <h2><a name="uris">Connections to QEMU driver</a></h2>
+    <h2><a id="uris">Connections to QEMU driver</a></h2>

    <p>
    The libvirt QEMU driver is a multi-instance driver, providing a single
@@ -63,14 +63,14 @@ qemu+tcp://example.com/system        (remote access, SASl/Kerberos)
 qemu+ssh://root@example.com/system   (remote access, SSH tunnelled)
 </pre>

-    <h2><a name="security">Driver security architecture</a></h2>
+    <h2><a id="security">Driver security architecture</a></h2>

    <p>
      There are multiple layers to security in the QEMU driver, allowing for
      flexibility in the use of QEMU based virtual machines.
    </p>

-    <h3><a name="securitydriver">Driver instances</a></h3>
+    <h3><a id="securitydriver">Driver instances</a></h3>

    <p>
      As explained above there are two ways to access the QEMU driver
@@ -94,7 +94,7 @@ qemu+ssh://root@example.com/system   (remote access, SSH tunnelled)
      elevated privileges.
    </p>

-    <h3><a name="securitydac">POSIX users/groups</a></h3>
+    <h3><a id="securitydac">POSIX users/groups</a></h3>

    <p>
      In the "session" instance, the POSIX users/groups model restricts QEMU
@@ -187,7 +187,7 @@ chmod o+x /path/to/directory
      </li>
    </ul>

-    <h3><a name="securitycap">Linux process capabilities</a></h3>
+    <h3><a id="securitycap">Linux process capabilities</a></h3>

    <p>
      The libvirt QEMU driver has a build time option allowing it to use
@@ -224,7 +224,7 @@ chmod o+x /path/to/directory
      to changing the <code>/etc/libvirt/qemu.conf</code> settings.
    </p>

-    <h3><a name="securityselinux">SELinux basic confinement</a></h3>
+    <h3><a id="securityselinux">SELinux basic confinement</a></h3>

    <p>
      The basic SELinux protection for QEMU virtual machines is intended to
@@ -255,7 +255,7 @@ chmod o+x /path/to/directory
      SELinux boolean.
    </p>

-    <h3><a name="securitysvirt">SELinux sVirt confinement</a></h3>
+    <h3><a id="securitysvirt">SELinux sVirt confinement</a></h3>

    <p>
      The SELinux sVirt protection for QEMU virtual machines builds to the
@@ -305,7 +305,7 @@ chmod o+x /path/to/directory
      file can be used to change the setting to <code>security_driver="none"</code>
    </p>

-    <h3><a name="securitysvirtaa">AppArmor sVirt confinement</a></h3>
+    <h3><a id="securitysvirtaa">AppArmor sVirt confinement</a></h3>

    <p>
      When using basic AppArmor protection for the libvirtd daemon and
@@ -373,7 +373,7 @@ chmod o+x /path/to/directory
    </p>


-    <h3><a name="securityacl">Cgroups device ACLs</a></h3>
+    <h3><a id="securityacl">Cgroups device ACLs</a></h3>

    <p>
      Recent Linux kernels have a capability known as "cgroups" which is used
@@ -416,7 +416,7 @@ mount -t cgroup none /dev/cgroup -o devices
      <code>/dev/cgroup/libvirt/qemu/$VMNAME/</code>
    </p>

-    <h2><a name="imex">Import and export of libvirt domain XML configs</a></h2>
+    <h2><a id="imex">Import and export of libvirt domain XML configs</a></h2>

    <p>The QEMU driver currently supports a single native
      config format known as <code>qemu-argv</code>. The data for this format
@@ -424,7 +424,7 @@ mount -t cgroup none /dev/cgroup -o devices
      then the QEMu binary name, finally followed by the QEMU command line
      arguments</p>

-    <h3><a name="xmlimport">Converting from QEMU args to domain XML</a></h3>
+    <h3><a id="xmlimport">Converting from QEMU args to domain XML</a></h3>

    <p>
      The <code>virsh domxml-from-native</code> provides a way to
@@ -473,7 +473,7 @@ $ virsh domxml-from-native qemu-argv demo.args

    <p>NB, don't include the literal \ in the args, put everything on one line</p>

-    <h3><a name="xmlexport">Converting from domain XML to QEMU args</a></h3>
+    <h3><a id="xmlexport">Converting from domain XML to QEMU args</a></h3>

    <p>
      The <code>virsh domxml-to-native</code> provides a way to convert a
@@ -515,7 +515,7 @@ $ virsh domxml-to-native qemu-argv demo.xml
  -serial none -parallel none -usb
 </pre>

-    <h2><a name="qemucommand">Pass-through of arbitrary qemu
+    <h2><a id="qemucommand">Pass-through of arbitrary qemu
    commands</a></h2>

    <p>Libvirt provides an XML namespace and an optional
@@ -582,7 +582,7 @@ $ virsh domxml-to-native qemu-argv demo.xml
 &lt;/domain&gt;
 </pre>

-    <h2><a name="xmlconfig">Example domain XML config</a></h2>
+    <h2><a id="xmlconfig">Example domain XML config</a></h2>

    <h3>QEMU emulated guest on x86_64</h3>

--- a/docs/drvremote.html.in
+++ b/docs/drvremote.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Remote management driver</h1>
--- a/docs/drvtest.html.in
+++ b/docs/drvtest.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Test "mock" driver</h1>
--- a/docs/drvuml.html.in
+++ b/docs/drvuml.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>User Mode Linux driver</h1>
@@ -13,7 +13,7 @@
    has pre-created TAP devices.
    </p>

-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
--- a/docs/drvvbox.html.in
+++ b/docs/drvvbox.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
    <body>
        <h1>VirtualBox hypervisor driver</h1>
@@ -8,7 +8,7 @@
        from version 2.2 onwards.
    </p>

-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
@@ -43,7 +43,7 @@ vbox+ssh://user@example.com/session  (remote access, SSH tunnelled)
        work is completed to get the libvirtd daemon working there.</strong>
    </p>

-    <h2><a name="xmlconfig">Example domain XML config</a></h2>
+    <h2><a id="xmlconfig">Example domain XML config</a></h2>

 <pre>
 &lt;domain type='vbox'&gt;
--- a/docs/drvvirtuozzo.html.in
+++ b/docs/drvvirtuozzo.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Virtuozzo driver</h1>
@@ -9,7 +9,7 @@
    </p>


-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>
    <ul>
      <li>
        The <a href="http://www.odin.com/products/virtuozzo/">Virtuozzo</a> Solution.
@@ -17,7 +17,7 @@
    </ul>


-    <h2><a name="uri">Connections to the Virtuozzo driver</a></h2>
+    <h2><a id="uri">Connections to the Virtuozzo driver</a></h2>
    <p>
        The libvirt Virtuozzo driver is a single-instance privileged driver, with a driver name of 'virtuozzo'. Some example connection URIs for the libvirt driver are:
    </p>
@@ -29,7 +29,7 @@ vz+tcp://example.com/system      (remote access, SASl/Kerberos)
 vz+ssh://root@example.com/system (remote access, SSH tunnelled)
 </pre>

-    <h2><a name="example">Example guest domain XML configuration</a></h2>
+    <h2><a id="example">Example guest domain XML configuration</a></h2>

    <p>
    Virtuozzo driver require at least one hard disk for new domains
--- a/docs/drvvmware.html.in
+++ b/docs/drvvmware.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
    <body>
        <h1>VMware Workstation / Player / Fusion hypervisors driver</h1>
@@ -15,7 +15,7 @@
    from <a href="http://www.vmware.com/support/developer/vix-api/">here</a>.
    </p>

-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
@@ -51,7 +51,7 @@ vmwarews+tcp://user@example.com/session  (remote access to VMware Workstation, S
 vmwarews+ssh://user@example.com/session  (remote access to VMware Workstation, SSH tunnelled)
 </pre>

-    <h2><a name="xmlconfig">Example domain XML config</a></h2>
+    <h2><a id="xmlconfig">Example domain XML config</a></h2>

 <pre>
 &lt;domain type='vmware'&gt;
--- a/docs/drvxen.html.in
+++ b/docs/drvxen.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Xen hypervisor driver</h1>
@@ -11,7 +11,7 @@
      on any Xen release from 3.0.1 onwards.
    </p>

-    <h2><a name="project">Project Links</a></h2>
+    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
@@ -20,7 +20,7 @@
      </li>
    </ul>

-    <h2><a name="prereq">Deployment pre-requisites</a></h2>
+    <h2><a id="prereq">Deployment pre-requisites</a></h2>

    <p>
      The libvirt Xen driver uses a combination of channels to manage Xen
@@ -65,7 +65,7 @@
      </li>
    </ul>

-    <h2><a name="uri">Connections to Xen driver</a></h2>
+    <h2><a id="uri">Connections to Xen driver</a></h2>

    <p>
    The libvirt Xen driver is a single-instance privileged driver,
@@ -81,7 +81,7 @@ xen+tcp://example.com/         (remote access, SASl/Kerberos)
 xen+ssh://root@example.com/    (remote access, SSH tunnelled)
 </pre>

-    <h2><a name="imex">Import and export of libvirt domain XML configs</a></h2>
+    <h2><a id="imex">Import and export of libvirt domain XML configs</a></h2>

    <p>The Xen driver currently supports two native
      config formats. The first known as <code>xen-xm</code> is the format
@@ -89,7 +89,7 @@ xen+ssh://root@example.com/    (remote access, SSH tunnelled)
      known as <code>xen-sxpr</code>, is the format used for interacting
      with the XenD's legacy HTTP RPC service.</p>

-    <h3><a name="xmlimport">Converting from XM config files to domain XML</a></h3>
+    <h3><a id="xmlimport">Converting from XM config files to domain XML</a></h3>

    <p>
      The <code>virsh domxml-from-native</code> provides a way to convert an
@@ -135,7 +135,7 @@ xen+ssh://root@example.com/    (remote access, SSH tunnelled)
  &lt;/devices&gt;
 &lt;/domain&gt;</pre>

-    <h3><a name="xmlexport">Converting from domain XML to XM config files</a></h3>
+    <h3><a id="xmlexport">Converting from domain XML to XM config files</a></h3>

    <p>
      The <code>virsh domxml-to-native</code> provides a way to convert a
@@ -163,7 +163,7 @@ vnclisten = "0.0.0.0"
 disk = [ "tap:aio:/var/lib/xen/images/rhel5pv.img,xvda,w", "tap:qcow:/root/qcow1-xen.img,xvdd,w" ]
 vif = [ "mac=00:16:3e:60:36:ba,bridge=virbr0,script=vif-bridge,vifname=vif5.0" ]</pre>

-    <h2><a name="xmlconfig">Example domain XML config</a></h2>
+    <h2><a id="xmlconfig">Example domain XML config</a></h2>

    <p>
      Below are some example XML configurations for Xen guest domains.
--- a/docs/errors.html.in
+++ b/docs/errors.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1 >Handling of errors</h1>
--- a/docs/favicon-16x16.png
+++ b/docs/favicon-16x16.png
--- a/docs/favicon-32x32.png
+++ b/docs/favicon-32x32.png
--- a/docs/favicon.ico
+++ b/docs/favicon.ico
--- a/docs/firewall.html.in
+++ b/docs/firewall.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1 >Firewall and network filtering in libvirt</h1>
@@ -35,8 +35,7 @@
      </li>
    </ul>

-    <h3><a name="name-fw-virtual-network-driver"
-           id="id-fw-virtual-network-driver">The virtual network driver</a>
+    <h3><a id="fw-virtual-network-driver">The virtual network driver</a>
    </h3>
    <p>The typical configuration for guests is to use bridging of the
       physical NIC on the host to connect the guest directly to the LAN.
@@ -130,8 +129,7 @@ MASQUERADE all  --  *      *       192.168.122.0/24    !192.168.122.0/24</pre>
      </li>
    </ul>

-    <h3><a name="name-fw-network-filter-driver"
-           id="id-fw-network-filter-driver">The network filter driver</a>
+    <h3><a id="fw-network-filter-driver">The network filter driver</a>
    </h3>
    <p>This driver provides a fully configurable network filtering capability
       that leverages ebtables, iptables and ip6tables. This was written by
--- a/docs/format.html.in
+++ b/docs/format.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>XML Format</h1>
@@ -14,16 +14,16 @@


    <ul>
-      <li><a href="formatdomain.html" shape="rect">Domains</a></li>
-      <li><a href="formatnetwork.html" shape="rect">Networks</a></li>
-      <li><a href="formatnwfilter.html" shape="rect">Network filtering</a></li>
-      <li><a href="formatstorage.html" shape="rect">Storage</a></li>
-      <li><a href="formatstorageencryption.html" shape="rect">Storage encryption</a></li>
-      <li><a href="formatcaps.html" shape="rect">Capabilities</a></li>
-      <li><a href="formatdomaincaps.html" shape="rect">Domain capabilities</a></li>
-      <li><a href="formatnode.html" shape="rect">Node devices</a></li>
-      <li><a href="formatsecret.html" shape="rect">Secrets</a></li>
-      <li><a href="formatsnapshot.html" shape="rect">Snapshots</a></li>
+      <li><a href="formatdomain.html">Domains</a></li>
+      <li><a href="formatnetwork.html">Networks</a></li>
+      <li><a href="formatnwfilter.html">Network filtering</a></li>
+      <li><a href="formatstorage.html">Storage</a></li>
+      <li><a href="formatstorageencryption.html">Storage encryption</a></li>
+      <li><a href="formatcaps.html">Capabilities</a></li>
+      <li><a href="formatdomaincaps.html">Domain capabilities</a></li>
+      <li><a href="formatnode.html">Node devices</a></li>
+      <li><a href="formatsecret.html">Secrets</a></li>
+      <li><a href="formatsnapshot.html">Snapshots</a></li>
    </ul>

    <h2>Command line validation</h2>
--- a/docs/formatcaps.html.in
+++ b/docs/formatcaps.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Driver capabilities XML format</h1>

    <ul id="toc"></ul>

-    <h2><a name="elements">Element and attribute overview</a></h2>
+    <h2><a id="elements">Element and attribute overview</a></h2>

    <p>As new virtualization engine support gets added to libvirt, and to
    handle cases like QEMU supporting a variety of emulations, a query
@@ -28,7 +28,7 @@
    the set of architectures the host can run at the moment.</p>


-    <h3><a name="elementHost">Host capabilities</a></h3>
+    <h3><a id="elementHost">Host capabilities</a></h3>

    <p>The <code>&lt;host/&gt;</code> element consists of the following child
    elements:</p>
@@ -61,7 +61,7 @@
    </dl>


-    <h3><a name="elementGuest">Guest capabilities</a></h3>
+    <h3><a id="elementGuest">Guest capabilities</a></h3>

    <p>While the <a href="#elementHost">previous section</a> aims at host
    capabilities, this one focuses on capabilities available to a guest
@@ -138,7 +138,7 @@
        </dd>
    </dl>

-    <h3><a name="elementExamples">Examples</a></h3>
+    <h3><a id="elementExamples">Examples</a></h3>

    <p>For example, in the case of a 64-bit machine with hardware
    virtualization capabilities enabled in the chip and
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Domain XML format</h1>
@@ -14,7 +14,7 @@
    </p>


-    <h2><a name="elements">Element and attribute overview</a></h2>
+    <h2><a id="elements">Element and attribute overview</a></h2>

    <p>
      The root element required for all virtual machines is
@@ -28,7 +28,7 @@
    </p>


-    <h3><a name="elementsMetadata">General metadata</a></h3>
+    <h3><a id="elementsMetadata">General metadata</a></h3>

 <pre>
 &lt;domain type='xen' id='3'&gt;
@@ -82,14 +82,14 @@
        element). <span class="since">Since 0.9.10</span></dd>
   </dl>

-    <h3><a name="elementsOS">Operating system booting</a></h3>
+    <h3><a id="elementsOS">Operating system booting</a></h3>

    <p>
      There are a number of different ways to boot virtual machines
      each with their own pros and cons.
    </p>

-    <h4><a name="elementsOSBIOS">BIOS bootloader</a></h4>
+    <h4><a id="elementsOSBIOS">BIOS bootloader</a></h4>

    <p>
      Booting via the BIOS is available for hypervisors supporting
@@ -229,7 +229,7 @@
      </dd>
    </dl>

-    <h4><a name="elementsOSBootloader">Host bootloader</a></h4>
+    <h4><a id="elementsOSBootloader">Host bootloader</a></h4>

    <p>
      Hypervisors employing paravirtualization do not usually emulate
@@ -262,7 +262,7 @@

    </dl>

-    <h4><a name="elementsOSKernel">Direct kernel boot</a></h4>
+    <h4><a id="elementsOSKernel">Direct kernel boot</a></h4>

    <p>
      When installing a new guest OS it is often useful to boot directly
@@ -315,7 +315,7 @@
        <span class="since">Since 1.3.5 (QEMU only)</span></dd>
    </dl>

-    <h4><a name="elementsOSContainer">Container boot</a></h4>
+    <h4><a id="elementsOSContainer">Container boot</a></h4>

    <p>
      When booting a domain using container based virtualization, instead
@@ -379,7 +379,7 @@
    </pre>


-    <h3><a name="elementsSysinfo">SMBIOS System Information</a></h3>
+    <h3><a id="elementsSysinfo">SMBIOS System Information</a></h3>

    <p>
      Some hypervisors allow control over what system information is
@@ -502,7 +502,7 @@
      </dd>
    </dl>

-    <h3><a name="elementsCPUAllocation">CPU Allocation</a></h3>
+    <h3><a id="elementsCPUAllocation">CPU Allocation</a></h3>

 <pre>
 &lt;domain&gt;
@@ -610,7 +610,7 @@
      </dd>
    </dl>

-    <h3><a name="elementsIOThreadsAllocation">IOThreads Allocation</a></h3>
+    <h3><a id="elementsIOThreadsAllocation">IOThreads Allocation</a></h3>
      <p>
        IOThreads are dedicated event loop threads for supported disk
        devices to perform block I/O requests in order to improve
@@ -667,7 +667,7 @@
       </dd>
    </dl>

-    <h3><a name="elementsCPUTuning">CPU Tuning</a></h3>
+    <h3><a id="elementsCPUTuning">CPU Tuning</a></h3>

 <pre>
 &lt;domain&gt;
@@ -837,7 +837,7 @@
    </dl>


-    <h3><a name="elementsMemoryAllocation">Memory Allocation</a></h3>
+    <h3><a id="elementsMemoryAllocation">Memory Allocation</a></h3>

 <pre>
 &lt;domain&gt;
@@ -910,7 +910,7 @@
    </dl>


-    <h3><a name="elementsMemoryBacking">Memory Backing</a></h3>
+    <h3><a id="elementsMemoryBacking">Memory Backing</a></h3>

 <pre>
 &lt;domain&gt;
@@ -980,7 +980,7 @@
    </dl>


-    <h3><a name="elementsMemoryTuning">Memory Tuning</a></h3>
+    <h3><a id="elementsMemoryTuning">Memory Tuning</a></h3>

 <pre>
 &lt;domain&gt;
@@ -1044,7 +1044,7 @@
    </dl>


-    <h3><a name="elementsNUMATuning">NUMA Node Tuning</a></h3>
+    <h3><a id="elementsNUMATuning">NUMA Node Tuning</a></h3>

 <pre>
 &lt;domain&gt;
@@ -1105,7 +1105,7 @@
    </dl>


-    <h3><a name="elementsBlockTuning">Block I/O Tuning</a></h3>
+    <h3><a id="elementsBlockTuning">Block I/O Tuning</a></h3>
 <pre>
 &lt;domain&gt;
  ...
@@ -1174,7 +1174,7 @@
      </dl></dd></dl>


-    <h3><a name="resPartition">Resource partitioning</a></h3>
+    <h3><a id="resPartition">Resource partitioning</a></h3>

    <p>
      Hypervisors may allow for virtual machines to be placed into
@@ -1203,7 +1203,7 @@
      in all mounted controllers. <span class="since">Since 1.0.5</span>
    </p>

-    <h3><a name="elementsCPU">CPU model and topology</a></h3>
+    <h3><a id="elementsCPU">CPU model and topology</a></h3>

    <p>
      Requirements for CPU model, its features and topology can be specified
@@ -1532,7 +1532,7 @@
      This guest NUMA specification is currently available only for QEMU/KVM.
    </p>

-    <h3><a name="elementsEvents">Events configuration</a></h3>
+    <h3><a id="elementsEvents">Events configuration</a></h3>

    <p>
      It is sometimes necessary to override the default actions taken
@@ -1643,7 +1643,7 @@
      <dd>Keep the domain running as if nothing happened.</dd>
    </dl>

-    <h3><a name="elementsPowerManagement">Power Management</a></h3>
+    <h3><a id="elementsPowerManagement">Power Management</a></h3>

    <p>
      <span class="since">Since 0.10.2</span> it is possible to
@@ -1667,7 +1667,7 @@
        left with its default value.</dd>
    </dl>

-    <h3><a name="elementsFeatures">Hypervisor features</a></h3>
+    <h3><a id="elementsFeatures">Hypervisor features</a></h3>

    <p>
      Hypervisors may allow certain CPU / machine features to be
@@ -1869,7 +1869,7 @@
      </dd>
    </dl>

-    <h3><a name="elementsTime">Time keeping</a></h3>
+    <h3><a id="elementsTime">Time keeping</a></h3>

    <p>
      The guest clock is typically initialized from the host clock.
@@ -2037,7 +2037,7 @@
      </dd>
    </dl>

-    <h3><a name="elementsPerf">Performance monitoring events</a></h3>
+    <h3><a id="elementsPerf">Performance monitoring events</a></h3>

    <p>
      Some platforms allow monitoring of performance of the virtual machine and
@@ -2218,7 +2218,7 @@
    </tr>
  </table>

-    <h3><a name="elementsDevices">Devices</a></h3>
+    <h3><a id="elementsDevices">Devices</a></h3>

    <p>
      The final set of XML elements are all used to describe devices
@@ -2245,7 +2245,7 @@
      </dd>
    </dl>

-    <h4><a name="elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>
+    <h4><a id="elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>

    <p>
      Any device that looks like a disk, be it a floppy, harddisk,
@@ -3185,7 +3185,7 @@
      </dd>
    </dl>

-    <h4><a name="elementsFilesystems">Filesystems</a></h4>
+    <h4><a id="elementsFilesystems">Filesystems</a></h4>

    <p>
      A directory on the host that can be accessed directly from the guest.
@@ -3368,7 +3368,7 @@
      </dd>
    </dl>

-    <h4><a name="elementsAddress">Device Addresses</a></h4>
+    <h4><a id="elementsAddress">Device Addresses</a></h4>

    <p>
      Many devices have an optional <code>&lt;address&gt;</code>
@@ -3485,7 +3485,7 @@
      </dd>
    </dl>

-    <h4><a name="elementsVirtio">Virtio-related options</a></h4>
+    <h4><a id="elementsVirtio">Virtio-related options</a></h4>

    <p>
      QEMU's virtio devices have some attributes related to the virtio transport under
@@ -3498,14 +3498,16 @@
      <span class="since">Since 3.5.0</span>
    </p>

-    <h4><a name="elementsControllers">Controllers</a></h4>
+    <h4><a id="elementsControllers">Controllers</a></h4>

    <p>
      Depending on the guest architecture, some device buses can
      appear more than once, with a group of virtual devices tied to a
      virtual controller.  Normally, libvirt can automatically infer such
      controllers without requiring explicit XML markup, but sometimes
-      it is necessary to provide an explicit controller element.
+      it is necessary to provide an explicit controller element, notably
+      when planning the <a href="pci-hotplug.html">PCI topology</a>
+      for guests where device hotplug is expected.
    </p>

 <pre>
@@ -3884,7 +3886,7 @@
 &lt;/devices&gt;
 ...</pre>

-    <h4><a name="elementsLease">Device leases</a></h4>
+    <h4><a id="elementsLease">Device leases</a></h4>

    <p>
      When using a lock manager, it may be desirable to record device leases
@@ -3924,9 +3926,9 @@
      </dd>
    </dl>

-    <h4><a name="elementsHostDev">Host device assignment</a></h4>
+    <h4><a id="elementsHostDev">Host device assignment</a></h4>

-    <h5><a name="elementsHostDevSubsys">USB / PCI / SCSI devices</a></h5>
+    <h5><a id="elementsHostDevSubsys">USB / PCI / SCSI devices</a></h5>

    <p>
      USB, PCI and SCSI devices attached to the host can be passed through
@@ -4237,7 +4239,7 @@
    </dl>


-    <h5><a name="elementsHostDevCaps">Block / character devices</a></h5>
+    <h5><a id="elementsHostDevCaps">Block / character devices</a></h5>

    <p>
      Block / character devices from the host can be passed through
@@ -4294,7 +4296,7 @@
      </dd>
    </dl>

-    <h4><a name="elementsRedir">Redirected devices</a></h4>
+    <h4><a id="elementsRedir">Redirected devices</a></h4>

    <p>
      USB device redirection through a character device is
@@ -4361,7 +4363,7 @@
      </dd>
    </dl>

-    <h4><a name="elementsSmartcard">Smartcard devices</a></h4>
+    <h4><a id="elementsSmartcard">Smartcard devices</a></h4>

    <p>
      A virtual smartcard device can be supplied to the guest via the
@@ -4454,7 +4456,7 @@
      smartcard, with an address of bus=0 slot=0.
    </p>

-    <h4><a name="elementsNICS">Network interfaces</a></h4>
+    <h4><a id="elementsNICS">Network interfaces</a></h4>

 <pre>
 ...
@@ -4494,7 +4496,7 @@
      as <a href="#elementsAddress">documented above</a>.
    </p>

-    <h5><a name="elementsNICSVirtual">Virtual network</a></h5>
+    <h5><a id="elementsNICSVirtual">Virtual network</a></h5>

    <p>
      <strong><em>
@@ -4600,7 +4602,7 @@
 &lt;/devices&gt;
 ...</pre>

-    <h5><a name="elementsNICSBridge">Bridge to LAN</a></h5>
+    <h5><a id="elementsNICSBridge">Bridge to LAN</a></h5>

    <p>
      <strong><em>
@@ -4691,7 +4693,7 @@
 &lt;/devices&gt;
 ...</pre>

-    <h5><a name="elementsNICSSlirp">Userspace SLIRP stack</a></h5>
+    <h5><a id="elementsNICSSlirp">Userspace SLIRP stack</a></h5>

    <p>
      Provides a virtual LAN with NAT to the outside world. The virtual
@@ -4714,7 +4716,7 @@
 ...</pre>


-    <h5><a name="elementsNICSEthernet">Generic ethernet connection</a></h5>
+    <h5><a id="elementsNICSEthernet">Generic ethernet connection</a></h5>

    <p>
      Provides a means for the administrator to execute an arbitrary script
@@ -4738,7 +4740,7 @@
 &lt;/devices&gt;
 ...</pre>

-    <h5><a name="elementsNICSDirect">Direct attachment to physical interface</a></h5>
+    <h5><a id="elementsNICSDirect">Direct attachment to physical interface</a></h5>

    <p>
      Provides direct attachment of the virtual machine's NIC to the given
@@ -4883,7 +4885,7 @@
 </pre>


-    <h5><a name="elementsNICSHostdev">PCI Passthrough</a></h5>
+    <h5><a id="elementsNICSHostdev">PCI Passthrough</a></h5>

    <p>
      A PCI network device (specified by the &lt;source&gt; element)
@@ -4956,7 +4958,7 @@
 ...</pre>


-    <h5><a name="elementsNICSMulticast">Multicast tunnel</a></h5>
+    <h5><a id="elementsNICSMulticast">Multicast tunnel</a></h5>

    <p>
      A multicast group is setup to represent a virtual network. Any VMs
@@ -4980,7 +4982,7 @@
 &lt;/devices&gt;
 ...</pre>

-    <h5><a name="elementsNICSTCP">TCP tunnel</a></h5>
+    <h5><a id="elementsNICSTCP">TCP tunnel</a></h5>

    <p>
      A TCP client/server architecture provides a virtual network. One VM
@@ -5006,7 +5008,7 @@
 &lt;/devices&gt;
 ...</pre>

-    <h5><a name="elementsNICSUDP">UDP unicast tunnel</a></h5>
+    <h5><a id="elementsNICSUDP">UDP unicast tunnel</a></h5>

    <p>
    A UDP unicast architecture provides a virtual network which enables
@@ -5030,7 +5032,7 @@
 &lt;/devices&gt;
 ...</pre>

-    <h5><a name="elementsNICSModel">Setting the NIC model</a></h5>
+    <h5><a id="elementsNICSModel">Setting the NIC model</a></h5>

 <pre>
 ...
@@ -5065,7 +5067,7 @@ qemu-kvm -net nic,model=? /dev/null
      ne2k_isa i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio
    </p>

-    <h5><a name="elementsDriverBackendOptions">Setting NIC driver-specific options</a></h5>
+    <h5><a id="elementsDriverBackendOptions">Setting NIC driver-specific options</a></h5>

 <pre>
 ...
@@ -5074,7 +5076,7 @@ qemu-kvm -net nic,model=? /dev/null
    &lt;source network='default'/&gt;
    &lt;target dev='vnet1'/&gt;
    &lt;model type='virtio'/&gt;
-    <b>&lt;driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='off' queues='5' rx_queue_size='256'&gt;
+    <b>&lt;driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='off' queues='5' rx_queue_size='256' tx_queue_size='256'&gt;
      &lt;host csum='off' gso='off' tso4='off' tso6='off' ecn='off' ufo='off' mrg_rxbuf='off'/&gt;
      &lt;guest csum='off' tso4='off' tso6='off' ecn='off' ufo='off'/&gt;
    &lt;/driver&gt;
@@ -5204,6 +5206,22 @@ qemu-kvm -net nic,model=? /dev/null
        <b>In general you should leave this option alone, unless you
        are very certain you know what you are doing.</b>
      </dd>
+      <dt><code>tx_queue_size</code></dt>
+      <dd>
+        The optional <code>tx_queue_size</code> attribute controls
+        the size of virtio ring for each queue as described above.
+        The default value is hypervisor dependent and may change
+        across its releases. Moreover, some hypervisors may pose
+        some restrictions on actual value. For instance, QEMU
+        v2.9  requires value to be a power of two from [256, 1024]
+        range. In addition to that, this may work only for a subset of
+        interface types, e.g. aforementioned QEMU enables this option
+        only for <code>vhostuser</code> type.
+        <span class="since">Since 3.7.0 (QEMU and KVM only)</span><br/><br/>
+
+        <b>In general you should leave this option alone, unless you
+        are very certain you know what you are doing.</b>
+      </dd>
      <dt>virtio options</dt>
      <dd>
        For virtio interfaces,
@@ -5240,7 +5258,7 @@ qemu-kvm -net nic,model=? /dev/null
      </dd>
    </dl>

-    <h5><a name="elementsBackendOptions">Setting network backend-specific options</a></h5>
+    <h5><a id="elementsBackendOptions">Setting network backend-specific options</a></h5>

 <pre>
 ...
@@ -5271,7 +5289,7 @@ qemu-kvm -net nic,model=? /dev/null
      adjust the size of send buffer in the host. <span class="since">Since
      0.8.8</span>
    </p>
-    <h5><a name="elementsNICSTargetOverride">Overriding the target element</a></h5>
+    <h5><a id="elementsNICSTargetOverride">Overriding the target element</a></h5>

 <pre>
 ...
@@ -5309,7 +5327,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h5><a name="elementsNICSBoot">Specifying boot order</a></h5>
+    <h5><a id="elementsNICSBoot">Specifying boot order</a></h5>

 <pre>
 ...
@@ -5332,7 +5350,7 @@ qemu-kvm -net nic,model=? /dev/null
      <span class="since">Since 0.8.8</span>
    </p>

-    <h5><a name="elementsNICSROM">Interface ROM BIOS configuration</a></h5>
+    <h5><a id="elementsNICSROM">Interface ROM BIOS configuration</a></h5>

 <pre>
 ...
@@ -5361,7 +5379,7 @@ qemu-kvm -net nic,model=? /dev/null
      network device.
      <span class="since">Since 0.9.10 (QEMU and KVM only)</span>.
    </p>
-    <h5><a name="elementDomain">Setting up a network backend in a driver domain</a></h5>
+    <h5><a id="elementDomain">Setting up a network backend in a driver domain</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5385,7 +5403,7 @@ qemu-kvm -net nic,model=? /dev/null
      <span class="since">Since 1.2.13 (Xen only)</span>
    </p>

-    <h5><a name="elementQoS">Quality of service</a></h5>
+    <h5><a id="elementQoS">Quality of service</a></h5>

 <pre>
 ...
@@ -5409,7 +5427,7 @@ qemu-kvm -net nic,model=? /dev/null
      the Network XML.
    </p>

-    <h5><a name="elementVlanTag">Setting VLAN tag (on supported network types only)</a></h5>
+    <h5><a id="elementVlanTag">Setting VLAN tag (on supported network types only)</a></h5>

 <pre>
 ...
@@ -5477,7 +5495,7 @@ qemu-kvm -net nic,model=? /dev/null
      traffic for that VLAN will be tagged.
    </p>

-    <h5><a name="elementLink">Modifying virtual link state</a></h5>
+    <h5><a id="elementLink">Modifying virtual link state</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5498,7 +5516,7 @@ qemu-kvm -net nic,model=? /dev/null
      <span class="since">Since 0.9.5</span>
    </p>

-    <h5><a name="mtu">MTU configuration</a></h5>
+    <h5><a id="mtu">MTU configuration</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5517,7 +5535,7 @@ qemu-kvm -net nic,model=? /dev/null
      <span class="since">Since 3.1.0</span>
    </p>

-    <h5><a name="coalesce">Coalesce settings</a></h5>
+    <h5><a id="coalesce">Coalesce settings</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5544,7 +5562,7 @@ qemu-kvm -net nic,model=? /dev/null
      <span class="since">Since 3.3.0</span>
    </p>

-    <h5><a name="ipconfig">IP configuration</a></h5>
+    <h5><a id="ipconfig">IP configuration</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5623,7 +5641,7 @@ qemu-kvm -net nic,model=? /dev/null
      configure the guest side of the interface (described above).
    </p>

-    <h5><a name="elementVhostuser">vhost-user interface</a></h5>
+    <h5><a id="elementVhostuser">vhost-user interface</a></h5>

    <p>
    <span class="since">Since 1.2.7</span> the vhost-user enables the
@@ -5660,7 +5678,7 @@ qemu-kvm -net nic,model=? /dev/null
      <code>&lt;model&gt;</code> element is mandatory.
    </p>

-    <h5><a name="elementNwfilter">Traffic filtering with NWFilter</a></h5>
+    <h5><a id="elementNwfilter">Traffic filtering with NWFilter</a></h5>

    <p>
    <span class="since">Since 0.8.0</span> an <code>nwfilter</code> profile
@@ -5700,7 +5718,7 @@ qemu-kvm -net nic,model=? /dev/null
    </p>


-    <h4><a name="elementsInput">Input devices</a></h4>
+    <h4><a id="elementsInput">Input devices</a></h4>

    <p>
      Input devices allow interaction with the graphical framebuffer
@@ -5755,7 +5773,7 @@ qemu-kvm -net nic,model=? /dev/null
        set. (<span class="since">Since 3.5.0</span>)
    </p>

-    <h4><a name="elementsHub">Hub devices</a></h4>
+    <h4><a id="elementsHub">Hub devices</a></h4>

    <p>
      A hub is a device that expands a single port into several so
@@ -5784,7 +5802,7 @@ qemu-kvm -net nic,model=? /dev/null
      above</a>.
    </p>

-    <h4><a name="elementsGraphics">Graphical framebuffers</a></h4>
+    <h4><a id="elementsGraphics">Graphical framebuffers</a></h4>

    <p>
      A graphics device allows for graphical interaction with the
@@ -6082,7 +6100,7 @@ qemu-kvm -net nic,model=? /dev/null
      </dd>
    </dl>

-    <h4><a name="elementsVideo">Video devices</a></h4>
+    <h4><a id="elementsVideo">Video devices</a></h4>
    <p>
      A video device.
    </p>
@@ -6197,7 +6215,7 @@ qemu-kvm -net nic,model=? /dev/null
      </dd>
    </dl>

-    <h4><a name="elementsConsole">Consoles, serial, parallel &amp; channel devices</a></h4>
+    <h4><a id="elementsConsole">Consoles, serial, parallel &amp; channel devices</a></h4>

    <p>
      A character device provides a way to interact with the virtual machine.
@@ -6283,14 +6301,25 @@ qemu-kvm -net nic,model=? /dev/null
      slot.
    </p>

-    <h5><a name="elementsCharGuestInterface">Guest interface</a></h5>
+    <p>
+      For character device with type <code>unix</code> or <code>tcp</code>
+      the <code>source</code> has an optional element <code>reconnect</code>
+      which configures reconnect timeout if the connection is lost.
+      There are two attributes, <code>enabled</code> where possible
+      values are "yes" and "no" and <code>timeout</code> which is in
+      seconds. The <code>reconnect</code> attribute is valid only
+      for <code>connect</code> mode.
+      <span class="since">Since 3.7.0 (QEMU driver only)</span>.
+    </p>
+
+    <h5><a id="elementsCharGuestInterface">Guest interface</a></h5>

    <p>
      A character device presents itself to the guest as one of the following
      types.
    </p>

-    <h6><a name="elementCharParallel">Parallel port</a></h6>
+    <h6><a id="elementCharParallel">Parallel port</a></h6>

 <pre>
 ...
@@ -6308,7 +6337,7 @@ qemu-kvm -net nic,model=? /dev/null
      usually 0, 1 or 2 parallel ports.
    </p>

-    <h6><a name="elementCharSerial">Serial port</a></h6>
+    <h6><a id="elementCharSerial">Serial port</a></h6>

 <pre>
 ...
@@ -6337,7 +6366,7 @@ qemu-kvm -net nic,model=? /dev/null
      <code>type='pci'</code> to select desired location on the PCI bus.
    </p>

-    <h6><a name="elementCharConsole">Console</a></h6>
+    <h6><a id="elementCharConsole">Console</a></h6>

    <p>
      The console element is used to represent interactive consoles. Depending
@@ -6409,7 +6438,7 @@ qemu-kvm -net nic,model=? /dev/null
      only 1 console.
    </p>

-    <h6><a name="elementCharChannel">Channel</a></h6>
+    <h6><a id="elementCharChannel">Channel</a></h6>

    <p>
      This represents a private communication channel between the host and the
@@ -6501,14 +6530,14 @@ qemu-kvm -net nic,model=? /dev/null
        <span class="since">Since 0.8.8</span></dd>
    </dl>

-    <h5><a name="elementsCharHostInterface">Host interface</a></h5>
+    <h5><a id="elementsCharHostInterface">Host interface</a></h5>

    <p>
      A character device presents itself to the host as one of the following
      types.
    </p>

-    <h6><a name="elementsCharSTDIO">Domain logfile</a></h6>
+    <h6><a id="elementsCharSTDIO">Domain logfile</a></h6>

    <p>
      This disables all input on the character device, and sends output
@@ -6525,7 +6554,7 @@ qemu-kvm -net nic,model=? /dev/null
 ...</pre>


-    <h6><a name="elementsCharFle">Device logfile</a></h6>
+    <h6><a id="elementsCharFle">Device logfile</a></h6>

    <p>
      A file is opened and all data sent to the character
@@ -6542,7 +6571,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharVC">Virtual console</a></h6>
+    <h6><a id="elementsCharVC">Virtual console</a></h6>

    <p>
      Connects the character device to the graphical framebuffer in
@@ -6559,7 +6588,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharNull">Null device</a></h6>
+    <h6><a id="elementsCharNull">Null device</a></h6>

    <p>
      Connects the character device to the void. No data is ever
@@ -6575,7 +6604,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharPTY">Pseudo TTY</a></h6>
+    <h6><a id="elementsCharPTY">Pseudo TTY</a></h6>

    <p>
      A Pseudo TTY is allocated using /dev/ptmx. A suitable client
@@ -6600,7 +6629,7 @@ qemu-kvm -net nic,model=? /dev/null
      with existing syntax for &lt;console&gt; tags.
    </p>

-    <h6><a name="elementsCharHost">Host device proxy</a></h6>
+    <h6><a id="elementsCharHost">Host device proxy</a></h6>

    <p>
      The character device is passed through to the underlying
@@ -6620,7 +6649,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharPipe">Named pipe</a></h6>
+    <h6><a id="elementsCharPipe">Named pipe</a></h6>

    <p>
      The character device writes output to a named pipe. See pipe(7) for
@@ -6637,7 +6666,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharTCP">TCP client/server</a></h6>
+    <h6><a id="elementsCharTCP">TCP client/server</a></h6>

    <p>
      The character device acts as a TCP client connecting to a
@@ -6726,7 +6755,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharUDP">UDP network console</a></h6>
+    <h6><a id="elementsCharUDP">UDP network console</a></h6>

    <p>
      The character device acts as a UDP netconsole service,
@@ -6744,7 +6773,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharUNIX">UNIX domain socket client/server</a></h6>
+    <h6><a id="elementsCharUNIX">UNIX domain socket client/server</a></h6>

    <p>
      The character device acts as a UNIX domain socket server,
@@ -6761,7 +6790,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsCharSpiceport">Spice channel</a></h6>
+    <h6><a id="elementsCharSpiceport">Spice channel</a></h6>

    <p>
      The character device is accessible through spice connection
@@ -6784,7 +6813,7 @@ qemu-kvm -net nic,model=? /dev/null
 &lt;/devices&gt;
 ...</pre>

-    <h6><a name="elementsNmdm">Nmdm device</a></h6>
+    <h6><a id="elementsNmdm">Nmdm device</a></h6>

    <p>
      The nmdm device driver, available on FreeBSD, provides two
@@ -6815,7 +6844,7 @@ qemu-kvm -net nic,model=? /dev/null
      to the guest console. Device is specified by a fully qualified path.</dd>
    </dl>

-    <h4><a name="elementsSound">Sound devices</a></h4>
+    <h4><a id="elementsSound">Sound devices</a></h4>

    <p>
      A virtual sound card can be attached to the host via the
@@ -6868,7 +6897,7 @@ qemu-kvm -net nic,model=? /dev/null
      slot, <a href="#elementsAddress">documented above</a>.
    </p>

-    <h4><a name="elementsWatchdog">Watchdog device</a></h4>
+    <h4><a id="elementsWatchdog">Watchdog device</a></h4>

    <p>
      A virtual hardware watchdog device can be added to the guest via
@@ -6914,10 +6943,10 @@ qemu-kvm -net nic,model=? /dev/null
        QEMU and KVM support:
        </p>
        <ul>
-          <li> 'i6300esb' &mdash; the recommended device,
+          <li>'i6300esb' - the recommended device,
            emulating a PCI Intel 6300ESB </li>
-          <li> 'ib700' &mdash; emulating an ISA iBase IB700 </li>
-          <li> 'diag288' &mdash; emulating an S390 DIAG288 device
+          <li>'ib700' - emulating an ISA iBase IB700 </li>
+          <li>'diag288' - emulating an S390 DIAG288 device
            <span class="since">Since 1.2.17</span></li>
        </ul>
      </dd>
@@ -6932,15 +6961,15 @@ qemu-kvm -net nic,model=? /dev/null
        QEMU and KVM support:
        </p>
        <ul>
-          <li>'reset' &mdash; default, forcefully reset the guest</li>
-          <li>'shutdown' &mdash; gracefully shutdown the guest
+          <li>'reset' - default, forcefully reset the guest</li>
+          <li>'shutdown' - gracefully shutdown the guest
            (not recommended) </li>
-          <li>'poweroff' &mdash; forcefully power off the guest</li>
-          <li>'pause' &mdash; pause the guest</li>
-          <li>'none' &mdash; do nothing</li>
-          <li>'dump' &mdash; automatically dump the guest
+          <li>'poweroff' - forcefully power off the guest</li>
+          <li>'pause' - pause the guest</li>
+          <li>'none' - do nothing</li>
+          <li>'dump' - automatically dump the guest
            <span class="since">Since 0.8.7</span></li>
-          <li>'inject-nmi' &mdash; inject a non-maskable interrupt
+          <li>'inject-nmi' - inject a non-maskable interrupt
            into the guest
            <span class="since">Since 1.2.17</span></li>
        </ul>
@@ -6958,7 +6987,7 @@ qemu-kvm -net nic,model=? /dev/null
      </dd>
    </dl>

-    <h4><a name="elementsMemBalloon">Memory balloon device</a></h4>
+    <h4><a id="elementsMemBalloon">Memory balloon device</a></h4>

    <p>
      A virtual memory balloon device is added to all Xen and KVM/QEMU
@@ -7005,8 +7034,8 @@ qemu-kvm -net nic,model=? /dev/null
          the virtualization platform
        </p>
        <ul>
-          <li>'virtio' &mdash; default with QEMU/KVM</li>
-          <li>'xen' &mdash; default with Xen</li>
+          <li>'virtio' - default with QEMU/KVM</li>
+          <li>'xen' - default with Xen</li>
        </ul>
      </dd>
      <dt><code>autodeflate</code></dt>
@@ -7043,7 +7072,7 @@ qemu-kvm -net nic,model=? /dev/null
        set. (<span class="since">Since 3.5.0</span>)
      </dd>
    </dl>
-    <h4><a name="elementsRng">Random number generator device</a></h4>
+    <h4><a id="elementsRng">Random number generator device</a></h4>

    <p>
      The virtual random number generator device allows the host to pass
@@ -7078,7 +7107,7 @@ qemu-kvm -net nic,model=? /dev/null
          the virtualization platform:
        </p>
        <ul>
-          <li>'virtio' &mdash; supported by qemu and virtio-rng kernel module</li>
+          <li>'virtio' - supported by qemu and virtio-rng kernel module</li>
        </ul>
      </dd>
      <dt><code>rate</code></dt>
@@ -7137,7 +7166,7 @@ qemu-kvm -net nic,model=? /dev/null

    </dl>

-    <h4><a name="elementsTpm">TPM device</a></h4>
+    <h4><a id="elementsTpm">TPM device</a></h4>

    <p>
      The TPM device enables a QEMU guest to have access to TPM
@@ -7197,7 +7226,7 @@ qemu-kvm -net nic,model=? /dev/null
      </dd>
    </dl>

-    <h4><a name="elementsNVRAM">NVRAM device</a></h4>
+    <h4><a id="elementsNVRAM">NVRAM device</a></h4>
    <p>
      nvram device is always added to pSeries guest on PPC64, and its address
      is allowed to be changed.  Element <code>nvram</code> (only valid for
@@ -7231,7 +7260,7 @@ qemu-kvm -net nic,model=? /dev/null
    </dd>
  </dl>

-    <h4><a name="elementsPanic">panic device</a></h4>
+    <h4><a id="elementsPanic">panic device</a></h4>
    <p>
      panic device enables libvirt to receive panic notification from a QEMU
      guest.
@@ -7270,11 +7299,11 @@ qemu-kvm -net nic,model=? /dev/null
          is missing depends on the hypervisor and guest arch.
        </p>
        <ul>
-          <li>'isa' &mdash; for ISA pvpanic device</li>
-          <li>'pseries' &mdash; default and valid only for pSeries guests.</li>
-          <li>'hyperv' &mdash; for Hyper-V crash CPU feature.
+          <li>'isa' - for ISA pvpanic device</li>
+          <li>'pseries' - default and valid only for pSeries guests.</li>
+          <li>'hyperv' - for Hyper-V crash CPU feature.
            <span class="since">Since 1.3.0, QEMU and KVM only</span></li>
-          <li>'s390' &mdash; default for S390 guests.
+          <li>'s390' - default for S390 guests.
            <span class="since">Since 1.3.5</span></li>
        </ul>
      </dd>
@@ -7288,7 +7317,7 @@ qemu-kvm -net nic,model=? /dev/null
    </dd>
  </dl>

-  <h4><a name="elementsShmem">Shared memory device</a></h4>
+  <h4><a id="elementsShmem">Shared memory device</a></h4>

    <p>
      A shared memory device allows to share a memory region between
@@ -7352,7 +7381,7 @@ qemu-kvm -net nic,model=? /dev/null
    </dd>
  </dl>

-    <h4><a name="elementsMemory">Memory devices</a></h4>
+    <h4><a id="elementsMemory">Memory devices</a></h4>

    <p>
        In addition to the initial memory assigned to the guest, memory devices
@@ -7495,7 +7524,7 @@ qemu-kvm -net nic,model=? /dev/null
      </dd>
    </dl>

-    <h4><a name="elementsIommu">IOMMU devices</a></h4>
+    <h4><a id="elementsIommu">IOMMU devices</a></h4>

    <p>
      The <code>iommu</code> element can be used to add an IOMMU device.
@@ -7575,7 +7604,7 @@ qemu-kvm -net nic,model=? /dev/null
      </dd>
    </dl>

-    <h3><a name="seclabel">Security label</a></h3>
+    <h3><a id="seclabel">Security label</a></h3>

    <p>
      The <code>seclabel</code> element allows control over the
@@ -7704,7 +7733,7 @@ qemu-kvm -net nic,model=? /dev/null
      being on a file system that lacks security labeling.
    </p>

-    <h3><a name="keywrap">Key Wrap</a></h3>
+    <h3><a id="keywrap">Key Wrap</a></h3>

       <p>The content of the optional <code>keywrap</code> element specifies
        whether the guest will be allowed to perform the S390 cryptographic key
@@ -7743,7 +7772,7 @@ qemu-kvm -net nic,model=? /dev/null

    <p>Note: DEA/TDEA is synonymous with DES/TDES.</p>

-    <h2><a name="examples">Example configs</a></h2>
+    <h2><a id="examples">Example configs</a></h2>

    <p>
      Example configurations for each driver are provide on the
--- a/docs/formatdomaincaps.html.in
+++ b/docs/formatdomaincaps.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Domain capabilities XML format</h1>

    <ul id="toc"></ul>

-    <h2><a name="Overview">Overview</a></h2>
+    <h2><a id="Overview">Overview</a></h2>

    <p>Sometimes, when a new domain is to be created it may come handy to know
    the capabilities of the hypervisor so the correct combination of devices and
@@ -37,7 +37,7 @@
    management application to choose an appropriate mode for a pass-through
    host device as well as which adapter to utilize.</p>

-    <h2><a name="elements">Element and attribute overview</a></h2>
+    <h2><a id="elements">Element and attribute overview</a></h2>

    <p> A new query interface was added to the virConnect API's to retrieve the
    XML listing of the set of domain capabilities (<span class="since">Since
@@ -79,7 +79,7 @@

    </dl>

-    <h3><a name="elementsCPUAllocation">CPU Allocation</a></h3>
+    <h3><a id="elementsCPUAllocation">CPU Allocation</a></h3>

    <p>Before any devices capability occurs, there might be a info on domain
    wide capabilities, e.g. virtual CPUs:</p>
@@ -97,7 +97,7 @@
      <dd>The maximum number of supported virtual CPUs</dd>
    </dl>

-    <h3><a name="elementsOSBIOS">BIOS bootloader</a></h3>
+    <h3><a id="elementsOSBIOS">BIOS bootloader</a></h3>

    <p>Sometimes users might want to tweak some BIOS knobs or use
    UEFI. For cases like that, <a
@@ -143,7 +143,7 @@
      &lt;loader/&gt; element.</dd>
    </dl>

-    <h3><a name="elementsCPU">CPU configuration</a></h3>
+    <h3><a id="elementsCPU">CPU configuration</a></h3>

    <p>
      The <code>cpu</code> element exposes options usable for configuring
@@ -208,7 +208,7 @@
      </dd>
    </dl>

-    <h3><a name="elementsDevices">Devices</a></h3>
+    <h3><a id="elementsDevices">Devices</a></h3>

    <p>
      Another set of XML elements describe the supported devices and their
@@ -240,7 +240,7 @@
    support the values <code>disk</code>, <code>cdrom</code>,
    <code>floppy</code>, or <code>lun</code>.</p>

-    <h4><a name="elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>
+    <h4><a id="elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>
    <p>Disk capabilities are exposed under the <code>disk</code> element. For
    instance:</p>

@@ -283,7 +283,7 @@
    </dl>


-    <h4><a name="elementsGraphics">Graphical framebuffers</a></h4>
+    <h4><a id="elementsGraphics">Graphical framebuffers</a></h4>
    <p>Graphics device capabilities are exposed under the
    <code>graphics</code> element. For instance:</p>

@@ -310,7 +310,7 @@
    </dl>


-    <h4><a name="elementsVideo">Video device</a></h4>
+    <h4><a id="elementsVideo">Video device</a></h4>
    <p>Video device capabilities are exposed under the
    <code>video</code> element. For instance:</p>

@@ -339,7 +339,7 @@
    </dl>


-    <h4><a name="elementsHostDev">Host device assignment</a></h4>
+    <h4><a id="elementsHostDev">Host device assignment</a></h4>
    <p>Some host devices can be passed through to a guest (e.g. USB, PCI and
    SCSI). Well, only if the following is enabled:</p>

@@ -401,7 +401,7 @@
      element.</dd>
    </dl>

-    <h3><a name="elementsFeatures">Features</a></h3>
+    <h3><a id="elementsFeatures">Features</a></h3>

    <p>One more set of XML elements describe the supported features and
    their capabilities. All features occur as children of the main
@@ -431,7 +431,7 @@
    the domain XML documentation.
    </p>

-    <h4><a name="elementsGIC">GIC capabilities</a></h4>
+    <h4><a id="elementsGIC">GIC capabilities</a></h4>

    <p>GIC capabilities are exposed under the <code>gic</code> element.</p>

--- a/docs/formatnetwork.html.in
+++ b/docs/formatnetwork.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Network XML format</h1>
@@ -13,7 +13,7 @@
      <a href="https://wiki.libvirt.org/page/Networking">relevant wiki page</a>.
    </p>

-    <h2><a name="elements">Element and attribute overview</a></h2>
+    <h2><a id="elements">Element and attribute overview</a></h2>

    <p>
      The root element required for all virtual networks is
@@ -27,7 +27,7 @@
      available <span class="since">since 0.3.0</span>
    </p>

-    <h3><a name="elementsMetadata">General metadata</a></h3>
+    <h3><a id="elementsMetadata">General metadata</a></h3>

    <p>
      The first elements provide basic metadata about the virtual
@@ -83,7 +83,7 @@
        override the setting in the network.</dd>
    </dl>

-    <h3><a name="elementsConnect">Connectivity</a></h3>
+    <h3><a id="elementsConnect">Connectivity</a></h3>

    <p>
      The next set of elements control how a virtual network is
@@ -514,7 +514,7 @@

      </dd>
    </dl>
-    <h5><a name="elementQoS">Quality of service</a></h5>
+    <h5><a id="elementQoS">Quality of service</a></h5>

 <pre>
 ...
@@ -634,7 +634,7 @@
        <span class="since">since 1.0.1</span>.
      </p>

-    <h5><a name="elementVlanTag">Setting VLAN tag (on supported network types only)</a></h5>
+    <h5><a id="elementVlanTag">Setting VLAN tag (on supported network types only)</a></h5>

 <pre>
 &lt;network&gt;
@@ -712,7 +712,7 @@
      or <code>&lt;interface&gt;</code>.
    </p>

-    <h5><a name="elementsPortgroup">Portgroups</a></h5>
+    <h5><a id="elementsPortgroup">Portgroups</a></h5>

 <pre>
 ...
@@ -790,7 +790,7 @@
      setting in the portgroup.
    </p>

-    <h5><a name="elementsStaticroute">Static Routes</a></h5>
+    <h5><a id="elementsStaticroute">Static Routes</a></h5>
    <p>
      Static route definitions are used to provide routing information
      to the virtualization host for networks which are not directly
@@ -845,7 +845,7 @@
 ...
    </pre>

-    <h3><a name="elementsAddress">Addressing</a></h3>
+    <h3><a id="elementsAddress">Addressing</a></h3>

    <p>
      The final set of elements define the addresses (IPv4 and/or
@@ -997,7 +997,7 @@
        <code>prefix</code> attribute, which is an integer (for example,
        <code>netmask='255.255.255.0'</code> could also be given as
        <code>prefix='24'</code>). The <code>family</code> attribute is used
-        to specify the type of address &mdash; <code>ipv4</code> or
+        to specify the type of address - <code>ipv4</code> or
        <code>ipv6</code>; if no <code>family</code> is given,
        <code>ipv4</code> is assumed. More than one address of each family can
        be defined for a network. The optional <code>localPtr</code> attribute
@@ -1079,9 +1079,9 @@
      </dd>
    </dl>

-    <h2><a name="examples">Example configuration</a></h2>
+    <h2><a id="examples">Example configuration</a></h2>

-    <h3><a name="examplesNAT">NAT based network</a></h3>
+    <h3><a id="examplesNAT">NAT based network</a></h3>

    <p>
      This example is the so called "default" virtual network. It is
@@ -1129,7 +1129,7 @@
  &lt;/ip&gt;
 &lt;/network&gt;</pre>

-    <h3><a name="examplesRoute">Routed network config</a></h3>
+    <h3><a id="examplesRoute">Routed network config</a></h3>

    <p>
      This is a variant on the default network which routes traffic
@@ -1211,7 +1211,7 @@
  &lt;route family="ipv6" address="2001:db8:ca2:8::" prefix="64" gateway="2001:db8:ca2:7::4"/&gt;
 &lt;/network&gt;</pre>

-    <h3><a name="examplesPrivate">Isolated network config</a></h3>
+    <h3><a id="examplesPrivate">Isolated network config</a></h3>

    <p>
      This variant provides a completely isolated private network
@@ -1233,7 +1233,7 @@
  &lt;ip family="ipv6" address="2001:db8:ca2:3::1" prefix="64"/&gt;
 &lt;/network&gt;</pre>

-    <h3><a name="examplesPrivate6">Isolated IPv6 network config</a></h3>
+    <h3><a id="examplesPrivate6">Isolated IPv6 network config</a></h3>

    <p>
      This variation of an isolated network defines only IPv6.
@@ -1259,7 +1259,7 @@
  &lt;/ip&gt;
 &lt;/network&gt;</pre>

-    <h3><a name="examplesBridge">Using an existing host bridge</a></h3>
+    <h3><a id="examplesBridge">Using an existing host bridge</a></h3>

    <p>
      <span class="since">Since 0.9.4</span>
@@ -1277,7 +1277,7 @@
  &lt;bridge name="br0"/&gt;
 &lt;/network&gt;</pre>

-    <h3><a name="examplesDirect">Using a macvtap "direct" connection</a></h3>
+    <h3><a id="examplesDirect">Using a macvtap "direct" connection</a></h3>

    <p>
      <span class="since">Since 0.9.4, QEMU and KVM only, requires
@@ -1312,7 +1312,7 @@
  &lt;/forward&gt;
 &lt;/network&gt;</pre>

-    <h3><a name="examplesNoGateway">Network config with no gateway addresses</a></h3>
+    <h3><a id="examplesNoGateway">Network config with no gateway addresses</a></h3>

    <p>
    A valid network definition can contain no IPv4 or IPv6 addresses.  Such a definition
--- a/docs/formatnode.html.in
+++ b/docs/formatnode.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Node devices XML format</h1>

    <ul id="toc"></ul>

-    <h2><a name="NodedevAttributes">Node Device XML</a></h2>
+    <h2><a id="NodedevAttributes">Node Device XML</a></h2>

    <p>
      There are several libvirt functions, all with the
@@ -340,7 +340,7 @@
      </dd>
    </dl>

-    <h2><a name="nodeExample">Examples</a></h2>
+    <h2><a id="nodeExample">Examples</a></h2>

    <p>The following are some example node device XML outputs:</p>
    <pre>
--- a/docs/formatnwfilter.html.in
+++ b/docs/formatnwfilter.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Network Filters</h1>
@@ -12,7 +12,7 @@
      their goals, concepts and XML format.
    </p>

-    <h2><a name="goals">Goals and background</a></h2>
+    <h2><a id="goals">Goals and background</a></h2>

    <p>
      The goal of the network filtering XML is to enable administrators
@@ -43,7 +43,7 @@
      (QEMU, KVM)</span>
    </p>

-    <h2><a name="nwfconcepts">Concepts</a></h2>
+    <h2><a id="nwfconcepts">Concepts</a></h2>
    <p>
      The network traffic filtering subsystem enables configuration
      of network traffic filtering rules on individual network
@@ -111,7 +111,7 @@
      <br/><br/>
    </p>

-    <h3><a name="nwfconceptschains">Filtering chains</a></h3>
+    <h3><a id="nwfconceptschains">Filtering chains</a></h3>
    <p>
      Filtering rules are organized in filter chains. These chains can be
      thought of as having a tree structure with packet
@@ -192,7 +192,7 @@
      traverse the ARP chain.
      <br/><br/>
    </p>
-    <h3><a name="nwfconceptschainpriorities">Filtering chain priorities</a></h3>
+    <h3><a id="nwfconceptschainpriorities">Filtering chain priorities</a></h3>
    <p>
      All chains are connected to the <code>root</code> chain. The order in
      which those chains are accessed is influenced by the priority of the
@@ -236,7 +236,7 @@
      node. The above example filter shows the default priority of -500
      for <code>arp</code> chains.
    </p>
-    <h3><a name="nwfconceptsvars">Usage of variables in filters</a></h3>
+    <h3><a id="nwfconceptsvars">Usage of variables in filters</a></h3>
    <p>

      Two variables names have so far been reserved for usage by the
@@ -374,7 +374,7 @@ DSTPORTS = [ 80, 8080 ]
      former notation always assumes the iterator with Id '0'.
    </p>

-    <h3><a name="nwfelemsRulesAdvIPAddrDetection">Automatic IP address detection</a></h3>
+    <h3><a id="nwfelemsRulesAdvIPAddrDetection">Automatic IP address detection</a></h3>
    <p>
       The detection of IP addresses used on a virtual machine's interface
       is automatically activated if the variable <code>IP</code> is referenced
@@ -448,7 +448,7 @@ DSTPORTS = [ 80, 8080 ]
 &lt;/interface&gt;
 </pre>

-    <h3><a name="nwfelemsReservedVars">Reserved Variables</a></h3>
+    <h3><a id="nwfelemsReservedVars">Reserved Variables</a></h3>
    <p>
      The following table lists reserved variables in use by libvirt.
    </p>
@@ -485,7 +485,7 @@ DSTPORTS = [ 80, 8080 ]
       </tr>
      </table>

-    <h2><a name="nwfelems">Element and attribute overview</a></h2>
+    <h2><a id="nwfelems">Element and attribute overview</a></h2>

    <p>
      The root element required for all network filters is
@@ -498,7 +498,7 @@ DSTPORTS = [ 80, 8080 ]
      ipv4, ipv6, arp and rarp</code>.
    </p>

-    <h3><a name="nwfelemsRefs">References to other filters</a></h3>
+    <h3><a id="nwfelemsRefs">References to other filters</a></h3>
    <p>
     Any filter may hold references to other filters. Individual
     filters may be referenced multiple times in a filter tree but
@@ -536,7 +536,7 @@ DSTPORTS = [ 80, 8080 ]
    attached.
    </p>

-    <h3><a name="nwfelemsRules">Filter rules</a></h3>
+    <h3><a id="nwfelemsRules">Filter rules</a></h3>
    <p>
    The following XML shows a simple example of a network
    traffic filter implementing a rule to drop traffic if
@@ -618,7 +618,7 @@ DSTPORTS = [ 80, 8080 ]
     filtered.
    </p>

-    <h4><a name="nwfelemsRulesProto">Supported protocols</a></h4>
+    <h4><a id="nwfelemsRulesProto">Supported protocols</a></h4>
    <p>
     The following sections enumerate the list of protocols that
     are supported by the network filtering subsystem. The
@@ -677,7 +677,7 @@ DSTPORTS = [ 80, 8080 ]
    </p>


-    <h5><a name="nwfelemsRulesProtoMAC">MAC (Ethernet)</a></h5>
+    <h5><a id="nwfelemsRulesProtoMAC">MAC (Ethernet)</a></h5>
    <p>
      Protocol ID: <code>mac</code>
      <br/>
@@ -729,7 +729,7 @@ DSTPORTS = [ 80, 8080 ]
 [...]
 </pre>

-    <h5><a name="nwfelemsRulesProtoVLAN">VLAN (802.1Q)</a>
+    <h5><a id="nwfelemsRulesProtoVLAN">VLAN (802.1Q)</a>
      <span class="since">(Since 0.9.8)</span>
    </h5>
    <p>
@@ -784,7 +784,7 @@ DSTPORTS = [ 80, 8080 ]
      Valid Strings for <code>encap-protocol</code> are: arp, ipv4, ipv6
    </p>

-    <h5><a name="nwfelemsRulesProtoSTP">STP (Spanning Tree Protocol)</a>
+    <h5><a id="nwfelemsRulesProtoSTP">STP (Spanning Tree Protocol)</a>
      <span class="since">(Since 0.9.8)</span>
    </h5>
    <p>
@@ -926,7 +926,7 @@ DSTPORTS = [ 80, 8080 ]
       </tr>
      </table>

-    <h5><a name="nwfelemsRulesProtoARP">ARP/RARP</a></h5>
+    <h5><a id="nwfelemsRulesProtoARP">ARP/RARP</a></h5>
    <p>
      Protocol ID: <code>arp</code> or <code>rarp</code>
      <br/>
@@ -1022,7 +1022,7 @@ DSTPORTS = [ 80, 8080 ]
      <br/><br/>
    </p>

-    <h5><a name="nwfelemsRulesProtoIP">IPv4</a></h5>
+    <h5><a id="nwfelemsRulesProtoIP">IPv4</a></h5>
    <p>
      Protocol ID: <code>ip</code>
      <br/>
@@ -1118,7 +1118,7 @@ DSTPORTS = [ 80, 8080 ]
    </p>


-    <h5><a name="nwfelemsRulesProtoIPv6">IPv6</a></h5>
+    <h5><a id="nwfelemsRulesProtoIPv6">IPv6</a></h5>
    <p>
      Protocol ID: <code>ipv6</code>
      <br/>
@@ -1228,7 +1228,7 @@ DSTPORTS = [ 80, 8080 ]
      <br/><br/>
    </p>

-    <h5><a name="nwfelemsRulesProtoTCP-ipv4">TCP/UDP/SCTP</a></h5>
+    <h5><a id="nwfelemsRulesProtoTCP-ipv4">TCP/UDP/SCTP</a></h5>
    <p>
      Protocol ID: <code>tcp</code>, <code>udp</code>, <code>sctp</code>
      <br/>
@@ -1344,7 +1344,7 @@ DSTPORTS = [ 80, 8080 ]
    </p>


-    <h5><a name="nwfelemsRulesProtoICMP">ICMP</a></h5>
+    <h5><a id="nwfelemsRulesProtoICMP">ICMP</a></h5>
    <p>
      Protocol ID: <code>icmp</code>
      <br/>
@@ -1458,7 +1458,7 @@ DSTPORTS = [ 80, 8080 ]
      <br/><br/>
    </p>

-    <h5><a name="nwfelemsRulesProtoMisc">IGMP, ESP, AH, UDPLITE, 'ALL'</a></h5>
+    <h5><a id="nwfelemsRulesProtoMisc">IGMP, ESP, AH, UDPLITE, 'ALL'</a></h5>
    <p>
      Protocol ID: <code>igmp</code>, <code>esp</code>, <code>ah</code>, <code>udplite</code>, <code>all</code>
      <br/>
@@ -1563,7 +1563,7 @@ DSTPORTS = [ 80, 8080 ]
    </p>


-    <h5><a name="nwfelemsRulesProtoTCP-ipv6">TCP/UDP/SCTP over IPV6</a></h5>
+    <h5><a id="nwfelemsRulesProtoTCP-ipv6">TCP/UDP/SCTP over IPV6</a></h5>
    <p>
      Protocol ID: <code>tcp-ipv6</code>, <code>udp-ipv6</code>, <code>sctp-ipv6</code>
      <br/>
@@ -1679,7 +1679,7 @@ DSTPORTS = [ 80, 8080 ]
    </p>


-    <h5><a name="nwfelemsRulesProtoICMPv6">ICMPv6</a></h5>
+    <h5><a id="nwfelemsRulesProtoICMPv6">ICMPv6</a></h5>
    <p>
      Protocol ID: <code>icmpv6</code>
      <br/>
@@ -1779,7 +1779,7 @@ DSTPORTS = [ 80, 8080 ]
      <br/><br/>
    </p>

-    <h5><a name="nwfelemsRulesProtoMiscv6">ESP, AH, UDPLITE, 'ALL' over IPv6</a></h5>
+    <h5><a id="nwfelemsRulesProtoMiscv6">ESP, AH, UDPLITE, 'ALL' over IPv6</a></h5>
    <p>
      Protocol ID: <code>esp-ipv6</code>, <code>ah-ipv6</code>, <code>udplite-ipv6</code>, <code>all-ipv6</code>
      <br/>
@@ -1868,13 +1868,13 @@ DSTPORTS = [ 80, 8080 ]
      <br/><br/>
    </p>

-    <h3><a name="nwfelemsRulesAdv">Advanced Filter Configuration Topics</a></h3>
+    <h3><a id="nwfelemsRulesAdv">Advanced Filter Configuration Topics</a></h3>
    <p>
     The following sections discuss advanced filter configuration
     topics.
    </p>

-    <h4><a name="nwfelemsRulesAdvTracking">Connection tracking</a></h4>
+    <h4><a id="nwfelemsRulesAdvTracking">Connection tracking</a></h4>
    <p>
     The network filtering subsystem (on Linux) makes use of the connection
     tracking support of iptables. This helps in enforcing the
@@ -1908,7 +1908,7 @@ DSTPORTS = [ 80, 8080 ]
     which may or may not be desirable.
    </p>

-    <h4><a name="nwfelemsRulesAdvLimiting">Limiting Number of Connections</a></h4>
+    <h4><a id="nwfelemsRulesAdvLimiting">Limiting Number of Connections</a></h4>
    <p>
     To limit the number of connections a VM may establish, a rule must
     be provided that sets a limit of connections for a given
@@ -1981,7 +1981,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout
      traffic behavior in relation to idle connections.
    </p>

-    <h2><a name="nwfcli">Command line tools</a></h2>
+    <h2><a id="nwfcli">Command line tools</a></h2>
    <p>
      The libvirt command line tool <code>virsh</code> has been extended
      with life-cycle support for network filters. All commands related
@@ -1996,7 +1996,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout
     <li>nwfilter-edit : edit a network filter given its name</li>
    </ul>

-    <h2><a name="nwfexamples">Pre-existing network filters</a></h2>
+    <h2><a id="nwfexamples">Pre-existing network filters</a></h2>
    <p>
     The following is a list of example network filters that are
     automatically installed with libvirt.</p>
@@ -2051,7 +2051,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout
     on top of the prevention of packet spoofing.
    </p>

-    <h2><a name="nwfwrite">Writing your own filters</a></h2>
+    <h2><a id="nwfwrite">Writing your own filters</a></h2>

    <p>
     Since libvirt only provides a couple of example networking filters, you
@@ -2124,7 +2124,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout
    <code>udp-ipv6</code> traffic filtering node.
    </p>

-    <h3><a name="nwfwriteexample">Example custom filter</a></h3>
+    <h3><a id="nwfwriteexample">Example custom filter</a></h3>
    <p>
     As an example we want to now build a filter that fulfills the following
     list of requirements:
@@ -2227,7 +2227,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout
 &lt;/rule&gt;
 </pre>

-    <h3><a name="nwfwriteexample2nd">Second example custom filter</a></h3>
+    <h3><a id="nwfwriteexample2nd">Second example custom filter</a></h3>
    <p>
     In this example we now want to build a similar filter as in the
     example above, but extend the list of requirements with an
@@ -2400,13 +2400,13 @@ modprobe ip_conntrack_ftp   # if above is not available

 </pre>

-    <h2><a name="nwflimits">Limitations</a></h2>
+    <h2><a id="nwflimits">Limitations</a></h2>
    <p>
     The following sections list (current) limitations of the network
     filtering subsystem.
    </p>

-    <h3><a name="nwflimitsmigr">VM Migration</a></h3>
+    <h3><a id="nwflimitsmigr">VM Migration</a></h3>
     <p>
      VM migration is only supported if the whole filter tree
      that is referenced by a virtual machine's top level filter
@@ -2424,7 +2424,7 @@ modprobe ip_conntrack_ftp   # if above is not available
      0.8.1 or later in order not to lose the network traffic filters
      associated with an interface.
     </p>
-    <h3><a name="nwflimitsvlan">VLAN filtering on Linux</a></h3>
+    <h3><a id="nwflimitsvlan">VLAN filtering on Linux</a></h3>
     <p>
      VLAN (802.1Q) packets, if sent by a virtual machine, cannot be filtered
      with rules for protocol IDs <code>arp</code>, <code>rarp</code>,
--- a/docs/formatsecret.html.in
+++ b/docs/formatsecret.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Secret XML format</h1>

    <ul id="toc"></ul>

-    <h2><a name="SecretAttributes">Secret XML</a></h2>
+    <h2><a id="SecretAttributes">Secret XML</a></h2>

    <p>
      Secrets stored by libvirt may have attributes associated with them, using
@@ -47,7 +47,7 @@
      </dd>
    </dl>

-    <h3><a name="VolumeUsageType">Usage type "volume"</a></h3>
+    <h3><a id="VolumeUsageType">Usage type "volume"</a></h3>

    <p>
      This secret is associated with a volume, whether the format is either
@@ -120,7 +120,7 @@ Secret value set
 #
    </pre>

-    <h3><a name="CephUsageType">Usage type "ceph"</a></h3>
+    <h3><a id="CephUsageType">Usage type "ceph"</a></h3>
    <p>
      This secret is associated with a Ceph RBD (rados block device).
      The <code>&lt;usage type='ceph'&gt;</code> element must contain
@@ -187,7 +187,7 @@ Secret value set
 &lt;/auth&gt;
    </pre>

-    <h3><a name="iSCSIUsageType">Usage type "iscsi"</a></h3>
+    <h3><a id="iSCSIUsageType">Usage type "iscsi"</a></h3>

    <p>
      This secret is associated with an iSCSI target for CHAP authentication.
@@ -272,7 +272,7 @@ Secret value set
 &lt;/auth&gt;
    </pre>

-    <h3><a name="tlsUsageType">Usage type "tls"</a></h3>
+    <h3><a id="tlsUsageType">Usage type "tls"</a></h3>

    <p>
      This secret may be used in order to provide the passphrase for the
--- a/docs/formatsnapshot.html.in
+++ b/docs/formatsnapshot.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Snapshot XML format</h1>

    <ul id="toc"></ul>

-    <h2><a name="SnapshotAttributes">Snapshot XML</a></h2>
+    <h2><a id="SnapshotAttributes">Snapshot XML</a></h2>

    <p>
      There are several types of snapshots:
@@ -243,7 +243,7 @@
      </dd>
    </dl>

-    <h2><a name="example">Examples</a></h2>
+    <h2><a id="example">Examples</a></h2>

    <p>Using this XML to create a disk snapshot of just vda on a qemu
      domain with two disks:</p>
--- a/docs/formatstorage.html.in
+++ b/docs/formatstorage.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Storage pool and volume XML format</h1>

    <ul id="toc"></ul>

-    <h2><a name="StoragePool">Storage pool XML</a></h2>
+    <h2><a id="StoragePool">Storage pool XML</a></h2>

    <p>
      Although all storage pool backends share the same public APIs and
@@ -29,7 +29,7 @@
      3.1.0</span>). This corresponds to the
      storage backend drivers listed further along in this document.
    </p>
-    <h3><a name="StoragePoolFirst">General metadata</a></h3>
+    <h3><a id="StoragePoolFirst">General metadata</a></h3>

    <pre>
 &lt;pool type="iscsi"&gt;
@@ -66,7 +66,7 @@
        pool. <span class="since">Since 0.4.1</span></dd>
    </dl>

-    <h3><a name="StoragePoolSource">Source elements</a></h3>
+    <h3><a id="StoragePoolSource">Source elements</a></h3>

    <p>
      A single <code>source</code> element is contained within the top level
@@ -397,7 +397,7 @@
        is backend specific.  <span class="since">Since 0.8.4</span></dd>
    </dl>

-    <h3><a name="StoragePoolTarget">Target elements</a></h3>
+    <h3><a id="StoragePoolTarget">Target elements</a></h3>

    <p>
      A single <code>target</code> element is contained within the top level
@@ -461,7 +461,7 @@
      </dd>
    </dl>

-    <h3><a name="StoragePoolExtents">Device extents</a></h3>
+    <h3><a id="StoragePoolExtents">Device extents</a></h3>

    <p>
      If a storage pool exposes information about its underlying
@@ -481,7 +481,7 @@
      device, measured in bytes.  <span class="since">Since 0.4.1</span>
    </p>

-    <h2><a name="StorageVol">Storage volume XML</a></h2>
+    <h2><a id="StorageVol">Storage volume XML</a></h2>
    <p>
      A storage volume will generally be either a file or a device
      node; <span class="since">since 1.2.0</span>, an optional
@@ -491,7 +491,7 @@
      XML format is available <span class="since">since 0.4.1</span>
    </p>

-    <h3><a name="StorageVolFirst">General metadata</a></h3>
+    <h3><a id="StorageVolFirst">General metadata</a></h3>

    <pre>
 &lt;volume type='file'&gt;
@@ -570,7 +570,7 @@
        on the local host. <span class="since">Since 0.4.1</span></dd>
    </dl>

-    <h3><a name="StorageVolTarget">Target elements</a></h3>
+    <h3><a id="StorageVolTarget">Target elements</a></h3>

    <p>
      A single <code>target</code> element is contained within the top level
@@ -686,7 +686,7 @@
      </dd>
    </dl>

-    <h3><a name="StorageVolBacking">Backing store elements</a></h3>
+    <h3><a id="StorageVolBacking">Backing store elements</a></h3>

    <p>
      A single <code>backingStore</code> element is contained within the top level
@@ -732,14 +732,14 @@
      </dd>
    </dl>

-    <h2><a name="examples">Example configuration</a></h2>
+    <h2><a id="examples">Example configuration</a></h2>

    <p>
      Here are a couple of examples, for a more complete set demonstrating
      every type of storage pool, consult the <a href="storage.html">storage driver page</a>
    </p>

-    <h3><a name="exampleFile">File based storage pool</a></h3>
+    <h3><a id="exampleFile">File based storage pool</a></h3>

    <pre>
 &lt;pool type="dir"&gt;
@@ -749,7 +749,7 @@
  &lt;/target&gt;
 &lt;/pool&gt;</pre>

-    <h3><a name="exampleISCSI">iSCSI based storage pool</a></h3>
+    <h3><a id="exampleISCSI">iSCSI based storage pool</a></h3>

    <pre>
 &lt;pool type="iscsi"&gt;
@@ -766,7 +766,7 @@
  &lt;/target&gt;
 &lt;/pool&gt;</pre>

-    <h3><a name="exampleVol">Storage volume</a></h3>
+    <h3><a id="exampleVol">Storage volume</a></h3>

    <pre>
 &lt;volume&gt;
@@ -784,7 +784,7 @@
  &lt;/target&gt;
 &lt;/volume&gt;</pre>

-    <h3><a name="exampleLuks">Storage volume using LUKS</a></h3>
+    <h3><a id="exampleLuks">Storage volume using LUKS</a></h3>

    <pre>
 &lt;volume&gt;
--- a/docs/formatstorageencryption.html.in
+++ b/docs/formatstorageencryption.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Storage volume encryption XML format</h1>

    <ul id="toc"></ul>

-    <h2><a name="StorageEncryption">Storage volume encryption XML</a></h2>
+    <h2><a id="StorageEncryption">Storage volume encryption XML</a></h2>

    <p>
      Storage volumes may be encrypted, the XML snippet described below is used
@@ -37,7 +37,7 @@
      secret value at the time of volume creation, and store it using the
      specified <code>uuid</code>.
    </p>
-    <h3><a name="StorageEncryptionDefault">"default" format</a></h3>
+    <h3><a id="StorageEncryptionDefault">"default" format</a></h3>
    <p>
      <code>&lt;encryption format="default"/&gt;</code> can be specified only
      when creating a qcow volume.  If the volume is successfully created, the
@@ -47,7 +47,7 @@
      in later operations with the volume, or when setting up a domain that
      uses the volume.
    </p>
-    <h3><a name="StorageEncryptionQcow">"qcow" format</a></h3>
+    <h3><a id="StorageEncryptionQcow">"qcow" format</a></h3>
    <p>
      The <code>qcow</code> format specifies that the built-in encryption
      support in <code>qcow</code>- or <code>qcow2</code>-formatted volume
@@ -56,7 +56,7 @@
      the <code>secret</code> element is not present during volume creation,
      a secret is automatically generated and attached to the volume.
    </p>
-    <h3><a name="StorageEncryptionLuks">"luks" format</a></h3>
+    <h3><a id="StorageEncryptionLuks">"luks" format</a></h3>
    <p>
      The <code>luks</code> format is specific to a luks encrypted volume
      and the secret is used in order to either encrypt during volume creation
@@ -119,7 +119,7 @@
    </dl>


-    <h2><a name="example">Examples</a></h2>
+    <h2><a id="example">Examples</a></h2>

    <p>
      Here is a simple example, specifying use of the <code>qcow</code> format:
--- a/docs/genaclperms.pl
+++ b/docs/genaclperms.pl
@@ -74,7 +74,7 @@ while (<>) {

 print <<EOF;
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
 EOF
--- a/docs/goals.html.in
+++ b/docs/goals.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Terminology and goals</h1>
--- a/docs/governance.html.in
+++ b/docs/governance.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Project governance</h1>
@@ -14,7 +14,7 @@
      influence, within the community.
    </p>

-    <h2><a name="codeofconduct">Code of conduct</a></h2>
+    <h2><a id="codeofconduct">Code of conduct</a></h2>

    <p>
      The libvirt project community covers people from a wide variety of
@@ -49,7 +49,7 @@
        from them. Playing a blame game doesn't help anyone.</li>
    </ul>

-    <h2><a name="roles">Roles and responsibilities</a></h2>
+    <h2><a id="roles">Roles and responsibilities</a></h2>

    <h3><a href="users">Users</a></h3>

@@ -91,7 +91,7 @@
      ways listed in the next section.
    </p>

-    <h3><a name="contributors">Contributors</a></h3>
+    <h3><a id="contributors">Contributors</a></h3>

    <p>
      The contributors are community members who have some concrete impact
@@ -156,7 +156,7 @@
      covered are found in the source repositories, or website in question.
    </p>

-    <h3><a name="committers">Committers</a></h3>
+    <h3><a id="committers">Committers</a></h3>

    <p>
      The committers are the subset of contributors who have direct access
@@ -227,7 +227,7 @@
      to retain their role as a committer.
    </p>

-    <h3><a name="secteam">Security team</a></h3>
+    <h3><a id="secteam">Security team</a></h3>

    <p>
      The security team consists of a subset of the project committers
@@ -252,7 +252,7 @@
      before disclosing a private issue.
    </p>

-    <h2><a name="roughconsensus">Rough consensus</a></h2>
+    <h2><a id="roughconsensus">Rough consensus</a></h2>

    <p>
      A core concept for governance of the project described above is
--- a/docs/hacking.html.in
+++ b/docs/hacking.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Contributor guidelines</h1>

    <ul id="toc"></ul>

-    <h2><a name="patches">General tips for contributing patches</a></h2>
+    <h2><a id="patches">General tips for contributing patches</a></h2>
    <ol>
      <li>
        <p>Discuss any large changes on the mailing list first.  Post patches
@@ -336,7 +336,7 @@
        Richard Jones' guide to working with open source projects</a>.
    </p>

-    <h2><a name="tooling">Tooling</a></h2>
+    <h2><a id="tooling">Tooling</a></h2>

    <p>
      libvirt includes support for some useful development tools right in its
@@ -356,7 +356,7 @@
      </li>
    </ul>

-    <h2><a name="naming">Naming conventions</a></h2>
+    <h2><a id="naming">Naming conventions</a></h2>

    <p>
      When reading libvirt code, a number of different naming conventions will
@@ -450,7 +450,7 @@
      </dd>
    </dl>

-    <h2><a name="indent">Code indentation</a></h2>
+    <h2><a id="indent">Code indentation</a></h2>
    <p>
      Libvirt's C source code generally adheres to some basic code-formatting
      conventions.  The existing code base is not totally consistent on this
@@ -487,7 +487,7 @@
      which will load the .lvimrc only when you edit libvirt code.
    </p>

-    <h2><a name="formatting">Code formatting (especially for new code)</a></h2>
+    <h2><a id="formatting">Code formatting (especially for new code)</a></h2>

    <p>
      With new code, we can be even more strict.
@@ -523,7 +523,7 @@
    </p>


-    <h2><a name="bracket_spacing">Bracket spacing</a></h2>
+    <h2><a id="bracket_spacing">Bracket spacing</a></h2>

    <p>
      The keywords <code>if</code>, <code>for</code>, <code>while</code>,
@@ -572,7 +572,7 @@
      int foo(int wizz);    // Good
 </pre>

-    <h2><a name="comma">Commas</a></h2>
+    <h2><a id="comma">Commas</a></h2>

    <p>
      Commas should always be followed by a space or end of line, and
@@ -609,7 +609,7 @@
      };
 </pre>

-    <h2><a name="semicolon">Semicolons</a></h2>
+    <h2><a id="semicolon">Semicolons</a></h2>

    <p>
      Semicolons should never have a space beforehand.  Inside the
@@ -638,7 +638,7 @@
      }
 </pre>

-    <h2><a name="curly_braces">Curly braces</a></h2>
+    <h2><a id="curly_braces">Curly braces</a></h2>

    <p>
      Omit the curly braces around an <code>if</code>, <code>while</code>,
@@ -819,7 +819,7 @@
  }
 </pre>

-    <h2><a name="preprocessor">Preprocessor</a></h2>
+    <h2><a id="preprocessor">Preprocessor</a></h2>

    <p>Macros defined with an ALL_CAPS name should generally be
      assumed to be unsafe with regards to arguments with side-effects
@@ -844,7 +844,7 @@
  #endif
 </pre>

-    <h2><a name="types">C types</a></h2>
+    <h2><a id="types">C types</a></h2>

    <p>
      Use the right type.
@@ -919,7 +919,7 @@
      it points to, or it is aliased to another pointer that is.
    </p>

-    <h2><a name="memalloc">Low level memory management</a></h2>
+    <h2><a id="memalloc">Low level memory management</a></h2>

    <p>
      Use of the malloc/free/realloc/calloc APIs is deprecated in the libvirt
@@ -1013,7 +1013,7 @@
      </li>
    </ul>

-    <h2><a name="file_handling">File handling</a></h2>
+    <h2><a id="file_handling">File handling</a></h2>

    <p>
      Usage of the <code>fdopen()</code>, <code>close()</code>, <code>fclose()</code>
@@ -1059,7 +1059,7 @@
      </li>
    </ul>

-    <h2><a name="string_comparision">String comparisons</a></h2>
+    <h2><a id="string_comparision">String comparisons</a></h2>

    <p>
      Do not use the strcmp, strncmp, etc functions directly. Instead use
@@ -1109,7 +1109,7 @@
    </ul>


-    <h2><a name="string_copying">String copying</a></h2>
+    <h2><a id="string_copying">String copying</a></h2>

    <p>
      Do not use the strncpy function.  According to the man page, it
@@ -1169,7 +1169,7 @@
      and usually considered a flaw.
    </p>

-    <h2><a name="strbuf">Variable length string buffer</a></h2>
+    <h2><a id="strbuf">Variable length string buffer</a></h2>

    <p>
      If there is a need for complex string concatenations, avoid using
@@ -1202,7 +1202,7 @@
 </pre>


-    <h2><a name="includes">Include files</a></h2>
+    <h2><a id="includes">Include files</a></h2>

    <p>
      There are now quite a large number of include files, both libvirt
@@ -1251,7 +1251,7 @@
    </p>


-    <h2><a name="printf">Printf-style functions</a></h2>
+    <h2><a id="printf">Printf-style functions</a></h2>

    <p>
      Whenever you add a new printf-style function, i.e., one with a format
@@ -1280,7 +1280,7 @@
      does for snprintf.
    </p>

-    <h2><a name="goto">Use of goto</a></h2>
+    <h2><a id="goto">Use of goto</a></h2>

    <p>
      The use of goto is not forbidden, and goto is widely used
@@ -1363,7 +1363,7 @@ int foo()



-    <h2><a name="committers">Libvirt committer guidelines</a></h2>
+    <h2><a id="committers">Libvirt committer guidelines</a></h2>

    <p>
      The AUTHORS files indicates the list of people with commit access right
--- a/docs/hooks.html.in
+++ b/docs/hooks.html.in
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Hooks for specific system management</h1>

    <ul id="toc"></ul>

-    <h2><a name="intro">Custom event scripts</a></h2>
+    <h2><a id="intro">Custom event scripts</a></h2>
    <p>Beginning with libvirt 0.8.0, specific events on a host system will
       trigger custom scripts.</p>
    <p>These custom <b>hook</b> scripts are executed when any of the following
@@ -26,7 +26,7 @@
          (<span class="since">since 1.2.2</span>)<br/><br/></li>
    </ul>

-    <h2><a name="location">Script location</a></h2>
+    <h2><a id="location">Script location</a></h2>
    <p>The libvirt hook scripts are located in the directory
       <code>$SYSCONFDIR/libvirt/hooks/</code>.</p>
    <ul>
@@ -42,7 +42,7 @@
       them executable.</p>
    <br/>

-    <h2><a name="names">Script names</a></h2>
+    <h2><a id="names">Script names</a></h2>
    <p>At present, there are five hook scripts that can be called:</p>
    <ul>
      <li><code>/etc/libvirt/hooks/daemon</code><br/><br/>
@@ -61,7 +61,7 @@
    </ul>
    <br/>

-    <h2><a name="structure">Script structure</a></h2>
+    <h2><a id="structure">Script structure</a></h2>
    <p>The hook scripts are executed using standard Linux process creation
       functions.  Therefore, they must begin with the declaration of the
       command interpreter to use.</p>
@@ -73,7 +73,7 @@
       binary, so you are welcome to use your favourite languages.</p>
    <br/>

-    <h2><a name="arguments">Script arguments</a></h2>
+    <h2><a id="arguments">Script arguments</a></h2>
    <p>The hook scripts are called with specific command line arguments,
       depending upon the script, and the operation being performed.</p>
    <p>The guest hook scripts, qemu and lxc, are also given the <b>full</b>
@@ -128,10 +128,10 @@
          none.</li>
    </ol>

-    <h4><a name="arguments_specifics">Specifics</a></h4>
+    <h4><a id="arguments_specifics">Specifics</a></h4>
    <p>This translates to the following specifics for each hook script:</p>

-    <h5><a name="daemon">/etc/libvirt/hooks/daemon</a></h5>
+    <h5><a id="daemon">/etc/libvirt/hooks/daemon</a></h5>
    <ul>
      <li>When the libvirt daemon is started, this script is called as:<br/>
          <pre>/etc/libvirt/hooks/daemon - start - start</pre></li>
@@ -146,7 +146,7 @@
       with the "start" operation.  There is no specific operation to indicate
       a "restart" is occurring.</p>

-    <h5><a name="qemu">/etc/libvirt/hooks/qemu</a></h5>
+    <h5><a id="qemu">/etc/libvirt/hooks/qemu</a></h5>
    <ul>
      <li>Before a QEMU guest is started, the qemu hook script is
        called in three locations; if any location fails, the guest
@@ -206,7 +206,7 @@
      </li>
    </ul>

-    <h5><a name="lxc">/etc/libvirt/hooks/lxc</a></h5>
+    <h5><a id="lxc">/etc/libvirt/hooks/lxc</a></h5>
    <ul>
      <li>Before a LXC guest is started, the lxc hook script is
        called in three locations; if any location fails, the guest
@@ -240,7 +240,7 @@
      </li>
    </ul>

-    <h5><a name="libxl">/etc/libvirt/hooks/libxl</a></h5>
+    <h5><a id="libxl">/etc/libvirt/hooks/libxl</a></h5>
    <ul>
      <li>Before a Xen guest is started using libxl driver, the libxl hook
        script is called in three locations; if any location fails, the guest
@@ -284,12 +284,12 @@
      </li>
    </ul>

-    <h5><a name="network">/etc/libvirt/hooks/network</a></h5>
+    <h5><a id="network">/etc/libvirt/hooks/network</a></h5>
    <ul>
      <li><span class="since">Since 1.2.2</span>, before a network is started,
        this script is called as:<br/>
          <pre>/etc/libvirt/hooks/network network_name start begin -</pre></li>
-      <li>After the network is started, up &and; running, the script is
+      <li>After the network is started, up &amp; running, the script is
        called as:<br/>
          <pre>/etc/libvirt/hooks/network network_name started begin -</pre></li>
      <li>When a network is shut down, this script is called as:<br/>
@@ -310,7 +310,7 @@

    <br/>

-    <h2><a name="execution">Script execution</a></h2>
+    <h2><a id="execution">Script execution</a></h2>
    <ul>
      <li>The "start" operation for the guest and network hook scripts,
          executes <b>prior</b> to the object (guest or network) being created.
@@ -335,7 +335,7 @@
    </ul>
    <br/>

-    <h2><a name="qemu_migration">QEMU guest migration</a></h2>
+    <h2><a id="qemu_migration">QEMU guest migration</a></h2>
    <p>Migration of a QEMU guest involves running hook scripts on both the
       source and destination hosts:</p>
    <ol>
@@ -357,14 +357,14 @@
    </ol>
    <br/>

-    <h2><a name="recursive">Calling libvirt functions from within a hook script</a></h2>
+    <h2><a id="recursive">Calling libvirt functions from within a hook script</a></h2>
    <p><b>DO NOT DO THIS!</b></p>
    <p>A hook script must not call back into libvirt, as the libvirt daemon
       is already waiting for the script to exit.</p>
    <p>A deadlock is likely to occur.</p>
    <br/>

-    <h2><a name="return_codes">Return codes and logging</a></h2>
+    <h2><a id="return_codes">Return codes and logging</a></h2>
    <p>If a hook script returns with an exit code of 0, the libvirt daemon
       regards this as successful and performs no logging of it.</p>
    <p>However, if a hook script returns with a non zero exit code, the libvirt
--- a/docs/hvsupport.pl
+++ b/docs/hvsupport.pl
@@ -332,7 +332,7 @@ foreach my $drv (keys %{$groups{"virHypervisorDriver"}->{drivers}}) {

 print <<EOF;
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
 <body class="hvsupport">
 <h1>libvirt API support matrix</h1>
--- a/docs/index.html.in
+++ b/docs/index.html.in
@@ -1,10 +1,10 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
-    <script type="text/javascript" src="js/jquery-3.1.1.min.js"></script>
-    <script type="text/javascript" src="js/moment.min.js"></script>
-    <script type="text/javascript" src="js/jquery.rss.min.js"></script>
+    <script type="text/javascript" src="js/jquery-3.1.1.min.js"> </script>
+    <script type="text/javascript" src="js/moment.min.js"> </script>
+    <script type="text/javascript" src="js/jquery.rss.min.js"> </script>

    <script type="text/javascript">
      <!--
@@ -59,16 +59,16 @@

        <dt><a href="format.html">XML configuration</a></dt>
        <dd>Description of the XML schemas for
-          <a href="formatdomain.html" shape="rect">domains</a>,
-          <a href="formatnetwork.html" shape="rect">networks</a>,
-          <a href="formatnwfilter.html" shape="rect">network filtering</a>,
-          <a href="formatstorage.html" shape="rect">storage</a>,
-          <a href="formatstorageencryption.html" shape="rect">storage encryption</a>,
-          <a href="formatcaps.html" shape="rect">capabilities</a>,
-          <a href="formatdomaincaps.html" shape="rect">domain capabilities</a>,
-          <a href="formatnode.html" shape="rect">node devices</a>,
-          <a href="formatsecret.html" shape="rect">secrets</a>,
-          <a href="formatsnapshot.html" shape="rect">snapshots</a></dd>
+          <a href="formatdomain.html">domains</a>,
+          <a href="formatnetwork.html">networks</a>,
+          <a href="formatnwfilter.html">network filtering</a>,
+          <a href="formatstorage.html">storage</a>,
+          <a href="formatstorageencryption.html">storage encryption</a>,
+          <a href="formatcaps.html">capabilities</a>,
+          <a href="formatdomaincaps.html">domain capabilities</a>,
+          <a href="formatnode.html">node devices</a>,
+          <a href="formatsecret.html">secrets</a>,
+          <a href="formatsnapshot.html">snapshots</a></dd>
        <dt><a href="http://wiki.libvirt.org">Wiki</a></dt>
        <dd>Read further community contributed content</dd>
      </dl>
--- a/docs/internals.html.in
+++ b/docs/internals.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>libvirt internals</h1>
--- a/docs/internals/command.html.in
+++ b/docs/internals/command.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Spawning processes / commands from libvirt drivers</h1>
@@ -12,7 +12,7 @@
      All code is required to use these APIs
    </p>

-    <h2><a name="posix">Problems with standard POSIX APIs</a></h2>
+    <h2><a id="posix">Problems with standard POSIX APIs</a></h2>

    <p>
      The POSIX specification includes a number of APIs for
@@ -62,7 +62,7 @@
      error prone, particularly wrt memory leak / OOM handling.
    </p>

-    <h2><a name="api">The libvirt command execution API</a></h2>
+    <h2><a id="api">The libvirt command execution API</a></h2>

    <p>
      There is now a high level API that provides a safe and
@@ -72,7 +72,7 @@
      header which can be imported using <code>#include "vircommand.h"</code>
    </p>

-    <h3><a name="initial">Defining commands in libvirt</a></h3>
+    <h3><a id="initial">Defining commands in libvirt</a></h3>

    <p>
      The first step is to declare what command is to be
@@ -92,7 +92,7 @@ virCommandPtr cmd = virCommandNew("/usr/bin/dnsmasq");
      reported at a later time.
    </p>

-    <h3><a name="args">Adding arguments to the command</a></h3>
+    <h3><a id="args">Adding arguments to the command</a></h3>

    <p>
      There are a number of APIs for adding arguments to a
@@ -150,7 +150,7 @@ virCommandPtr cmd2 = virCommandNewArgList("/usr/bin/dnsmasq",
                                          "--domain", "localdomain", NULL);
 </pre>

-    <h3><a name="env">Setting up the environment</a></h3>
+    <h3><a id="env">Setting up the environment</a></h3>

    <p>
      By default a command will inherit all environment variables
@@ -199,7 +199,7 @@ virCommandAddEnvPair(cmd, "TERM", "xterm");
 virCommandAddEnvString(cmd, "TERM=xterm");
 </pre>

-    <h3><a name="misc">Miscellaneous other options</a></h3>
+    <h3><a id="misc">Miscellaneous other options</a></h3>

    <p>
      Normally the spawned command will retain the current
@@ -229,7 +229,7 @@ virCommandSetPidFile(cmd, "/var/run/dnsmasq.pid");
      the intermediate process exits.
    </p>

-    <h3><a name="privs">Reducing command privileges</a></h3>
+    <h3><a id="privs">Reducing command privileges</a></h3>

    <p>
      Normally a command will inherit all privileges of
@@ -243,7 +243,7 @@ virCommandSetPidFile(cmd, "/var/run/dnsmasq.pid");
 virCommandClearCaps(cmd);
 </pre>

-    <h3><a name="fds">Managing file handles</a></h3>
+    <h3><a id="fds">Managing file handles</a></h3>

    <p>
      To prevent unintended resource leaks to child processes, the
@@ -329,7 +329,7 @@ virCommandSetErrorFD(cmd, &amp;errfd);
 virCommandNonblockingFDs(cmd);
 </pre>

-    <h3><a name="buffers">Feeding &amp; capturing strings to/from the child</a></h3>
+    <h3><a id="buffers">Feeding &amp; capturing strings to/from the child</a></h3>

    <p>
      Often dealing with file handles for stdin/out/err is
@@ -382,7 +382,7 @@ virCommandSetErrorBuffer(cmd, &amp;errors);
      case the child process interleaves output into a single string.
    </p>

-    <h3><a name="directory">Setting working directory</a></h3>
+    <h3><a id="directory">Setting working directory</a></h3>

    <p>
      Daemonized commands are always run with "/" as the current
@@ -395,7 +395,7 @@ virCommandSetErrorBuffer(cmd, &amp;errors);
 virCommandSetWorkingDirectory(cmd, LOCALSTATEDIR);
 </pre>

-    <h3><a name="hooks">Any additional hooks</a></h3>
+    <h3><a id="hooks">Any additional hooks</a></h3>

    <p>
      If anything else is needed, it is possible to request a hook
@@ -409,7 +409,7 @@ virCommandSetWorkingDirectory(cmd, LOCALSTATEDIR);
 virCommandSetPreExecHook(cmd, hook, opaque);
 </pre>

-    <h3><a name="logging">Logging commands</a></h3>
+    <h3><a id="logging">Logging commands</a></h3>

    <p>
      Sometimes, it is desirable to log what command will be run, or
@@ -434,7 +434,7 @@ if (virCommandRun(cmd, NULL) &lt; 0)
    return -1;
 </pre>

-    <h3><a name="sync">Running commands synchronously</a></h3>
+    <h3><a id="sync">Running commands synchronously</a></h3>

    <p>
      For most commands, the desired behaviour is to spawn
@@ -480,7 +480,7 @@ if (WIFEXITED(status) &amp;&amp; WEXITSTATUS(status) == 1) {
 }
 </pre>

-    <h3><a name="async">Running commands asynchronously</a></h3>
+    <h3><a id="async">Running commands asynchronously</a></h3>

    <p>
      In certain complex scenarios, particularly special
@@ -530,7 +530,7 @@ if (WEXITSTATUS(status)...) {
      virCommandAbort to reap the process.
    </p>

-    <h3><a name="release">Releasing resources</a></h3>
+    <h3><a id="release">Releasing resources</a></h3>

    <p>
      Once the command has been executed, or if execution
@@ -550,7 +550,7 @@ virCommandFree(cmd);
      it will be forcibly killed and cleaned up (via waitpid).
    </p>

-    <h2><a name="example">Complete examples</a></h2>
+    <h2><a id="example">Complete examples</a></h2>

    <p>
      This shows a complete example usage of the APIs roughly
--- a/docs/internals/eventloop.html.in
+++ b/docs/internals/eventloop.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Libvirt's event loop</h1>
@@ -11,7 +11,7 @@
      libvirt. Both server and client.
    </p>

-    <h2><a name="event_loop">Event driven programming</a></h2>
+    <h2><a id="event_loop">Event driven programming</a></h2>

    <p>Traditionally, a program simply ran once, then terminated.
    This type of program was very common in the early days of
@@ -38,7 +38,7 @@
    file descriptor which is then watched for incoming events,
    e.g. messages. </p>

-    <h2><a name="api">The event loop API</a></h2>
+    <h2><a id="api">The event loop API</a></h2>

    <p>To work with event loop from our code we have plenty of
    APIs.</p>
@@ -62,7 +62,7 @@
    <p>For more information on these APIs continue reading <a
    href="../html/libvirt-libvirt-event.html">here</a>.</p>

-    <h2><a name="worker_pool">Worker pool</a></h2>
+    <h2><a id="worker_pool">Worker pool</a></h2>

    <p>Looking back at the image above we can see one big
    limitation. While processing a message event loop is blocked
--- a/docs/internals/locking.html.in
+++ b/docs/internals/locking.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Resource Lock Manager</h1>
@@ -12,7 +12,7 @@
      access to content.
    </p>

-    <h2><a name="goals">Goals</a></h2>
+    <h2><a id="goals">Goals</a></h2>

    <p>
      The high level goal is to prevent the same disk image being
@@ -36,7 +36,7 @@
      </li>
    </ol>

-    <h2><a name="requirement">Requirements</a></h2>
+    <h2><a id="requirement">Requirements</a></h2>

    <p>
      The high level goal leads to a set of requirements
@@ -67,7 +67,7 @@
      </li>
    </ol>

-    <h2><a name="design">Design</a></h2>
+    <h2><a id="design">Design</a></h2>

    <p>
      Within a lock manager the following series of operations
@@ -102,7 +102,7 @@
      </li>
    </ul>

-    <h2><a name="impl">Plugin Implementations</a></h2>
+    <h2><a id="impl">Plugin Implementations</a></h2>

    <p>
      Lock manager implementations are provided as LGPLv2+
@@ -132,7 +132,7 @@
      in the previously mentioned header file
    </p>

-    <h2><a name="qemuIntegrate">QEMU Driver integration</a></h2>
+    <h2><a id="qemuIntegrate">QEMU Driver integration</a></h2>

    <p>
      With the QEMU driver, the lock plugin will be set
@@ -149,7 +149,7 @@ lockManager="sanlock"
      for backwards compatibility
    </p>

-    <h2><a name="usagePatterns">Lock usage patterns</a></h2>
+    <h2><a id="usagePatterns">Lock usage patterns</a></h2>

    <p>
      The following pseudo code illustrates the common
@@ -157,7 +157,7 @@ lockManager="sanlock"
      manager plugin callbacks.
    </p>

-    <h3><a name="usageLockAcquire">Lock acquisition</a></h3>
+    <h3><a id="usageLockAcquire">Lock acquisition</a></h3>

    <p>
      Initial lock acquisition will be performed from the
@@ -205,7 +205,7 @@ if (virLockManagerAcquire(lock, NULL, 0) &lt; 0);
  ...abort...
    </pre>

-    <h3><a name="usageLockAttach">Lock release</a></h3>
+    <h3><a id="usageLockAttach">Lock release</a></h3>

    <p>
      The locks are all implicitly released when the process
--- a/docs/internals/oomtesting.html.in
+++ b/docs/internals/oomtesting.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Out of memory testing</h1>
@@ -26,7 +26,7 @@ $ ./configure --enable-test-oom
 </pre>


-    <h2><a name="basicoom">Basic OOM testing support</a></h2>
+    <h2><a id="basicoom">Basic OOM testing support</a></h2>

    <p>
      The first step in validating OOM usage is to run a test suite
@@ -64,7 +64,7 @@ $ VIR_TEST_OOM=1 ./qemuxml2argvtest
      of memory allocations from that test case.
    </p>

-    <h3><a name="valgrind">Tracking failures with valgrind</a></h3>
+    <h3><a id="valgrind">Tracking failures with valgrind</a></h3>

    <p>
      The test suite should obviously *not* crash during OOM testing.
@@ -88,7 +88,7 @@ $ VIR_TEST_OOM=1 VIR_TEST_RANGE=5 ../run valgrind ./qemuxml2argvtest
      access.
    </p>

-    <h3><a name="stacktraces">Tracking failures with stack traces</a></h3>
+    <h3><a id="stacktraces">Tracking failures with stack traces</a></h3>

    <p>
      With some really difficult bugs valgrind is not sufficient to
@@ -191,7 +191,7 @@ _start
 ??:?
    </pre>

-    <h3><a name="noncrash">Non-crash related problems</a></h3>
+    <h3><a id="noncrash">Non-crash related problems</a></h3>

    <p>
      Not all memory allocation bugs result in code crashing. Sometimes
--- a/docs/internals/rpc.html.in
+++ b/docs/internals/rpc.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>libvirt RPC infrastructure</h1>
@@ -17,7 +17,7 @@
    </p>


-    <h2><a name="protocol">RPC protocol</a></h2>
+    <h2><a id="protocol">RPC protocol</a></h2>

    <p>
      libvirt uses a simple, variable length, packet based RPC protocol.
@@ -193,14 +193,14 @@
      definition for the program+version in question
    </p>

-    <h3><a name="wireexamples">Wire examples</a></h3>
+    <h3><a id="wireexamples">Wire examples</a></h3>

    <p>
      The following diagrams illustrate some example packet exchanges
      between a client and server
    </p>

-    <h4><a name="wireexamplescall">Method call</a></h4>
+    <h4><a id="wireexamplescall">Method call</a></h4>

    <p>
      A single method call and successful
@@ -219,7 +219,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
       +--+-----------------------+--------+
    </pre>

-    <h4><a name="wireexamplescallerr">Method call with error</a></h4>
+    <h4><a id="wireexamplescallerr">Method call with error</a></h4>

    <p>
      An unsuccessful method call will instead return an error object
@@ -235,7 +235,7 @@ C &lt;--  |48| 8 | 1 | 3 | 2 | 1 | 0 | .o.oOo.o.oOo.o.oOo.o.oOo |  &lt;-- S  (er
       +--+-----------------------+--------------------------+
    </pre>

-    <h4><a name="wireexamplescallup">Method call with upload stream</a></h4>
+    <h4><a id="wireexamplescallup">Method call with upload stream</a></h4>

    <p>
      A method call which also involves uploading some data over
@@ -272,7 +272,7 @@ C &lt;--  |24| 8 | 1 | 3 | 3 | 1 | 0 | &lt;-- S  (stream finish)
       +--+-----------------------+
    </pre>

-    <h4><a name="wireexamplescallbi">Method call bidirectional stream</a></h4>
+    <h4><a id="wireexamplescallbi">Method call bidirectional stream</a></h4>

    <p>
      A method call which also involves a bi-directional stream will
@@ -328,7 +328,7 @@ C &lt;--  |24| 8 | 1 | 3 | 3 | 1 | 0 | &lt;-- S  (stream finish)
    </pre>


-    <h4><a name="wireexamplescallmany">Method calls overlapping</a></h4>
+    <h4><a id="wireexamplescallmany">Method calls overlapping</a></h4>
    <pre>
       +--+-----------------------+-----------+
 C --&gt;  |38| 8 | 1 | 3 | 0 | 1 | 0 | .o.oOo.o. |  --&gt; S  (call 1)
@@ -356,7 +356,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 4 | 0 | .o.oOo |  &lt;-- S  (reply 4)
       +--+-----------------------+--------+
    </pre>

-    <h4><a name="wireexamplescallfd">Method call with passed FD</a></h4>
+    <h4><a id="wireexamplescallfd">Method call with passed FD</a></h4>

    <p>
      A single method call with 2 passed file descriptors and successful
@@ -378,14 +378,14 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
    </pre>


-    <h2><a name="security">RPC security</a></h2>
+    <h2><a id="security">RPC security</a></h2>

    <p>
      There are various things to consider to ensure an implementation
      of the RPC protocol can be satisfactorily secured
    </p>

-    <h3><a name="securitytls">Authentication/encryption</a></h3>
+    <h3><a id="securitytls">Authentication/encryption</a></h3>

    <p>
      The basic RPC protocol does not define or require any specific
@@ -399,7 +399,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      stream can of course be tunnelled over transports such as SSH.
    </p>

-    <h3><a name="securitylimits">Data limits</a></h3>
+    <h3><a id="securitylimits">Data limits</a></h3>

    <p>
      Although the protocol itself defines many arbitrary sized data values in the
@@ -411,7 +411,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      breaking compatibility of the RPC data on the wire.
    </p>

-    <h3><a name="securityvalidate">Data validation</a></h3>
+    <h3><a id="securityvalidate">Data validation</a></h3>

    <p>
      It is important that all data be fully validated before performing
@@ -427,7 +427,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      execution API (e.g. corresponding libvirt public API).
    </p>

-    <h2><a name="internals">RPC internal APIs</a></h2>
+    <h2><a id="internals">RPC internal APIs</a></h2>

    <p>
      The generic internal RPC library code lives in the <code>src/rpc/</code>
@@ -436,7 +436,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      purposes are:
    </p>

-    <h3><a name="apioverview">Overview of RPC objects</a></h3>
+    <h3><a id="apioverview">Overview of RPC objects</a></h3>

    <p>
      The following is a high level overview of the role of each
@@ -568,7 +568,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      </dd>
    </dl>

-    <h3><a name="apiclientdispatch">Client RPC dispatch</a></h3>
+    <h3><a id="apiclientdispatch">Client RPC dispatch</a></h3>

    <p>
      The client RPC code must allow for multiple overlapping RPC method
@@ -601,7 +601,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      grabs the buck, and re-enabled when the buck is released.
    </p>

-    <h4><a name="apiclientdispatchex1">Example with buck passing</a></h4>
+    <h4><a id="apiclientdispatchex1">Example with buck passing</a></h4>

    <p>
      In the first example, a second thread issues an API call
@@ -649,7 +649,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
                      Return API2()
    </pre>

-    <h4><a name="apiclientdispatchex2">Example without buck passing</a></h4>
+    <h4><a id="apiclientdispatchex2">Example without buck passing</a></h4>

    <p>
      In this second example, a second thread issues an API call
@@ -699,7 +699,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
       Return API1()
    </pre>

-    <h4><a name="apiclientdispatchex3">Example with async events</a></h4>
+    <h4><a id="apiclientdispatchex3">Example with async events</a></h4>

    <p>
      In this example, only one thread is present and it has to
@@ -739,7 +739,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
                          ...
    </pre>

-    <h3><a name="apiserverdispatch">Server RPC dispatch</a></h3>
+    <h3><a id="apiserverdispatch">Server RPC dispatch</a></h3>

    <p>
      The RPC server code must support receipt of incoming RPC requests from
@@ -827,7 +827,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      queue.
    </p>

-    <h4><a name="apiserverdispatchex1">Example with overlapping methods</a></h4>
+    <h4><a id="apiserverdispatchex1">Example with overlapping methods</a></h4>

    <p>
      This example illustrates processing of two incoming methods with
@@ -874,7 +874,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;-- S  (reply)
      ...
    </pre>

-    <h4><a name="apiserverdispatchex2">Example with stream data</a></h4>
+    <h4><a id="apiserverdispatchex2">Example with stream data</a></h4>

    <p>
      This example illustrates processing of stream data
--- a/docs/java.html.in
+++ b/docs/java.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Java API bindings</h1>
--- a/docs/locking-lockd.html.in
+++ b/docs/locking-lockd.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Virtual machine lock manager, virtlockd plugin</h1>
@@ -12,7 +12,7 @@
      plugin for virtual machine disk mutual exclusion.
    </p>

-    <h2><a name="background">virtlockd background</a></h2>
+    <h2><a id="background">virtlockd background</a></h2>

    <p>
      The virtlockd daemon is a single purpose binary which
@@ -26,7 +26,7 @@
      commonly used filesystems.
    </p>

-    <h2><a name="sanlock">virtlockd daemon setup</a></h2>
+    <h2><a id="sanlock">virtlockd daemon setup</a></h2>

    <p>
      In most OS, the virtlockd daemon itself will not require
@@ -53,7 +53,7 @@
      setup at all.
    </p>

-    <h2><a name="lockdplugin">libvirt lockd plugin configuration</a></h2>
+    <h2><a id="lockdplugin">libvirt lockd plugin configuration</a></h2>

    <p>
      Once the virtlockd daemon is running, or setup to autostart,
@@ -127,7 +127,7 @@ $ su - root
      the same locking mechanism
    </p>

-    <h2><a name="qemuconfig">QEMU/KVM driver configuration</a></h2>
+    <h2><a id="qemuconfig">QEMU/KVM driver configuration</a></h2>

    <p>
      The QEMU driver is capable of using the virtlockd plugin
--- a/docs/locking-sanlock.html.in
+++ b/docs/locking-sanlock.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Virtual machine lock manager, sanlock plugin</h1>
@@ -13,7 +13,7 @@
      plugin for virtual machine disk mutual exclusion.
    </p>

-    <h2><a name="sanlock">Sanlock daemon setup</a></h2>
+    <h2><a id="sanlock">Sanlock daemon setup</a></h2>

    <p>
      On many operating systems, the <strong>sanlock</strong> plugin
@@ -68,7 +68,7 @@ SANLOCKOPTS="-w 0"
      steps as necessary.
    </p>

-    <h2><a name="sanlockplugin">libvirt sanlock plugin configuration</a></h2>
+    <h2><a id="sanlockplugin">libvirt sanlock plugin configuration</a></h2>

    <p>
      Once the sanlock daemon is running, the next step is to
@@ -91,7 +91,7 @@ $ su - root
      unique value for the host.
    </p>

-    <h2><a name="sanlockstorage">libvirt sanlock storage configuration</a></h2>
+    <h2><a id="sanlockstorage">libvirt sanlock storage configuration</a></h2>

    <p>
      The sanlock plugin needs to create leases in a directory
@@ -152,7 +152,7 @@ augtool -s set /files/etc/libvirt/qemu-sanlock.conf/group sanlock
      it should be sufficient to run the cleanup once a week.
    </p>

-    <h2><a name="qemuconfig">QEMU/KVM driver configuration</a></h2>
+    <h2><a id="qemuconfig">QEMU/KVM driver configuration</a></h2>

    <p>
      The QEMU/KVM driver is fully integrated with the lock
@@ -219,7 +219,7 @@ __LIBVIRT__DISKS__
 &lt;/pool&gt;
    </pre>

-    <h2><a name="domainconfig">Domain configuration</a></h2>
+    <h2><a id="domainconfig">Domain configuration</a></h2>

    <p>
      In case sanlock loses access to disk locks for some reason, it will
--- a/docs/locking.html.in
+++ b/docs/locking.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Virtual machine lock manager</h1>
@@ -15,7 +15,7 @@
      aware filesystem.
    </p>

-    <h2><a name="plugins">Lock manager plugins</a></h2>
+    <h2><a id="plugins">Lock manager plugins</a></h2>

    <p>
      The lock manager framework has a pluggable architecture,
--- a/docs/logging.html.in
+++ b/docs/logging.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1 >Logging in the library and the daemon</h1>
@@ -12,7 +12,7 @@
    <ul id="toc"/>

    <h2>
-      <a name="log_library">Logging in the library</a>
+      <a id="log_library">Logging in the library</a>
    </h2>
    <p>The logging functionalities in libvirt are based on 3 key concepts,
       similar to the one present in other generic logging facilities like
@@ -40,7 +40,7 @@
    </ul>

    <h2>
-      <a name="log_config">Configuring logging in the library</a>
+      <a id="log_config">Configuring logging in the library</a>
    </h2>
    <p>The library configuration of logging is through 3 environment variables
    allowing to control the logging behaviour:</p>
@@ -61,7 +61,7 @@
       have an error in a filter or output string, some of the settings may be
       applied up to the point at which libvirt encountered the error.</p>
    <h2>
-      <a name="log_daemon">Logging in the daemon</a>
+      <a id="log_daemon">Logging in the daemon</a>
    </h2>
    <p>Similarly the daemon logging behaviour can be tuned using 3 config
    variables, stored in the configuration file:</p>
@@ -96,7 +96,7 @@
       for debugging purposes by sending the daemon a USR2 signal:</p>
       <pre>killall -USR2 libvirtd</pre>
    <h2>
-      <a name="log_syntax">Syntax for filters and output values</a>
+      <a id="log_syntax">Syntax for filters and output values</a>
    </h2>
    <p>The syntax for filters and outputs is the same for both types of
       variables.</p>
@@ -149,7 +149,7 @@ x:+name (log message + stack trace)</pre>
       but also log all debug and information included in the
       file <code>/tmp/libvirt.log</code></p>

-    <h2><a name="journald">Systemd journal fields</a></h2>
+    <h2><a id="journald">Systemd journal fields</a></h2>

    <p>
      When logging to the systemd journal, the following fields
@@ -176,7 +176,7 @@ x:+name (log message + stack trace)</pre>
      <dd>The libvirt error code (values from virErrorCode enum), if LIBVIRT_SOURCE="error"</dd>
    </dl>

-    <h3><a name="journaldids">Well known message ID values</a></h3>
+    <h3><a id="journaldids">Well known message ID values</a></h3>

    <p>
      Certain areas of the code will emit log records tagged with well known
@@ -221,7 +221,7 @@ $ journalctl MESSAGE_ID=8ae2f3fb-2dbe-498e-8fbd-012d40afa361 --output=json
    </pre>

    <h2>
-      <a name="log_examples">Examples</a>
+      <a id="log_examples">Examples</a>
    </h2>
    <p>For example setting up the following:</p>
    <pre>export LIBVIRT_DEBUG=1
--- a/docs/main.css
+++ b/docs/main.css
@@ -1,3 +1,4 @@
@import url(fonts/stylesheet.css);
@import url(generic.css);
@import url(libvirt.css);
+@import url(mobile.css);
--- a/docs/manifest.json
+++ b/docs/manifest.json
@@ -0,0 +1,18 @@
+{
+    "name": "Libvirt",
+    "icons": [
+        {
+            "src": "/android-chrome-192x192.png",
+            "sizes": "192x192",
+            "type": "image/png"
+        },
+        {
+            "src": "/android-chrome-256x256.png",
+            "sizes": "256x256",
+            "type": "image/png"
+        }
+    ],
+    "theme_color": "#ffffff",
+    "background_color": "#ffffff",
+    "display": "standalone"
+}
--- a/docs/migration.html.in
+++ b/docs/migration.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <body>
    <h1>Guest migration</h1>
@@ -13,7 +13,7 @@
      libvirt implements several options for migration.
    </p>

-    <h2><a name="transport">Network data transports</a></h2>
+    <h2><a id="transport">Network data transports</a></h2>

    <p>
      There are two options for the data transport used during migration, either
@@ -21,7 +21,7 @@
      over a libvirtd connection.
    </p>

-    <h3><a name="transportnative">Hypervisor native transport</a></h3>
+    <h3><a id="transportnative">Hypervisor native transport</a></h3>
    <p>
      <em>Native</em> data transports may or may not support encryption, depending
      on the hypervisor in question, but will typically have the lowest computational costs
@@ -35,7 +35,7 @@
      <img class="diagram" src="migration-native.png" alt="Migration native path"/>
    </p>

-    <h3><a name="transporttunnel">libvirt tunnelled transport</a></h3>
+    <h3><a id="transporttunnel">libvirt tunnelled transport</a></h3>
    <p>
      <em>Tunnelled</em> data transports will always be capable of strong encryption
      since they are able to leverage the capabilities built in to the libvirt RPC protocol.
@@ -53,7 +53,7 @@
      <img class="diagram" src="migration-tunnel.png" alt="Migration tunnel path"/>
    </p>

-    <h2><a name="flow">Communication control paths/flows</a></h2>
+    <h2><a id="flow">Communication control paths/flows</a></h2>

    <p>
      Migration of virtual machines requires close co-ordination of the two
@@ -61,7 +61,7 @@
      which may be on the source, the destination, or a third host.
    </p>

-    <h3><a name="flowmanageddirect">Managed direct migration</a></h3>
+    <h3><a id="flowmanageddirect">Managed direct migration</a></h3>

    <p>
      With <em>managed direct</em> migration, the libvirt client process
@@ -81,7 +81,7 @@
    </p>


-    <h3><a name="flowpeer2peer">Managed peer to peer migration</a></h3>
+    <h3><a id="flowpeer2peer">Managed peer to peer migration</a></h3>

    <p>
      With <em>peer to peer</em> migration, the libvirt client process only
@@ -103,7 +103,7 @@
    </p>


-    <h3><a name="flowunmanageddirect">Unmanaged direct migration</a></h3>
+    <h3><a id="flowunmanageddirect">Unmanaged direct migration</a></h3>

    <p>
      With <em>unmanaged direct</em> migration, neither the libvirt client
@@ -119,7 +119,7 @@
    </p>


-    <h2><a name="security">Data security</a></h2>
+    <h2><a id="security">Data security</a></h2>

    <p>
      Since the migration data stream includes a complete copy of the guest
@@ -138,7 +138,7 @@
      facility should be used.
    </p>

-    <h2><a name="offline">Offline migration</a></h2>
+    <h2><a id="offline">Offline migration</a></h2>

    <p>
      Offline migration transfers inactive the definition of a domain
@@ -153,7 +153,7 @@
      offline migration.
    </p>

-    <h2><a name="uris">Migration URIs</a></h2>
+    <h2><a id="uris">Migration URIs</a></h2>

    <p>
      Initiating a guest migration requires the client application to
@@ -203,7 +203,7 @@
        to comply with local firewall policies.</li>
    </ol>

-    <h2><a name="config">Configuration file handling</a></h2>
+    <h2><a id="config">Configuration file handling</a></h2>

    <p>
      There are two types of virtual machine known to libvirt. A <em>transient</em>
@@ -446,10 +446,10 @@
      </tbody>
    </table>

-    <h2><a name="scenarios">Migration scenarios</a></h2>
+    <h2><a id="scenarios">Migration scenarios</a></h2>


-    <h3><a name="scenarionativedirect">Native migration, client to two libvirtd servers</a></h3>
+    <h3><a id="scenarionativedirect">Native migration, client to two libvirtd servers</a></h3>

    <p>
      At an API level this requires use of virDomainMigrate, without the
@@ -479,7 +479,7 @@ virsh migrate web1 xen+tcp://desthost/system  xenmigr:10.0.0.1/
      Supported by Xen, QEMU, VMware and VirtualBox drivers
    </p>

-    <h3><a name="scenarionativepeer2peer">Native migration, client to and peer2peer between, two libvirtd servers</a></h3>
+    <h3><a id="scenarionativepeer2peer">Native migration, client to and peer2peer between, two libvirtd servers</a></h3>

    <p>
      virDomainMigrate, with the VIR_MIGRATE_PEER2PEER flag set,
@@ -503,7 +503,7 @@ virsh migrate web1 xen+tcp://desthost/system  xenmigr:10.0.0.1/
      Supported by QEMU driver
    </p>

-    <h3><a name="scenariotunnelpeer2peer1">Tunnelled migration, client and peer2peer between two libvirtd servers</a></h3>
+    <h3><a id="scenariotunnelpeer2peer1">Tunnelled migration, client and peer2peer between two libvirtd servers</a></h3>

    <p>
      virDomainMigrate, with the VIR_MIGRATE_PEER2PEER &amp; VIR_MIGRATE_TUNNELLED
@@ -526,7 +526,7 @@ virsh migrate web1 xen+tcp://desthost/system  xenmigr:10.0.0.1/
      Supported by QEMU driver
    </p>

-    <h3><a name="nativedirectunmanaged">Native migration, client to one libvirtd server</a></h3>
+    <h3><a id="nativedirectunmanaged">Native migration, client to one libvirtd server</a></h3>

    <p>
      virDomainMigrateToURI, without the VIR_MIGRATE_PEER2PEER flag set,
@@ -550,7 +550,7 @@ virsh migrate --direct web1 xenmigr://desthost/
      Supported by Xen driver
    </p>

-    <h3><a name="nativepeer2peer">Native migration, peer2peer between two libvirtd servers</a></h3>
+    <h3><a id="nativepeer2peer">Native migration, peer2peer between two libvirtd servers</a></h3>

    <p>
      virDomainMigrateToURI, with the VIR_MIGRATE_PEER2PEER flag set,
@@ -587,7 +587,7 @@ virsh migrate --p2p web1 qemu+ssh://desthost/system qemu+ssh://10.0.0.1/system
      Supported by the QEMU driver
    </p>

-    <h3><a name="scenariotunnelpeer2peer2">Tunnelled migration, peer2peer between two libvirtd servers</a></h3>
+    <h3><a id="scenariotunnelpeer2peer2">Tunnelled migration, peer2peer between two libvirtd servers</a></h3>

    <p>
      virDomainMigrateToURI, with the VIR_MIGRATE_PEER2PEER &amp; VIR_MIGRATE_TUNNELLED
--- a/docs/mobile.css
+++ b/docs/mobile.css
@@ -0,0 +1,94 @@
+@media (max-width: 1000px) {
+    #home {
+	width: 100%;
+	display: block;
+	margin: 0px;
+	background: white url(logos/logo-banner-dark-256.png) no-repeat center center;
+	height: 94px;
+    }
+    #home a {
+	width: 100%;
+    }
+    #search {
+	width: 100%;
+	display: block;
+	margin: 0px;
+	background: white;
+	padding: 0px;
+    }
+    #search form {
+	padding: 5px;
+    }
+    body.index h1 {
+	display: none;
+    }
+    #jumplinks {
+	padding: 0px;
+	display: block;
+	width: 100%;
+	text-align: center;
+	margin: 0px;
+	height: 1.3em;
+	font-size: 1em;
+	border-top: 3px solid rgb(60, 133, 124);
+	border-bottom: 3px solid rgb(60, 133, 124);
+    }
+    #jumplinks ul {
+	display: block;
+	padding: 0px;
+	margin: 0px;
+    }
+    #jumplinks li {
+	margin: 0px;
+	padding-left: 0.5em;
+	padding-right: 0.5em;
+    }
+    #nav {
+	border: 0px;
+    }
+
+    #search.navhide {
+	display: none !IMPORTANT;
+    }
+    #home.navhide {
+	position: fixed;
+	top: 0px;
+	z-index: 9001;
+	width: 6em;
+	display: block;
+	margin: 0px;
+	background: inherit;
+	height: 1.3em;
+	border-top: 3px solid rgb(60, 133, 124);
+	border-bottom: 3px solid rgb(60, 133, 124);
+	font-size: 1em;
+	text-indent: 0px;
+	font-weight: bold;
+	padding-left: 1em;
+    }
+    #home.navhide a {
+	color: white;
+	text-decoration: none;
+    }
+    #home.navhide a:hover {
+	color: rgb(255, 230, 0);
+    }
+    #jumplinks.navhide {
+	position: fixed;
+	text-align: right;
+	top: 0px;
+	z-index: 9000;
+	background: rgb(0, 95, 97);
+    }
+    #jumplinks.navhide ul {
+	z-index: 9001;
+    }
+    #body {
+	margin-top: 180px;
+    }
+    div.panel {
+	width: 80%;
+	float: none;
+	margin-bottom: 2em;
+    }
+}
--- a/docs/mstile-150x150.png
+++ b/docs/mstile-150x150.png
--- a/docs/newapi.xsl
+++ b/docs/newapi.xsl
@@ -17,10 +17,7 @@
  <!-- Import the main part of the site stylesheets -->
  <xsl:import href="page.xsl"/>

-  <!-- Generate XHTML-1.0 transitional -->
-  <xsl:output method="xml" encoding="UTF-8" indent="yes"
-      doctype-public="-//W3C//DTD XHTML 1.0//EN"
-      doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"/>
+  <xsl:output method="xml" encoding="UTF-8" indent="yes"/>

  <!-- Build keys for all symbols -->
  <xsl:key name="symbols" match="/api/symbols/*" use="@name"/>
@@ -737,6 +734,8 @@
  <xsl:template match="file">
    <xsl:variable name="name" select="@name"/>
    <xsl:variable name="title">Module <xsl:value-of select="$name"/> from <xsl:value-of select="/api/@name"/></xsl:variable>
+    <xsl:text disable-output-escaping="yes">&lt;!DOCTYPE html&gt;
+</xsl:text>
    <html>
      <body>
        <h1><xsl:value-of select="$title"/></h1>
@@ -794,6 +793,8 @@

  <xsl:template name="mainpage">
    <xsl:variable name="title">Reference Manual for <xsl:value-of select="/api/@name"/></xsl:variable>
+    <xsl:text disable-output-escaping="yes">&lt;!DOCTYPE html&gt;
+</xsl:text>
    <html>
      <body>
        <h1><xsl:value-of select="$title"/></h1>
@@ -813,9 +814,8 @@
    <xsl:document
      href="{concat($htmldir, '/index.html')}"
      method="xml"
-      encoding="UTF-8"
-      doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"
-      doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+      indent="yes"
+      encoding="UTF-8">
      <xsl:apply-templates select="exsl:node-set($mainpage)" mode="page">
        <xsl:with-param name="pagename" select="concat($htmldir, '/index.html')"/>
        <xsl:with-param name="timestamp" select="$timestamp"/>
@@ -830,9 +830,8 @@
      <xsl:document
        href="{concat($htmldir, '/libvirt-', @name, '.html')}"
        method="xml"
-        encoding="UTF-8"
-        doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"
-        doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+        indent="yes"
+        encoding="UTF-8">
        <xsl:apply-templates select="exsl:node-set($subpage)" mode="page">
          <xsl:with-param name="pagename" select="concat($htmldir, '/libvirt-', @name, '.html')"/>
          <xsl:with-param name="timestamp" select="$timestamp"/>
--- a/docs/news-2005.html.in
+++ b/docs/news-2005.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -9,9 +9,9 @@
    <p>Here is the list of official releases made during the year 2005.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2006.html.in
+++ b/docs/news-2006.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2005.html">2005</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2007.html.in
+++ b/docs/news-2007.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2006.html">2006</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2008.html.in
+++ b/docs/news-2008.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2007.html">2007</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2009.html.in
+++ b/docs/news-2009.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2008.html">2008</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2010.html.in
+++ b/docs/news-2010.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2009.html">2009</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2011.html.in
+++ b/docs/news-2011.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2010.html">2010</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2012.html.in
+++ b/docs/news-2012.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2011.html">2011</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2013.html.in
+++ b/docs/news-2013.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
@@ -10,9 +10,9 @@
    A similar list for <a href="news-2012.html">2012</a> is also available.
    </p>
    <p>It is also possible to just use
-    the <a href="downloads.html" shape="rect">GIT version or snapshot</a>,
+    the <a href="downloads.html">GIT version or snapshot</a>,
    contact the mailing list and check
-    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log" shape="rect">GIT log</a>
+    the <a href="http://libvirt.org/git/?p=libvirt.git;a=log">GIT log</a>
    to gauge progress.
    </p>

--- a/docs/news-2014.html.in
+++ b/docs/news-2014.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
--- a/docs/news-2015.html.in
+++ b/docs/news-2015.html.in
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
--- a/Show More
+++ b/Show More