RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1443955 - There is error info about permission denied when convert a guest from vmx file by virt-v2v
Summary: There is error info about permission denied when convert a guest from vmx fil...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.4
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
Whiteboard: V2V
Depends On: 1045069
Blocks: 1558351
TreeView+ depends on / blocked
Reported: 2017-04-20 10:39 UTC by kuwei@redhat.com
Modified: 2019-05-13 09:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-13 09:39:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description kuwei@redhat.com 2017-04-20 10:39:56 UTC
Description of problem:
There is error info about permission denied when convert a guest from vmx file by virt-v2v

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

How reproducible:

Steps to Reproduce:
1.Mount the NFS storage which contains VMware virtual machines to virt-v2v conversion server as below:
#mount IP:/path  /mnt

2.Locate in VMware virtual machine directory, then import the vmx file to KVM by virt-v2v
#virt-v2v -i vmx esx5.5-rhel7.2-x86_64.vmx -of qcow2
[   0.0] Opening the source -i vmx esx5.5-rhel7.2-x86_64.vmx
[   0.0] Creating an overlay to protect the source from being modified
[   0.2] Initializing the target -o libvirt -os default
[   0.2] Opening the overlay
virt-v2v: error: libguestfs error: could not create appliance through 

Try running qemu directly without libvirt using this environment variable:

Original error from libvirt: internal error: process exited while 
connecting to monitor: 2017-04-20T06:30:44.247605Z qemu-kvm: -drive 
Could not open backing file: Could not open 
'/mnt/esx5.5-rhel7.2-x86_64/esx5.5-rhel7.2-x86_64.vmdk': Permission denied 
[code=1 int1=-1]

If reporting bugs, run virt-v2v with debugging enabled and include the 
complete output:

  virt-v2v -v -x [...]

Actual results:
As above description

Expected results:
virt-v2v should not report any error when convert a guest from vmx file by virt-v2v.

Additional info:

Comment 2 Richard W.M. Jones 2017-04-20 10:46:25 UTC
Yes, I have seen this problem too.

The workaround is to set LIBGUESTFS_BACKEND=direct before conversion.

I believe it's the usual thing related to lack of qemu:///session
support as root in libvirt (bug 890291 / bug 1045069).

Anyway we will have to leave this one open until RHEL 7.5.

Comment 3 Richard W.M. Jones 2019-05-13 09:39:48 UTC
We don't plan to fix this (or the real bug 1045069) in RHEL 7, so I'm
closing this.  This probably does occur on RHEL 8, but the real bug here
is in libvirt, not virt-v2v.

Note You need to log in before you can comment on or make changes to this bug.