From b1a89d3b1ccdcd5aed3619cfc2c47812b288205e Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Mon, 11 Feb 2013 14:05:26 +0000
Subject: [PATCH] test-tool: Document how to run with alternate libvirt.

---
 test-tool/libguestfs-test-tool.pod | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/test-tool/libguestfs-test-tool.pod b/test-tool/libguestfs-test-tool.pod
index ddd212d4c..3345a8901 100644
--- a/test-tool/libguestfs-test-tool.pod
+++ b/test-tool/libguestfs-test-tool.pod
@@ -90,6 +90,21 @@ old febootstrap 3.21 program).
 Refer to L<supermin-helper(8)/ENVIRONMENT VARIABLES>
 for further information.
 
+=head1 TRYING OUT A DIFFERENT VERSION OF LIBVIRT
+
+If you are using the libvirt attach-method, then you can try out a
+different (eg. upstream) version of libvirt by running these commands
+(I<not> as root):
+
+ killall libvirtd lt-libvirtd
+ ~/path/to/libvirt/run libguestfs-test-tool
+
+The first command kills any session C<libvirtd> process(es) that may
+be running on the machine.  The second command uses libvirt's C<run>
+script (in the top-level libvirt build directory) to set some
+environment variables so that the alternate version of libvirt is used
+to run the program.
+
 =head1 SELF-DIAGNOSIS
 
 Refer to L<guestfs(3)/APPLIANCE BOOT PROCESS> to understand the