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:
Unknown error reported when creating mdev device with the same uuid twice

Version-Release number of selected component (if applicable):
libvirt-7.8.0-1.module+el8.6.0+12982+5e169f40.x86_64

How reproducible:
100%

Steps to Reproduce:
1.#virsh nodedev-create mdev-2.xml                                             
Node device mdev_39be1f71_9b55_462a_a3d0_3db3d0f6c215_0000_41_00_0 created from mdev-2.xml

2.#virsh nodedev-create mdev-2.xml
error: Failed to create node device from mdev-2.xml
error: internal error: Unable to start mediated device: Unknown error

3.

Actual results:


Expected results:
Should report more clear error, such as:
Failed to create mdev_39be1f71_9b55_462a_a3d0_3db3d0f6c215_0000_41_00_0
error: Requested operation is not valid: Device is already active

Additional info:

Jonathon, please have a look. Thanks.

This is a result of the old version of mdevctl not returning an error message in this particular situation. The new version of mdevctl should return the error message "Device already exists". This should be fixed with the rebase to mdevctl 1.1.0

Pre-verified (sanity)

# virsh nodedev-define vfio_ccw_nodedev.xml 
error: Failed to define node device from 'vfio_ccw_nodedev.xml'
error: internal error: Unable to define mediated device: Error: Cowardly refusing to overwrite existing config for 0.0.27aa/8d312cf6-f92a-485c-8db8-ba9299848f46

Setting ITM to 22 according to rebase BZ (s. Depends On)

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 (mdevctl 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-2022:1922