Exalogic 188.8.131.52.X, 184.108.40.206.X, 220.127.116.11.X, 18.104.22.168.X: Dom0 SWIOTLB buffer size configuration for X2-2, X3-2, X4-2, X5-2 and X6-2 compute nodes
(Doc ID 1607217.1)
Last updated on MARCH 03, 2020
Applies to:Oracle Exalogic Elastic Cloud Software - Version 22.214.171.124.0 to 126.96.36.199.4
Oracle Exalogic Elastic Cloud Software - Version 188.8.131.52.0 to 184.108.40.206.2
Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.0 to 18.104.22.168.170418
Oracle Exalogic Elastic Cloud Software - Version 22.214.171.124.0 and later
Oracle Virtual Server(x86-64)
This MOS note applies to only Exalogic 126.96.36.199.X, 188.8.131.52.X, 184.108.40.206.X, 220.127.116.11.X Virtual releases. It does not apply to 18.104.22.168.X Virtual release.
X2-2, X3-2, X4-2, and X5-2 Systems in a Virtualized configuration with Compute Node Dom0 memory levels set to 3.5 GB or higher as per the "Document : 1582091.1 - Exalogic Virtual dom0 Memory Recommendations"
An issue has arisen whereby the SWIOTLB buffer, used for Xen PCI passthrough, becomes temporarily exhausted on Compute Nodes running the recommended Dom0 memory layout of 3.5 GB or higher.
The issue manifests itself through vServers that will boot with no IB networking.
Evidence of the issue can be found in the failed vServer logs or be observed on the vServer serial console (through attaching to the vServer serial console using ‘xm console <domain>’)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Confirm the dom0 memory size is 3.5 GB or larger|
|Increase the default SWIOTLB buffer size|
|Validate if swiotlb buffer size change in above step 2 has taken affect|
|Perform the following steps|