Bug 2026985 - [virt-manager] vm installation fails when adding mdev hostdev
Summary: [virt-manager] vm installation fails when adding mdev hostdev
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-manager
Version: 8.6
Hardware: All
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jonathon Jongsma
QA Contact: Virtualization Bugs
Jiri Herrmann
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-26 18:07 UTC by smitterl
Modified: 2023-01-30 13:31 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.Attaching mediated devices to virtual machines in `virt-manager` in some cases fails The `virt-manager` application is currently able to detect mediated devices, but cannot recognize whether the device is active. As a consequence, attempting to attach an inactive mediated device to a running virtual machine (VM) using `virt-manager` fails. Similarly, attempting to create a new VM that uses an inactive mediated device fails with a `device not found` error. To work around this issue, use the `virsh nodedev-start` or `mdevctl start` commands to activate the mediated device before using it in `virt-manager`.
Clone Of:
Last Closed: 2022-04-28 18:33:16 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
error screenshot (92.42 KB, image/png)
2021-11-26 18:09 UTC, smitterl
no flags Details
mdev list view (118.47 KB, image/png)
2021-11-26 18:10 UTC, smitterl
no flags Details

System ID Private Priority Status Summary Last Updated
Github virt-manager virt-manager issues 392 0 None open vm installation fails when adding inactive mdev 2022-04-28 18:33:16 UTC
Red Hat Bugzilla 1995125 1 None None None 2022-05-10 14:59:14 UTC
Red Hat Issue Tracker RHELPLAN-104057 0 None None None 2021-11-26 18:07:39 UTC

Description smitterl 2021-11-26 18:07:14 UTC
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):

How reproducible:

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
B) The device is tentatively started
C) There's a way to manage devices on remote host through virt-manager GUI.

Comment 1 smitterl 2021-11-26 18:09:51 UTC
Created attachment 1843757 [details]
error screenshot

Comment 2 smitterl 2021-11-26 18:10:31 UTC
Created attachment 1843758 [details]
mdev list view

Comment 11 Jonathon Jongsma 2022-04-28 18:33:16 UTC
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

Note You need to log in before you can comment on or make changes to this bug.