libvirt/docs/index.html.in

<?xml version="1.0"?>
<html>
  <body>
    <h1>The virtualization API</h1>

    <h2>libvirt is:</h2>

    <ul>
      <li>
        A toolkit to interact with the virtualization capabilities
        of recent versions of Linux (and other OSes), see our
        <a href="goals.html">project goals</a> for details.
      </li>
      <li>
        Free software available under the
        <a href="http://www.opensource.org/licenses/lgpl-license.html">GNU
          Lesser General Public License</a>.
      </li>

      <li>
        A long term stable C API
      </li>
      <li>
        A set of bindings for common languages
      </li>
      <li>
        A <a href="CIM/">CIM provider</a> for the DMTF virtualization schema
      </li>
      <li>
        A <a href="/qpid/">QMF agent</a> for the AMQP/QPid messaging system
      </li>
    </ul>

    <h2>libvirt supports:</h2>

    <ul>
      <li>
        The <a href="http://libvirt.org/drvqemu.html">KVM/QEMU</a> Linux hypervisor
      </li>
      <li>
        The <a href="http://libvirt.org/drvxen.html">Xen</a> hypervisor
        on Linux and Solaris hosts.
      </li>
      <li>
        The <a href="http://libvirt.org/drvlxc.html">LXC</a> Linux container system
      </li>
      <li>
        The <a href="http://libvirt.org/drvopenvz.html">OpenVZ</a> Linux container system
      </li>
      <li>
        The <a href="http://libvirt.org/drvuml.html">User Mode Linux</a> paravirtualized kernel
      </li>
      <li>
        The <a href="http://libvirt.org/drvvbox.html">VirtualBox</a> hypervisor
      </li>
      <li>
        The <a href="http://libvirt.org/drvesx.html">VMware ESX and GSX</a> hypervisors
      </li>
      <li>
        The <a href="http://libvirt.org/drvvmware.html">VMware Workstation and Player</a> hypervisors
      </li>
      <li>
        The <a href="http://libvirt.org/drvhyperv.html">Microsoft Hyper-V</a> hypervisor
      </li>
      <li>
        Virtual networks using bridging, NAT, VEPA and VN-LINK.
      </li>
      <li>
        Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems
      </li>
    </ul>

    <h2>libvirt provides:</h2>

    <ul>
      <li>Remote management using TLS encryption and x509 certificates</li>
      <li>Remote management authenticating with Kerberos and SASL</li>
      <li>Local access control using PolicyKit</li>
      <li>Zero-conf discovery using Avahi multicast-DNS</li>
      <li>Management of virtual machines, virtual networks and storage</li>
      <li>Portable client API for Linux, Solaris and Windows</li>
    </ul>

    <p class="image">
      <img src="libvirtLogo.png" alt="libvirt Logo"/>
    </p>
  </body>
</html>
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`<?xml version="1.0"?>`
			`<html>`
			`<body>`
			`<h1>The virtualization API</h1>`

			`<h2>libvirt is:</h2>`

			`<ul>`
			`<li>`
Cleanup whitespace in docs This patch is the result of running the following command in the docs directory: sed -i 's/\t/ /g; s/\s$//' .html.in * docs/*.html.in:convert tabs into 8 spaces and remove trailing whitespace 2009-11-06 23:04:19 +08:00			`A toolkit to interact with the virtualization capabilities`
Update on the goal page Some things to note in this patch: - we do extend libvirt scope beyond purely managing domains, there is already a number of blocks which are here as helpr functions to manage the resources on the host. - we are expanding in the direction of libvirt being sufficient to do most of the management on the Host (but within the limits of the need for virtualization, e.g. managing users on the host is out of scope) - we don't require anymore APIs to be supported by multiple hypervisors to get in, it's already the case in practice, but we should still make sure the semantic of those APIs are clear. We added quite a bit for QEmu, but for example I saw on IRC that VBox could emulate a network unplug/replug on a domain interface, and that would be a good addition even if a priori no other hypervisor supports it. - Make clear that all libvirt APIs are available remotely, which is key to use libvirt for building management tools. - link the goal page from the project main page As for libvirt project directions, I think it just reflects the natural evolution in the last couple of years. We are less hypervisor agnostic and extending in the Host management. Clearly there is interest in making sure libvirt is complete in term of features for the hypervisors supported, especially the ones like KVM or LXC which don't really have integrated management library. * docs/goals.html.in: update the goals page * docs/index.html.in: link it from the top page 2011-03-28 10:40:24 +08:00			`of recent versions of Linux (and other OSes), see our`
			`<a href="goals.html">project goals</a> for details.`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`<li>`
Cleanup whitespace in docs This patch is the result of running the following command in the docs directory: sed -i 's/\t/ /g; s/\s$//' .html.in * docs/*.html.in:convert tabs into 8 spaces and remove trailing whitespace 2009-11-06 23:04:19 +08:00			`Free software available under the`
			`<a href="http://www.opensource.org/licenses/lgpl-license.html">GNU`
			`Lesser General Public License</a>.`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`

			`<li>`
Cleanup whitespace in docs This patch is the result of running the following command in the docs directory: sed -i 's/\t/ /g; s/\s$//' .html.in * docs/*.html.in:convert tabs into 8 spaces and remove trailing whitespace 2009-11-06 23:04:19 +08:00			`A long term stable C API`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`<li>`
Cleanup whitespace in docs This patch is the result of running the following command in the docs directory: sed -i 's/\t/ /g; s/\s$//' .html.in * docs/*.html.in:convert tabs into 8 spaces and remove trailing whitespace 2009-11-06 23:04:19 +08:00			`A set of bindings for common languages`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`<li>`
Cleanup whitespace in docs This patch is the result of running the following command in the docs directory: sed -i 's/\t/ /g; s/\s$//' .html.in * docs/*.html.in:convert tabs into 8 spaces and remove trailing whitespace 2009-11-06 23:04:19 +08:00			`A <a href="CIM/">CIM provider</a> for the DMTF virtualization schema`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
Added link to libvirt-qpid on front page, and docs on URI formats for each driver 2009-01-27 22:49:09 +08:00			`<li>`
Cleanup whitespace in docs This patch is the result of running the following command in the docs directory: sed -i 's/\t/ /g; s/\s$//' .html.in * docs/*.html.in:convert tabs into 8 spaces and remove trailing whitespace 2009-11-06 23:04:19 +08:00			`A <a href="/qpid/">QMF agent</a> for the AMQP/QPid messaging system`
Added link to libvirt-qpid on front page, and docs on URI formats for each driver 2009-01-27 22:49:09 +08:00			`</li>`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</ul>`

			`<h2>libvirt supports:</h2>`

			`<ul>`
			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvqemu.html">KVM/QEMU</a> Linux hypervisor`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvxen.html">Xen</a> hypervisor`
			`on Linux and Solaris hosts.`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvlxc.html">LXC</a> Linux container system`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvopenvz.html">OpenVZ</a> Linux container system`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvuml.html">User Mode Linux</a> paravirtualized kernel`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
Added link to libvirt-qpid on front page, and docs on URI formats for each driver 2009-01-27 22:49:09 +08:00			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvvbox.html">VirtualBox</a> hypervisor`
Added link to libvirt-qpid on front page, and docs on URI formats for each driver 2009-01-27 22:49:09 +08:00			`</li>`
release of 0.6.3 * NEWS configure.in libvirt.spec.in docs/: release of 0.6.3 po/: regenerated src/libvirt.c src/virterror.c: fixed some function comments Daniel 2009-04-24 22:04:54 +08:00			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvesx.html">VMware ESX and GSX</a> hypervisors`
release of 0.6.3 * NEWS configure.in libvirt.spec.in docs/: release of 0.6.3 po/: regenerated src/libvirt.c src/virterror.c: fixed some function comments Daniel 2009-04-24 22:04:54 +08:00			`</li>`
esx: Add documentation to the website * docs/drivers.html.in: list the ESX driver * docs/drvesx.html.in: the new ESX driver documentation * docs/hvsupport.html.in: add the ESX driver to the matrix * docs/index.html.in, docs/sitemap.html.in: list the ESX driver * src/esx/esx_driver.c: fix and cleanup some comments 2009-11-14 05:43:10 +08:00			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`The <a href="http://libvirt.org/drvvmware.html">VMware Workstation and Player</a> hypervisors`
esx: Add documentation to the website * docs/drivers.html.in: list the ESX driver * docs/drvesx.html.in: the new ESX driver documentation * docs/hvsupport.html.in: add the ESX driver to the matrix * docs/index.html.in, docs/sitemap.html.in: list the ESX driver * src/esx/esx_driver.c: fix and cleanup some comments 2009-11-14 05:43:10 +08:00			`</li>`
hyperv: Add basic documentation 2011-07-13 23:13:42 +08:00			`<li>`
			`The <a href="http://libvirt.org/drvhyperv.html">Microsoft Hyper-V</a> hypervisor`
			`</li>`
Add info about VMware driver to the libvirt website 2010-12-23 16:35:51 +08:00			`<li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-16 02:33:17 +08:00			`Virtual networks using bridging, NAT, VEPA and VN-LINK.`
Add info about VMware driver to the libvirt website 2010-12-23 16:35:51 +08:00			`</li>`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`<li>`
Cleanup whitespace in docs This patch is the result of running the following command in the docs directory: sed -i 's/\t/ /g; s/\s$//' .html.in * docs/*.html.in:convert tabs into 8 spaces and remove trailing whitespace 2009-11-06 23:04:19 +08:00			`Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</li>`
			`</ul>`

			`<h2>libvirt provides:</h2>`

			`<ul>`
			`<li>Remote management using TLS encryption and x509 certificates</li>`
			`<li>Remote management authenticating with Kerberos and SASL</li>`
			`<li>Local access control using PolicyKit</li>`
* proxy/libvirt_proxy.c and docs/* typo fixing Atsushi 2008-04-24 17:17:29 +08:00			`<li>Zero-conf discovery using Avahi multicast-DNS</li>`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`<li>Management of virtual machines, virtual networks and storage</li>`
Added link to libvirt-qpid on front page, and docs on URI formats for each driver 2009-01-27 22:49:09 +08:00			`<li>Portable client API for Linux, Solaris and Windows</li>`
Split website out into one file per page. APply new layout and styling 2008-04-24 01:08:31 +08:00			`</ul>`

			`<p class="image">`
			`<img src="libvirtLogo.png" alt="libvirt Logo"/>`
			`</p>`
			`</body>`
			`</html>`