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.

Bug 2166565

Summary: Remove option '-oo qemu-boot' info from v2v man page
Product: Red Hat Enterprise Linux 9 Reporter: mxie <mxie>
Component: virt-v2vAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: mxie <mxie>
Severity: low Docs Contact:
Priority: low    
Version: 9.2CC: chhu, hongzliu, juzhou, lersek, rjones, tyan, tzheng, vwu, xiaodwan
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-v2v-2.2.0-5.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 07:45:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mxie@redhat.com 2023-02-02 07:46:32 UTC
Description of problem:
Remove option '-oo qemu-boot' info from v2v man page 
 
Version-Release number of selected component (if applicable):
virt-v2v-2.2.0-3.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Check v2v man page about qemu-boot option
# man virt-v2v |grep qemu-boot -A 1
       -oo qemu-boot
           When using -o qemu only, this boots the guest immediately after virt-v2v finishes.

2.Convert a guest from VMware by v2v and add option '-oo qemu-boot' in command line
# virt-v2v -ic esx://root.212.36/?no_verify=1  -it vddk -io vddk-libdir=/home/vddk8.0.0 -io vddk-thumbprint=11:97:52:B3:B6:5D:C4:DD:05:D9:D0:43:31:0E:98:CB:73:6E:D6:45  -ip /home/esxpwd rocky9 -o qemu -oo qemu-boot
[   0.0] Setting up the source: -i libvirt -ic esx://root.212.36/?no_verify=1 -it vddk rocky9
virt-v2v: error: -o qemu: the -oo qemu-boot option cannot be used in RHEL

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

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


Actual results:
option '-oo qemu-boot' is shown in v2v man page 

Expected results:
Remove option '-oo qemu-boot' info from v2v man page 

Additional info:

Comment 1 mxie@redhat.com 2023-02-07 06:23:35 UTC
Test the bug with virt-v2v-2.2.0-5.el9.x86_64

Steps:
1.Check v2v man page about qemu-boot option
# man virt-v2v |grep qemu-boot -A 1
nothing

Result: the bug has been fixed

Comment 4 mxie@redhat.com 2023-02-09 06:06:00 UTC
Move the bug to verified status according to comment1

Comment 6 errata-xmlrpc 2023-05-09 07:45:48 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 (virt-v2v 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/RHBA-2023:2313