Re: [Libguestfs] [PATCH] v2v: docs: VDSM location of virt-v2v log file.

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-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 -RHV-M server itself, and is called -F</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 RHV 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 -F</var/log/vdsm/vdsm.log> which will contain detailed error messages -from low-level commands. +There are three log files of interest:

+ +=over 4 + +=item F</var/log/vdsm/import/> + +In oVirt E<ge> 4.1.0, vdsm preserves the virt-v2v log file for +30 days in this directory.

+ +This directory is found on the SPM host (SPM stands for "Storage Pool +Manager"). This is a RHV 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.