[Pkg-libvirt-commits] [libguestfs] 01/40: v2v: Add documentation for diagnosing RHEV-M import problems.

[Hilko Bengen]

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

bengen pushed a commit to annotated tag debian/1%1.27.57-1
in repository libguestfs.

commit 159d246b1dc4aae69ea04bbaeebaf3edd1fbcf23
Author: Richard W.M. Jones <rjones at redhat.com>
Date:   Fri Sep 26 19:14:57 2014 +0100

    v2v: Add documentation for diagnosing RHEV-M import problems.
---
 v2v/virt-v2v.pod | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
index 646b3bd..47fa632 100644
--- a/v2v/virt-v2v.pod
+++ b/v2v/virt-v2v.pod
@@ -857,6 +857,26 @@ Define the final guest in libvirt:
 
 =back
 
+=head1 DEBUGGING RHEV-M IMPORT FAILURES
+
+When you export to the RHEV-M Export Storage Domain, and then import
+that guest through the RHEV-M UI, you may encounter an import failure.
+Diagnosing these failures is infuriatingly difficult as the UI
+generally hides the true reason for the failure.
+
+There are two log files of interest.  The first is stored on the
+RHEV-M server itself, and is called
+C</var/log/ovirt-engine/engine.log>
+
+The second file, which is the most useful, is found on the SPM host
+(SPM stands for "Storage Pool Manager").  This is a RHEV node that is
+elected to do all metadata modifications in the data center, such as
+image or snapshot creation.  You can find out which host is the
+current SPM from the "Hosts" tab "Spm Status" column.  Once you have
+located the SPM, log into it and grab the file
+C</var/log/vdsm/vdsm.log> which will contain detailed error messages
+from low-level commands.
+
 =head1 MINIMAL XML FOR -i libvirtxml OPTION
 
 When using the I<-i libvirtxml> option, you have to supply some

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