+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml">
- <body>
- <h1>Internal drivers</h1>
-
- <ul>
- <li><a href="#hypervisor">Hypervisor drivers</a></li>
- <li><a href="storage.html">Storage drivers</a></li>
- <li><a href="drvnodedev.html">Node device driver</a></li>
- <li><a href="drvsecret.html">Secret driver</a></li>
- </ul>
-
- <p>
- The libvirt public API delegates its implementation to one or
- more internal drivers, depending on the <a href="uri.html">connection URI</a>
- passed when initializing the library. There is always a hypervisor driver
- active, and if the libvirt daemon is available there will usually be a
- network and storage driver active.
- </p>
-
- <h2><a id="hypervisor">Hypervisor drivers</a></h2>
-
- <p>
- The hypervisor drivers currently supported by libvirt are:
- </p>
-
- <ul>
- <li><strong><a href="drvlxc.html">LXC</a></strong> - Linux Containers</li>
- <li><strong><a href="drvopenvz.html">OpenVZ</a></strong></li>
- <li><strong><a href="drvqemu.html">QEMU</a></strong></li>
- <li><strong><a href="drvtest.html">Test</a></strong> - Used for testing</li>
- <li><strong><a href="drvvbox.html">VirtualBox</a></strong></li>
- <li><strong><a href="drvesx.html">VMware ESX</a></strong></li>
- <li><strong><a href="drvvmware.html">VMware Workstation/Player</a></strong></li>
- <li><strong><a href="drvxen.html">Xen</a></strong></li>
- <li><strong><a href="drvhyperv.html">Microsoft Hyper-V</a></strong></li>
- <li><strong><a href="drvvirtuozzo.html">Virtuozzo</a></strong></li>
- <li><strong><a href="drvbhyve.html">Bhyve</a></strong> - The BSD Hypervisor</li>
- <li><strong><a href="drvch.html">Cloud Hypervisor</a></strong></li>
- </ul>
-
- </body>
-</html>
--- /dev/null
+================
+Internal drivers
+================
+
+- `Hypervisor drivers <#hypervisor-drivers>`__
+- `Storage drivers <storage.html>`__
+- `Node device driver <drvnodedev.html>`__
+- `Secret driver <drvsecret.html>`__
+
+The libvirt public API delegates its implementation to one or more internal
+drivers, depending on the `connection URI <uri.html>`__ passed when initializing
+the library. There is always a hypervisor driver active, and if the libvirt
+daemon is available there will usually be a network and storage driver active.
+
+Hypervisor drivers
+------------------
+
+The hypervisor drivers currently supported by libvirt are:
+
+- `LXC <drvlxc.html>`__ - Linux Containers
+- `OpenVZ <drvopenvz.html>`__
+- `QEMU <drvqemu.html>`__
+- `Test <drvtest.html>`__ - Used for testing
+- `VirtualBox <drvvbox.html>`__
+- `VMware ESX <drvesx.html>`__
+- `VMware Workstation/Player <drvvmware.html>`__
+- `Xen <drvxen.html>`__
+- `Microsoft Hyper-V <drvhyperv.html>`__
+- `Virtuozzo <drvvirtuozzo.html>`__
+- `Bhyve <drvbhyve.html>`__ - The BSD Hypervisor
+- `Cloud Hypervisor <drvch.html>`__
projects / thirdparty / libvirt.git / commitdiff
