Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Descriptionmxie@redhat.com
2022-03-31 11:23:12 UTC
Description of problem:
Virt-v2v can't convert guest when os is installed on nvme disk via vmx+ssh
Version-Release number of selected component (if applicable):
virt-v2v-2.0.1-1.el9.x86_64
libguestfs-1.48.0-2.el9.x86_64
guestfs-tools-1.48.0-1.el9.x86_64
libvirt-libs-8.1.0-1.el9.x86_64
qemu-img-6.2.0-12.el9.x86_64
nbdkit-server-1.30.1-2.el9.x86_64
libnbd-1.12.2-1.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Prepare a VMware guest and its os is installed on nvme disk, convert it from VMware via vmx+ssh by v2v
# virt-v2v -i vmx -it ssh ssh://root.75.219/vmfs/volumes/esx6.7-function/esx6.7-rhel8.6-nvme-disk/esx6.7-rhel8.6-nvme-disk.vmx -ip /home/esxpw
[ 0.0] Setting up the source: -i vmx ssh://root.75.219/vmfs/volumes/esx6.7-function/esx6.7-rhel8.6-nvme-disk/esx6.7-rhel8.6-nvme-disk.vmx
(root.75.219) Password:
[ 3.8] Opening the source
[ 9.8] Inspecting the source
virt-v2v: error: inspection could not detect the source guest (or physical
machine).
Assuming that you are running virt-v2v/virt-p2v on a source which is
supported (and not, for example, a blank disk), then this should not
happen.
No root device found in this operating system image.
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 can convert guest when os is installed on nvme disk via vmx+ssh
Additional info:
Virt-v2v can convert guest when os is installed on nvme disk via ova
# virt-v2v -i ova /home/esx6_7-rhel8.6-nvme-disk -o rhv-upload -of qcow2 -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data -b ovirtmgmt -oo rhv-cafile=/home/ca.pem -oo rhv-verifypeer
[ 0.0] Setting up the source: -i ova /home/esx6_7-rhel8.6-nvme-disk
virt-v2v: warning: making OVA directory public readable to work around
libvirt bug https://bugzilla.redhat.com/1045069
[ 1.1] Opening the source
[ 5.3] Inspecting the source
[ 11.0] Checking for sufficient free disk space in the guest
[ 11.0] Converting Red Hat Enterprise Linux 8.6 Beta (Ootpa) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 96.7] Mapping filesystem data to avoid copying unused and blank areas
[ 98.0] Closing the overlay
[ 98.3] Assigning disks to buses
[ 98.3] Checking if the guest needs BIOS or UEFI to boot
[ 98.3] Setting up the destination: -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -os nfs_data
[ 117.8] Copying disk 1/1
█ 100% [****************************************]
[ 374.7] Creating output metadata
[ 384.1] Finishing off
Comment 2Richard W.M. Jones
2022-04-04 15:16:35 UTC
Verified with the versions.
virt-v2v-2.0.3-1.el9.x86_64
libguestfs-1.48.1-1.el9.x86_64
Step:
convert guest when os is installed on nvme disk via vmx+ssh.
# virt-v2v -i vmx -it ssh ssh://root.75.219/vmfs/volumes/esx6.7-function/esx6.7-rhel8.6-nvme-disk/esx6.7-rhel8.6-nvme-disk.vmx -ip /v2v-ops/esx_data_pwd
[ 0.0] Setting up the source: -i vmx ssh://root.75.219/vmfs/volumes/esx6.7-function/esx6.7-rhel8.6-nvme-disk/esx6.7-rhel8.6-nvme-disk.vmx
(root.75.219) Password:
(root.75.219) Password:
[ 7.2] Opening the source
[ 11.6] Inspecting the source
[ 20.8] Checking for sufficient free disk space in the guest
[ 20.8] Converting Red Hat Enterprise Linux 8.6 Beta (Ootpa) to run on KVM
virt-v2v: This guest has virtio drivers installed.
[ 114.0] Mapping filesystem data to avoid copying unused and blank areas
[ 115.1] Closing the overlay
[ 115.2] Assigning disks to buses
[ 115.2] Checking if the guest needs BIOS or UEFI to boot
[ 115.2] Setting up the destination: -o libvirt
[ 117.4] Copying disk 1/1
█ 100% [****************************************]
[ 222.6] Creating output metadata
[ 222.7] Finishing off
Moving to verified.
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 (Low: virt-v2v security, bug fix, and enhancement update), 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/RHSA-2022:7968