From: Justin Clift Date: Wed, 22 Dec 2010 12:48:25 +0000 (+1100) Subject: docs: fixed typo, added table of contents X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=c207b6d9f932619e7dfec4b5e71950f6ac2d781a;p=libvirt.git docs: fixed typo, added table of contents --- diff --git a/docs/drvopenvz.html.in b/docs/drvopenvz.html.in index e446b1a880..485d2096d2 100644 --- a/docs/drvopenvz.html.in +++ b/docs/drvopenvz.html.in @@ -2,6 +2,8 @@

OpenVZ container driver

+ +

The OpenVZ driver for libvirt allows use and management of container based virtualization on a Linux host OS. Prior to using the OpenVZ @@ -11,11 +13,11 @@ undue trouble.

-

Connections to OpenVZ driver

+

Connections to OpenVZ driver

The libvirt OpenVZ driver is a single-instance privileged driver, - with a driver name of 'openvz'. Some example conection URIs for + with a driver name of 'openvz'. Some example connection URIs for the libvirt driver are:

@@ -27,7 +29,7 @@ openvz+tcp://example.com/system (remote access, SASl/Kerberos) openvz+ssh://root@example.com/system (remote access, SSH tunnelled) -

Notes on bridged networking

+

Notes on bridged networking

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

-

Host network devices

+

Host network devices

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

-

OpenVZ tools configuration

+

OpenVZ tools configuration

OpenVZ releases later than 3.0.23 ship with a standard network device @@ -72,7 +74,7 @@ EXTERNAL_SCRIPT="/usr/sbin/vznetaddbr"

-

Example guest domain XML configuration

+

Example guest domain XML configuration

The current libvirt OpenVZ driver has a restriction that the