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:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/96/html/V2V_Guide/Converting-a-vm.html

3.2.1.1. Preparing to convert a virtual machine running Linux
Example 3.1. Missing Package error

virt-v2v: Installation failed because the following files referenced in the configuration file are required, but missing:
rhel/6/kernel-2.6.32-128.el6.x86_64.rpm
rhel/6/ecryptfs-utils-82-6.el6.x86_64.rpm
rhel/6/ecryptfs-utils-82-6.el6.i686.rpm


To obtain the relevant RPMs for your environment, repeat these steps for each missing package:

   1.Login to Red Hat Network
   2.Select the Package Search tab.
   3.In the Search For field, type the package name exactly matching the one shown in the error message. For the example shown in Example 2.1, “Missing Package error”, the first package is kernel-2.6.32-128.el6.x86_64

The above link "Example 2.1,"Missing Package error" " should link to "Example 3.1. Missing Package error".
This part belong to 3.2.1.1,and the picture is above.

Additional info:
Set Priority/Severity to high/high and raise the blocker flag, as it's better
to fix this doc bug in rhel-6.1.0.

Updated in 

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/96/html/V2V_Guide/Converting-a-vm.html

"c. In the Search For field, type the package name exactly matching the one shown in the error message. For the example shown in Example 3.1, “Missing Package error”, the first package is kernel-2.6.32-128.el6.x86_64"

Verified this issue:
In the Search For field, type the package name exactly matching the one shown in the error message. For the example shown in Example 3.1, “Missing Package error”, the first package is kernel-2.6.32-128.el6.x86_64

The link changed to 3.1,so change the status to VERIFIED