Bug 1394774

Summary: SR-IOV setup using wrong kernel parameter
Product: Red Hat OpenStack Reporter: Marko Myllynen <myllynen>
Component: documentationAssignee: Martin Lopes <mlopes>
Status: CLOSED CURRENTRELEASE QA Contact: Deepti Navale <dnavale>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: ekuris, mlopes, myllynen, srevivo, vromanso, yrachman
Target Milestone: ---Keywords: Documentation
Target Release: ---Flags: mlopes: needinfo? (vromanso)
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-03 00:19:30 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:

Description Marko Myllynen 2016-11-14 12:35:20 UTC 
Description of problem:
https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/networking-guide/chapter-20-sr-iov-support-for-virtual-networking states:

Activate Intel VT-d in the kernel by appending the intel_iommu=pt [...]

Upstream document at https://www.kernel.org/doc/Documentation/kernel-parameters.txt recognizes no "pt" value for intel_iommu, only for iommu and in fact when booting a RHEL 7.3 test system with parameters "intel_iommu=on" or "intel_iommu=on iommu=pt" we see the IOMMU groups being created but with no parameters or with intel_iommu=pt this does not happen:

# diff -u intel_iommu=pt intel_iommu=on
...
+DMAR: No ATSR found
+DMAR: dmar0: Using Queued invalidation
+DMAR: dmar1: Using Queued invalidation
+DMAR: Setting RMRR:
+DMAR: Setting identity map for device 0000:00:02.0 [0xad800000 - 0xafffffff]
+DMAR: Setting identity map for device 0000:00:14.0 [0xac127000 - 0xac13dfff]
+DMAR: Prepare 0-16MiB unity mapping for LPC
+DMAR: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
+DMAR: Intel(R) Virtualization Technology for Directed I/O
+iommu: Adding device 0000:00:00.0 to group 0
+iommu: Adding device 0000:00:02.0 to group 1
+iommu: Adding device 0000:00:03.0 to group 2
...

Thanks.
Comment 14 Martin Lopes 2018-08-03 00:19:30 UTC 
This was addressed in a separate BZ, as per the iommu settings defined in the guide: 
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_configuration_guide/