External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 05:35:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

website: Point main page links to libvirt driver pages

Browse Source 
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
This commit is contained in:
Dave Allan 2011-07-15 14:33:17 -04:00 committed by Eric Blake
parent 8d733f4ef1
commit e5adda7e6b
9 changed files with 90 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/drvesx.html.in
View File

@ -8,6 +8,14 @@
connect to a VMware vCenter 2.5/4.x (VPX).
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://www.vmware.com/">VMware ESX and GSX</a>
hypervisors
</li>
</ul>
<h2><a name="prereq">Deployment pre-requisites</a></h2>
<p>

12
docs/drvlxc.html.in
View File

@ -5,10 +5,18 @@
The libvirt LXC driver manages "Linux Containers". Containers are sets of processes
with private namespaces which can (but don't always) look like separate machines, but
do not have their own OS. Here are two example configurations. The first is a very
light-weight "application container" which does not have it's own root image. You would
start it using
light-weight "application container" which does not have its own root image.
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://lxc.sourceforge.net/">LXC</a> Linux
container system
</li>
</ul>
<h2>Cgroups Requirements</h2>
<p>

9
docs/drvopenvz.html.in
View File

@ -13,6 +13,15 @@
undue trouble.
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://openvz.org/">OpenVZ</a> Linux container
system
</li>
</ul>
<h2><a name="connections">Connections to OpenVZ driver</a></h2>
<p>

20
docs/drvqemu.html.in
View File

@ -1,15 +1,27 @@
<html>
<body>
<h1>QEMU/KVM hypervisor driver</h1>
<h1>KVM/QEMU hypervisor driver</h1>
<ul id="toc"></ul>
<p>
The libvirt QEMU driver can manage any QEMU emulator from version 0.8.1
or later. It can also manage anything that provides the same QEMU command
line syntax and monitor interaction. This includes KVM, and Xenner.
The libvirt KVM/QEMU driver can manage any QEMU emulator from
version 0.8.1 or later. It can also manage Xenner, which
provides the same QEMU command line syntax and monitor
interaction.
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://www.linux-kvm.org/">KVM</a> Linux
hypervisor
<li>
The <a href="http://wiki.qemu.org/Index.html">QEMU</a> emulator
</li>
</ul>
<h2><a name="prereq">Deployment pre-requisites</a></h2>
<ul>

9
docs/drvuml.html.in
View File

@ -11,6 +11,15 @@
has pre-created TAP devices.
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://user-mode-linux.sourceforge.net/">User
Mode Linux</a> paravirtualized kernel
</li>
</ul>
<h2>Connections to UML driver</h2>
<p>

9
docs/drvvbox.html.in
View File

@ -6,6 +6,15 @@
from version 2.2 onwards.
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://www.virtualbox.org/">VirtualBox</a>
hypervisor
</li>
</ul>
<h2>Connections to VirtualBox driver</h2>
<p>

9
docs/drvvmware.html.in
View File

@ -12,6 +12,15 @@
from <a href="http://www.vmware.com/support/developer/vix-api/">here</a>.
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://www.vmware.com/">VMware Workstation and
Player</a> hypervisors
</li>
</ul>
<h2>Connections to VMware driver</h2>
<p>

9
docs/drvxen.html.in
View File

@ -9,6 +9,15 @@
on any Xen release from 3.0.1 onwards.
</p>
<h2><a name="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/index.html">Xen</a>
hypervisor on Linux and Solaris hosts
</li>
</ul>
<h2><a name="prereq">Deployment pre-requisites</a></h2>
<p>

22
docs/index.html.in
View File

@ -35,32 +35,32 @@
<ul>
<li>
The <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/index.html">Xen</a> hypervisor
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://wiki.qemu.org/Index.html">QEMU</a> emulator
The <a href="http://libvirt.org/drvlxc.html">LXC</a> Linux container system
</li>
<li>
The <a href="http://www.linux-kvm.org/">KVM</a> Linux hypervisor
The <a href="http://libvirt.org/drvopenvz.html">OpenVZ</a> Linux container system
</li>
<li>
The <a href="http://lxc.sourceforge.net/">LXC</a> Linux container system
The <a href="http://libvirt.org/drvuml.html">User Mode Linux</a> paravirtualized kernel
</li>
<li>
The <a href="http://openvz.org/">OpenVZ</a> Linux container system
The <a href="http://libvirt.org/drvvbox.html">VirtualBox</a> hypervisor
</li>
<li>
The <a href="http://user-mode-linux.sourceforge.net/">User Mode Linux</a> paravirtualized kernel
The <a href="http://libvirt.org/drvesx.html">VMware ESX and GSX</a> hypervisors
</li>
<li>
The <a href="http://www.virtualbox.org/">VirtualBox</a> hypervisor
The <a href="http://libvirt.org/drvvmware.html">VMware Workstation and Player</a> hypervisors
</li>
<li>
The <a href="http://www.vmware.com/">VMware ESX and GSX</a> hypervisors
</li>
<li>
The <a href="http://www.vmware.com/">VMware Workstation and Player</a> hypervisors
Virtual networks using bridging, NAT, VEPA and VN-LINK.
</li>
<li>
Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems