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:
This is downstream report for upstream issue https://github.com/virt-manager/virt-manager/issues/318

There's a misleading error message that might have the customer research for a while while this might be a user documentation gap, too.

Version-Release number of selected component (if applicable):
virt-install-3.2.0-9.el9.noarch

How reproducible:
100%

Steps to Reproduce:
1. Start machine installation with a hostdev whose nodedev is not available,
 - minimally, execute: virt-install --hostdev whatever,address.type=pci

Actual results:
ERROR    Error: --hostdev anything: Unknown address type

... and the user might start investigating why address.type=pci might be wrong...

Expected results:
ERROR    Error: --hostdev anything: 'anything' is not a valid device reference.

Additional notes:
Junqin reproduced this for RHEL9 and also on RHEL8 - virt-install-2.2.1-4.el8.noarch

Pre-verify with virt-manager-3.2.0-13.el9.noarch

Step 1:
Use virt-install with an invalid hostdev address,
# virt-install --hostdev just_an_string
ERROR    Error: --hostdev just_an_string: Unknown hostdev address string format 'just_an_string'

On the error message, we can clearly get the reason why installation failed, This bug has pre-verified.

Reproduce with virt-install-3.2.0-9.el9.noarch

Error message is the same with Comment 0.

Verify with follow packages:

virt-install-3.2.0-13.el9.noarch
virt-manager-3.2.0-13.el9.noarch

Step 1:

Run virt-install with an invalid hostdev address

# virt-install --hostdev just_an_address,address.type=pci
ERROR    Error: --hostdev just_an_address,address.type=pci: Unknown hostdev address string format 'just_an_address'

Expect result: the error message can clearly point out the cause of fail

Actuall result: meet the expect. So I changer the status to verified, Thanks.

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 (new packages: virt-manager), 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-2022:2515