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:
Assigning a physical PCI device to a KVM guest has many subtle details which can easily go wrong for a user/admin.  Thus, adding a troubleshooting section to chapter 12 would be prudent.

So, here goes a recommended ToC:
  12.4 Troubleshooting Device Assignment
      .1 Multi-function devices (MFDs)
         .1 Security implications
         .2 hot-add versus static assignment
      .2 ACS Checking
      .3 PCI assignment (B:D.F) in guest
      .4 Potential driver issues
         .1 function-dependent addressing in MFDs
         .2 reset handling
      .5 How libvirt performs device assignment
         .1 PCI B:D.F assignment in guest
         .2 binding a device to pci-stub
         .3 reset-ing a PCI(e) device
         .4 binding device back to host 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

To add to list:
Limitations of hot-add of PCI device(s)
  -- limit of 8

Alex,

I believe that you are the best person to own the device assignment troubleshooting guide. It is mostly between you and ddd.

Thanks, Ronen.

Closing EOL, since this bug was opened years ago. If anyone still wants this content, feel free to re-open the bug or create a new one.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days