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.
Bug 1275401 - Incorrect description in 17.1.6. PCI passthrough
Summary: Incorrect description in 17.1.6. PCI passthrough
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Virtualization_Deployment_and_Administration_Guide
Version: 7.2
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Herrmann
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-26 19:47 UTC by Alex Williamson
Modified: 2021-02-22 10:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-02 07:39:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alex Williamson 2015-10-26 19:47:24 UTC 
Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Virtualization_Deployment_and_Administration_Guide/chap-Guest_virtual_machine_device_configuration.html#sect-PCI_devices-PCI_passthrough

Section Number and Name: 

17.1.6. PCI passthrough

Describe the issue: 

Regarding the following paragraph:

--
To use VFIO device assignment rather than traditional/legacy KVM device assignment (VFIO is a new method of device assignment that is compatible with UEFI Secure Boot), a <type='hostdev'> interface can have an optional driver sub-element with a name attribute set to "vfio". To use legacy KVM device assignment you can set name to "kvm" (or simply omit the <driver> element, since <driver='kvm'> is currently the default).
--

While the <driver> parameter is valid XML within the <hostdev> for an assigned device, RHEL7 only supports and only enables VFIO based device assignment.  Therefore if the <driver> element is omitted, the default will be to use VFIO, which is also the upstream default.  Using <driver='kvm'/> is not supported and will not work on RHEL7.

Suggestions for improvement: 

I'm not sure there's any value to the paragraph.  There is no release that supports or even enables both legacy KVM device assignment and VFIO.  The default is always the correct value to use, it will result in VFIO on RHEL7 and legacy on RHEL6.  We could further eliminate the <driver> element from the <hostdev> examples as it's just extraneous information for users.

Additional information:
Comment 2 Luiz Capitulino 2015-10-26 20:37:24 UTC 
I had to consult the documentation myself last week and got a bit confused precisely by the paragraph mentioned by Alex. Here's a few suggestions on how to make the documentation clearer:

1. In the introduction in 17.1 be clear that only VFIO is supported and it's used by our tools by default

2. Drop any reference to legacy device assignment from the docs

3. Standardize the terminology on "device assignment" or "passthrough". That is, pick one and drop the other from all sections

4. Maybe 17.1.6 can be dropped altogether? I'm new to this, but I still don't exactly get what it's documenting. Is it an attempt to document SR-IOV? The next section seems to do that too
Comment 3 Alex Williamson 2015-10-26 20:49:22 UTC 
(In reply to Luiz Capitulino from comment #2)
>
> 3. Standardize the terminology on "device assignment" or "passthrough". That
> is, pick one and drop the other from all sections

IMO, PCI device assignment should always use the term "device assignment".  "Passthrough" should be reserved for things like the way we attach USB devices or smartcards to a VM.
Note You need to log in before you can comment on or make changes to this bug.