Bug 1201503

Summary: [DOC]kernel parameter should be iommu=pt instead of iommu=on for KVM device assignment
Product: Red Hat Enterprise Linux 7 Reporter: Andrew Theurer <atheurer>
Component: doc-Virtualization_Deployment_and_Administration_GuideAssignee: Platform Virt Docs <virt-docs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.1CC: atheurer, jherrman, lnovich
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-20 08:40:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1286552    

Description Andrew Theurer 2015-03-12 20:23:08 UTC
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/chap-Guest_virtual_machine_device_configuration.html#sect-Guest_virtual_machine_device_configuration-PCI_devices

Section Number and Name: 20.1

Describe the issue: 

When preparing RHEL for PCI device assignment (for a KVM VM), IOMMU feature is required.  Currently, the document instructs to use "iommu-on".  This does work, but it can have significant performance side affects.  "iommu=on" enables IOMMU for all devices, even if they are not used for device assignment by KVM.  When using IOMMU for devices in the host, extra overhead is introduced for each DMA operation.  This can reduce performance of some IO adapters like 10Gb networking significantly.

Suggestions for improvement: 

The most appropriate option to use for device assignment is "iommu=pt".  The enables the IOMMU only for device assignment, which is exactly what is needed.

Additional information: 

If we want to document the use for "iommu=on" then it should be in another area, as the use case for that option is not actually for device assignment.  It is to provide protection to the host from a malfunctioning device driver [in the host].

Comment 10 Laura Novich 2015-12-20 08:40:34 UTC
Published on December 17 version 2-24

Comment 11 Laura Novich 2015-12-20 08:43:16 UTC
Published on December 17 version 2-24