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.
Description of problem:
customer is trying to import a RHEL 8.2 VM running on VMware to RHV 4.4.
and fails with
"message": "inspection could not detect the source guest (or physical machine).\n\nAssuming 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.\n\nInspection field i_arch was unknown.", "timestamp": "2021-04-13T16:21:48.230425370-05:00", "type": "error" }
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.
Inspection field i_arch was unknown.
Version-Release number of selected component (if applicable):
libguestfs-1.42.0-2.module+el8.3.0+6798+ad6e66be.x86_64
Comment 4Richard W.M. Jones
2021-04-15 07:26:16 UTC
There's no good workaround, but we can provide a hotfix in a few days.
Comment 5Richard W.M. Jones
2021-04-15 08:06:38 UTC
To test this I had to prepare a VM with a split /usr partition, as follows:
$ virt-builder fedora-33
$ virt-tar-out -a fedora-33.img /usr usr.tar
$ rm -f fedora-33-split-usr.img
$ truncate -s 10G fedora-33-split-usr.img
$ virt-resize fedora-33.img fedora-33-split-usr.img
Set up the separate /usr inside the new disk image:
$ guestfish -a fedora-33-split-usr.img -i
><fs> rm-rf /usr
><fs> mkfs xfs /dev/sda4
><fs> mkdir /usr
><fs> mount /dev/sda4 /usr
><fs> tar-in usr.tar /usr xattrs:true selinux:true acls:true
><fs> vi /etc/fstab
Add the following line at the end of /etc/fstab:
/dev/sda4 /usr xfs defaults 0 0
><fs> exit
Verify the split /usr partition configuration is detected:
$ guestfish --ro -a fedora-33-split-usr.img -i
/dev/sda3 mounted on /
/dev/sda2 mounted on /boot
/dev/sda4 mounted on /usr <--- note
><fs> exit
However if you run virt-inspector on the new image you will see there
is no <arch> entry and inspection is incomplete:
$ virt-inspector -a fedora-33-split-usr.img --no-applications
Also virt-v2v fails. The error message is slightly different, but the
root cause is the same thing:
$ virt-v2v -i disk fedora-33-split-usr.img -o null
virt-v2v: error: inspection could not detect the source guest (or physical
machine).
...
Inspection field ‘i_distro’ was ‘unknown’.