Bug 1250670

Summary: libguestfs-test-tool succeeds but guestmount fails
Product: [Community] Virtualization Tools Reporter: Itamar <itamarggal>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: itamarggal, ptoscano
Target Milestone: ---Flags: rjones: needinfo? (itamarggal)
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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
libguestfs-test-tool output none

Description Itamar 2015-08-05 18:12:53 UTC 
Created attachment 1059580 [details]
libguestfs-test-tool output

Description of problem:

libguestfs-test-tool succeeds but guestmount fails with the following error:

    libguestfs: error: guestfs_launch failed.


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

guestmount 1.20.11rhel=6,release=11.el6

libguestfs-test-tool 1.20.11rhel=6,release=11.el6


How reproducible:


Steps to Reproduce:
1. sudo guestmount -a "${path_to_vdi_file}" -i --ro /mnt/mountpoint
2.
3.

Actual results:

libguestfs: error: guestfs_launch failed.
See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
and/or run 'libguestfs-test-tool'.

Expected results:

mounted vdi file-system at mountpoint, no error message

Additional info:

Running on CentOS 6.6
Comment 1 Richard W.M. Jones 2015-08-05 19:08:23 UTC 
To find out what the real error is you should enable debugging
in the guestmount command by adding the --verbose and --trace
flags, as in this example:

$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.7 Beta (Santiago)
$ guestfish -N fs exit
$ mkdir /tmp/mp
$ guestmount -a test1.img -m /dev/sda1 --verbose --trace /tmp/mp

That will produce a lot of debug output which should identify the
error.  If you cannot tell from that what's going on, then copy
the *complete* output from your failing guestmount command as
an attachment to this bug.