[Pkg-libvirt-commits] [libguestfs] 49/179: FAQ: Add a section on debugging libvirtd.

[Hilko Bengen]

This is an automated email from the git hooks/post-receive script.

bengen pushed a commit to branch experimental
in repository libguestfs.

commit 7893a2cfb1b2e2e8fba9ceab35b498025fbe535a
Author: Richard W.M. Jones <rjones at redhat.com>
Date:   Fri Oct 10 11:47:26 2014 +0100

    FAQ: Add a section on debugging libvirtd.
---
 examples/guestfs-faq.pod | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/examples/guestfs-faq.pod b/examples/guestfs-faq.pod
index 575c086..f00ba7a 100644
--- a/examples/guestfs-faq.pod
+++ b/examples/guestfs-faq.pod
@@ -977,6 +977,21 @@ Enable debugging and look at the full output.  If you cannot work out
 what is going on, file a bug report, including the I<complete> output
 of L<libguestfs-test-tool(1)>.
 
+=head2 Debugging libvirt
+
+If you are using the libvirt backend, and libvirt is failing, then you
+can enable debugging by editing C</etc/libvirt/libvirtd.conf>.
+
+If you are running as non-root, then you have to edit a different
+file.  Create C<~/.config/libvirt/libvirtd.conf> containing:
+
+ log_level=1
+ log_outputs="1:file:/tmp/libvirtd.log"
+
+Kill any session (non-root) libvirtd that is running, and next time
+you run the libguestfs command, you should see a large amount of
+useful debugging information from libvirtd in C</tmp/libvirtd.log>
+
 =head1 DESIGN/INTERNALS OF LIBGUESTFS
 
 =head2 Why don't you do everything through the FUSE / filesystem

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-libvirt/libguestfs.git