My Oracle Support Banner

Exalogic 2.0.6.0.X, 2.0.6.1.X, 2.0.6.2.X, 2.0.6.3.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 2.0.6.0.0 to 2.0.6.2.4
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.1.0 to 2.0.6.1.2
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.0 to 2.0.6.2.170418
Oracle Exalogic Elastic Cloud Software - Version 2.0.6.3.0 and later
Linux x86-64
Oracle Virtual Server(x86-64)

This MOS note applies to only Exalogic 2.0.6.0.X, 2.0.6.1.X, 2.0.6.2.X, 2.0.6.3.X Virtual releases. It does not apply to 2.0.6.4.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"



Symptoms

 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>’)

Cause

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
Symptoms
Cause
Solution
 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
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.