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 1540535 - Example URI of "Convert from ESXi hypervisor over SSH to local libvirt" is incorrect in v2v man page
Summary: Example URI of "Convert from ESXi hypervisor over SSH to local libvirt" is in...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.5
Hardware: x86_64
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On: 1551055
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-31 10:44 UTC by mxie@redhat.com
Modified: 2018-10-30 07:47 UTC (History)
6 users (show)

Fixed In Version: libguestfs-1.38.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 07:45:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:3021 0 None None None 2018-10-30 07:47:20 UTC

Description mxie@redhat.com 2018-01-31 10:44:00 UTC 
Description of problem:
Example URI of "Convert from ESXi hypervisor over SSH to local libvirt" is incorrect in v2v man page


Version-Release number of selected component (if applicable):
virt-v2v-1.36.10-6.el7.x86_64
libguestfs-1.36.10-6.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Check vmx info in v2v man page,found example URI of "Convert from ESXi hypervisor over SSH to local libvirt" is incorrect 
#man virt-v2v
....
Convert from ESXi hypervisor over SSH to local libvirt
       You have an ESXi hypervisor called "esxi.example.com" with SSH access enabled.  You want to convert from
       VMFS storage on that server to a local file.

        virt-v2v \
          -i vmx -it ssh \
          "root.com/vmfs/volumes/datastore1/guest/guest.vmx" \
          -o local -os /var/tmp

       The guest must not be running.  Virt-v2v would not need to be run as root in this case.

       For more information about converting from VMX files see "INPUT FROM VMWARE VMX" below.
....
2.If missing  "ssh://" in the vmx url when convert guest from VMFS storage by virt-v2v, will pop up below error
# virt-v2v -i vmx -it ssh root.196.89/vmfs/volumes/59b21f90-80cd9f45-9122-30e1715dcab0/esx6.0-rhel7.4-x64-vmware-tools/esx6.0-rhel7.4-x64-vmware-tools.vmx 
[   0.0] Opening the source -i vmx root.196.89/vmfs/volumes/59b21f90-80cd9f45-9122-30e1715dcab0/esx6.0-rhel7.4-x64-vmware-tools/esx6.0-rhel7.4-x64-vmware-tools.vmx
virt-v2v: error: vmx URI remote server name omitted

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

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



Actual results:
Because v2v claims must specify a remote "ssh://..." URI pointing to the VMX file when using the SSH input transport. "ssh://" is missing in the URI example of "Convert from ESXi hypervisor over SSH to local libvirt"  in v2v man page


Expected results:
Add "ssh://"to URI example of "Convert from ESXi hypervisor over SSH to local libvirt" in v2v man page，looks like
             virt-v2v \
            -i vmx -it ssh \
            "ssh://root.com/vmfs/volumes/datastore1/guest/guest.vmx" \
            -o local -os /var/tmp



Additional info:
Comment 2 Pino Toscano 2018-02-07 17:03:29 UTC 
Fixed upstream with
https://github.com/libguestfs/libguestfs/commit/3d4c84185a5098f04e59e6d363b370d4d40e4c13
which is fixed in libguestfs >= 1.37.38.
Comment 4 mxie@redhat.com 2018-06-04 05:51:46 UTC 
Verify the bug with below builds:
virt-v2v-1.38.2-3.el7.x86_64
libguestfs-1.38.2-3.el7.x86_64


Steps:
1.Check vmx info in v2v man page
#man virt-v2v
....
    Convert from ESXi hypervisor over SSH to local libvirt
       You have an ESXi hypervisor called "esxi.example.com" with SSH access
       enabled.  You want to convert from VMFS storage on that server to a
       local file.

        virt-v2v \
          -i vmx -it ssh \
          "ssh://root.com/vmfs/volumes/datastore1/guest/guest.vmx" \
          -o local -os /var/tmp

       The guest must not be running.  Virt-v2v would not need to be run as
       root in this case.

       For more information about converting from VMX files see "INPUT FROM
       VMWARE VMX" below.

....

Result:

  Example URI of "Convert from ESXi hypervisor over SSH to local libvirt"  is correct, so move the bug from ON_QA to VERIFIED
Comment 6 errata-xmlrpc 2018-10-30 07:45:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:3021
Note You need to log in before you can comment on or make changes to this bug.