From e9406e9ea768e9f64838ffb7f57d72c7556aa03f Mon Sep 17 00:00:00 2001
From: Serge Hallyn <serge.hallyn@canonical.com>
Date: Tue, 15 Jun 2010 16:46:21 -0600
Subject: [PATCH] docs: fix lxc examples

* docs/drvlxc.html.in: Use correct VM name, and mention that
libvirt_lxc might be in an alternate location.
---
 AUTHORS             |  1 +
 docs/drvlxc.html.in | 14 +++++++++++---
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/AUTHORS b/AUTHORS
index 8b037a185a..0521b3d671 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -128,6 +128,7 @@ Patches have also been contributed by:
   Alan Pevec           <apevec@redhat.com>
   Aurelien Rougemont   <beorn@binaries.fr>
   Patrick Dignan       <pat_dignan@dell.com>
+  Serge Hallyn         <serge.hallyn@canonical.com>
 
   [....send patches to get your name here....]
 
diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in
index cfcfdab2ab..35058c4f5b 100644
--- a/docs/drvlxc.html.in
+++ b/docs/drvlxc.html.in
@@ -34,6 +34,11 @@ start it using
 &lt;/domain&gt;
 </pre>
 
+<p>
+In the &lt;emulator&gt; element, be sure you specify the correct path
+to libvirt_lxc, if it does not live in /usr/libexec on your system.
+</p>
+
 <p>
 The next example assumes there is a private root filesystem
 (perhaps hand-crafted using busybox, or installed from media,
@@ -71,14 +76,17 @@ debootstrap, whatever) under /opt/vm-1-root:
 In both cases, you can define and start a container using:</p>
 <pre>
 virsh --connect lxc:/// define v1.xml
-virsh --connect lxc:/// start v1.xml
+virsh --connect lxc:/// start vm1
 </pre>
 and then get a console  using:
 <pre>
-virsh --connect lxc:/// console v1
+virsh --connect lxc:/// console vm1
 </pre>
 <p>Now doing 'ps -ef' will only show processes in the container, for
-instance.
+instance.  You can undefine it using
 </p>
+<pre>
+virsh --connect lxc:/// undefine vm1
+</pre>
   </body>
 </html>