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:

Installing a new machine remotely with an attached mdev hostdev will fail although virt-manager offers the mdev in customization process.

The customer can't fix this via virt-manager, might also not be aware that the device '$uuid' is the actual mediated device by the selected nodedev, and would have to log into the libvirt host to find out the mdev is not running and start it manually.


Version-Release number of selected component (if applicable):
virt-manager-3.2.0-1.el8.noarch

How reproducible:
100%


Steps to Reproduce:
1. Have a $remote_server with a defined mdev $stopped_mdev that is not running
2. Connect virt-manager to $remote_server
3. Create a new VM (e.g. import image)
4. In Step 4 of 4 select "Customize configuration before install"
5. Select "Add Hardware"
6. Select "MDEV Host Device"
==> $stopped_mdev is listed
7. Add $stopped_mdev and Begin Installation

Actual results:
Error "Unable to install: 'device not found: mediated device '$uuid' not found'"

Expected results:
A) The device is not listed
OR
B) The device is tentatively started
OR
C) There's a way to manage devices on remote host through virt-manager GUI.

Created attachment 1843757 [details]
error screenshot

Created attachment 1843758 [details]
mdev list view

Since Jiri has added the documentation to the release notes and I have opened a bug upstream, I'm going to close this bug for now. 

See https://github.com/virt-manager/virt-manager/issues/392