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:
legacy KVM device assignment is deprecated.  Support only vfio-based device assignment going forward.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

I got this from Markus: "As far as I know, the plan is to disable legacy KVM device in the *kernel*, and then close this bug without patching qemu-kvm."

Alex: is that your understanding as well?

(In reply to Ademar de Souza Reis Jr. from comment #2)
> I got this from Markus: "As far as I know, the plan is to disable legacy KVM
> device in the *kernel*, and then close this bug without patching qemu-kvm."
> 
> Alex: is that your understanding as well?

Yes, pci-assign should fail gracefully in qemu when it's disabled in the kernel.  libvirt should also favor vfio when configuring a guest, so the only way a user would be exposed to it is to manually configure their guest xml for pci-assign.  We would only need to patch qemu if exposing the pci-assign driver but not having it work is somehow unacceptable.

*** This bug has been marked as a duplicate of bug 1025880 ***