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.
DescriptionAlex Williamson
2020-11-30 23:02:44 UTC
Description of problem:
The 0.78 release of mdevctl is moving to stable in Fedora, we're currently two upstream releases behind in RHEL8 (0.61). It seems like we should update it for 8.4.
Version-Release number of selected component (if applicable):
mdevctl-0.61-3.el8
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Danilo, as the first update to this package since it was added, how would you like to go about rebasing it? Patches, or maintainer rebase, or something else?
Since we still don't have drm & vfio backport available yet, tests are targeted at mdevctl pkg only.
packages used:
qemu-kvm-4.2.0-37.module+el8.4.0+8837+c89bcfe6.x86_64
4.18.0-259.el8.x86_64
mdevctl-0.78-1.el8.noarch
devices tested:
Intel Corporation HD Graphics P530
Tesla V100 SXM2
quadro RTX6000
Tesla M10
Scenarios tested:
mdevctl-test-query-mdev-parent-devices
mdevctl-create-remove-mdev
mdevctl-persistent-mdev-over-host-reboot
mdevctl-reattach-mdev-parent-devices-10-times(for quadro RTX6000 only)
Job links:
https://beaker.engineering.redhat.com/jobs/4800193 for intel HD p530
https://beaker.engineering.redhat.com/jobs/4800174 for Tesla V100 SXM2
https://beaker.engineering.redhat.com/jobs/4800172 for quadro rtx6000
https://beaker.engineering.redhat.com/jobs/4800034 for tesla m10
I don't find any fails related with mdevctl during testing
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-2021:1866