Bug 1469339

Summary: [virt-v2v] Inspection Could Not Detect Source Guest (CentOS OVA from VMware)
Product: [Community] Virtualization Tools Reporter: Zach Seils <seils>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: ptoscano, rbalakri
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-11 06:42:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
virt-v2v output with -v -x none

Description Zach Seils 2017-07-11 02:33:17 UTC 
Created attachment 1296028 [details]
virt-v2v output with -v -x

Description of problem:

While trying to convert an OVA exported from VMware vSphere to libvirt using virt-v2v, I get the following error:

virt-v2v: error: inspection could not detect the source guest (or physical 
machine).

Version-Release number of selected component (if applicable):

Base OS: 16.04.2 LTS (Xenial Xerus)
Source VM OS: CentOS 7
libguestfs: 1.32.2 (patched with https://github.com/libguestfs/libguestfs/commit/fd60be95091a1923e108f72caf251f5549eeccd0)


How reproducible: 100%


Steps to Reproduce:
1. Export CentOS using VMware ovftool
2. Execute virt-v2v command:

sudo virt-v2v -v -i ova fso-app-p01.ova -o libvirt -os projects -of qcow2

Actual results: See attached log.


Expected results: No failures; new domain created from source OVA.


Additional info:
Comment 1 Pino Toscano 2017-07-11 06:42:25 UTC 
This happens because that version of libguestfs does not identifies correctly a separate /usr partition.

This was reported already as bug 1186935, and fixed in libguestfs >= 1.35.15.

*** This bug has been marked as a duplicate of bug 1186935 ***