Jump to content
SUSE Linux Enterprise Server 12 SP4

Release Notes

This document provides guidance and an overview to high level general features and updates for SUSE Linux Enterprise Server 12 SP4. Besides architecture or product-specific information, it also describes the capabilities and limitations of SUSE Linux Enterprise Server 12 SP4.

General documentation can be found at: https://documentation.suse.com/sles/12-SP4/.

Publication Date: 2021-12-09, Version: 12.4.20211208
1 About the Release Notes
2 SUSE Linux Enterprise Server
2.1 Interoperability and Hardware Support
2.2 Support and Life Cycle
2.3 What Is New?
2.4 Documentation and Other Information
2.5 How to Obtain Source Code
2.6 Support Statement for SUSE Linux Enterprise Server
2.7 General Support
2.8 Software Requiring Specific Contracts
2.9 Technology Previews
2.10 Modules, Extensions, and Related Products
2.11 Security, Standards, and Certification
3 Installation and Upgrade
3.1 Upgrade-Related Notes
3.2 For More Information
4 Architecture Independent Information
4.1 Development
4.2 Kernel
4.3 Security
4.4 Networking
4.5 Systems Management
4.6 Storage
5 AMD64/Intel 64 (x86_64) Specific Information
5.1 Support for AMD Memory Encryption
5.2 System and Vendor Specific Information
6 POWER (ppc64le) Specific Information
6.1 Support for ibmvnic Networking Driver
6.2 Reduced Memory Usage When Booting FADump Capture Kernel
6.3 SDT Markers in Select Applications and Libraries
6.4 Support for POWER9 PMU Events Has Been Added to the perf Tool
6.5 Support for POWER9 24x7 Counters Has Been Added
6.6 OProfile Support for POWER9
6.7 Support for POWER9 Has Been Added to LibPFM
6.8 Support for POWER9 Has Been Added to PAPI
6.9 Speed of ibmveth Interface Not Reported Accurately
7 IBM Z (s390x) Specific Information
7.1 Hardware
7.2 Virtualization
7.3 Network
7.4 Security
7.5 Reliability, Availability, Serviceability (RAS)
7.6 Performance
7.7 Miscellaneous
8 ARM 64-Bit (AArch64) Specific Information
8.1 Boot and Driver Enablement for Raspberry Pi
8.2 Toolchain Module Enabled in Default Installation
9 Packages and Functionality Changes
9.1 Updated Packages
9.2 Removed and Deprecated Functionality
9.3 Changes in Packaging and Delivery
10 Technical Information
10.1 Kernel Limits
10.2 KVM Limits
10.3 Xen Limits
10.4 File Systems
10.5 Supported Java Versions
11 Legal Notices

1 About the Release Notes

These Release Notes are identical across all architectures, and the most recent version is always available online at http://www.suse.com/releasenotes/.

Some entries may be listed twice, if they are important and belong to more than one section.

Release notes usually only list changes that happened between two subsequent releases. Certain important entries from the release notes documents of previous product versions are repeated. To make these entries easier to identify, they contain a note to that effect.

However, repeated entries are provided as a courtesy only. Therefore, if you are skipping one or more service packs, check the release notes of the skipped service packs as well. If you are only reading the release notes of the current release, you could miss important changes.

2 SUSE Linux Enterprise Server

SUSE Linux Enterprise Server is a highly reliable, scalable, and secure server operating system, built to power mission-critical workloads in both physical and virtual environments. It is an affordable, interoperable, and manageable open source foundation. With it, enterprises can cost-effectively deliver core business services, enable secure networks, and simplify the management of their heterogeneous IT infrastructure, maximizing efficiency and value.

The only enterprise Linux recommended by Microsoft and SAP, SUSE Linux Enterprise Server is optimized to deliver high-performance mission-critical services, as well as edge of network, and web infrastructure workloads.

2.1 Interoperability and Hardware Support

Designed for interoperability, SUSE Linux Enterprise Server integrates into classical Unix as well as Windows environments, supports open standard interfaces for systems management, and has been certified for IPv6 compatibility.

This modular, general purpose operating system runs on four processor architectures and is available with optional extensions that provide advanced capabilities for tasks such as real time computing and high availability clustering.

SUSE Linux Enterprise Server is optimized to run as a high performing guest on leading hypervisors and supports an unlimited number of virtual machines per physical system with a single subscription, making it the perfect guest operating system for virtual computing.

2.2 Support and Life Cycle

SUSE Linux Enterprise Server is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.

SUSE Linux Enterprise Server 12 has a 13-year life cycle, with 10 years of General Support and 3 years of Extended Support. The current version (SP4) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise Server 12 SP5.

If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support you get an additional 12 to 36 months in twelve month increments, providing a total of 3 to 5 years of support on any given service pack.

For more information, check our Support Policy page https://www.suse.com/support/policy.html or the Long Term Service Pack Support Page https://www.suse.com/support/programs/long-term-service-pack-support.html.

2.3 What Is New?

SUSE Linux Enterprise Server 12 introduces many innovative changes compared to SUSE Linux Enterprise Server 11. Here are some of the highlights:

  • Robustness on administrative errors and improved management capabilities with full system rollback based on Btrfs as the default file system for the operating system partition and the Snapper technology of SUSE.

  • An overhaul of the installer introduces a new workflow that allows you to register your system and receive all available maintenance updates as part of the installation.

  • SUSE Linux Enterprise Server Modules offer a choice of supplemental packages, ranging from tools for Web Development and Scripting, through a Cloud Management module, all the way to a sneak preview of upcoming management tooling called Advanced Systems Management. Modules are part of your SUSE Linux Enterprise Server subscription, are technically delivered as online repositories, and differ from the base of SUSE Linux Enterprise Server only by their life cycle. For more information about modules, see Section 2.10.1, “Available Modules”.

  • New core technologies like systemd (replacing the time-honored System V-based init process) and Wicked (introducing a modern, dynamic network configuration infrastructure).

  • The open-source database system MariaDB is fully supported now.

  • Support for open-vm-tools together with VMware for better integration into VMware-based hypervisor environments.

  • Linux Containers are integrated into the virtualization management infrastructure (libvirt). Docker is provided as a fully supported technology. For more details, see https://www.suse.com/promo/sle/docker/.

  • Support for the AArch64 architecture (64-bit ARMv8) and the 64-bit Little-Endian variant of the IBM POWER architecture. Additionally, we continue to support the Intel 64/AMD64 and IBM Z architectures.

  • GNOME 3.20 gives users a modern desktop environment with a choice of several different look and feel options, including a special SUSE Linux Enterprise Classic mode for easier migration from earlier SUSE Linux Enterprise Desktop environments.

  • For users wishing to use the full range of productivity applications of a Desktop with their SUSE Linux Enterprise Server, we are now offering SUSE Linux Enterprise Workstation Extension (requires a SUSE Linux Enterprise Desktop subscription).

  • Integration with the new SUSE Customer Center, the new central web portal from SUSE to manage Subscriptions, Entitlements, and provide access to Support.

If you are upgrading from a previous SUSE Linux Enterprise Server release, you should review at least the following sections:

2.3.1 NV-DIMM Support

SLES 12-SP4 / SLES15 supports persistent memory (NV-DIMM) technologies, such as Intel AEP, on certified hardware and for certified ISV applications, specifically in memory databases, in cooperation with SUSE's hardware and software partners.

2.4 Documentation and Other Information

2.4.1 Available on the Product Media

  • Read the READMEs on the media.

  • Get the detailed change log information about a particular package from the RPM (where <FILENAME>.rpm is the name of the RPM):

    rpm --changelog -qp <FILENAME>.rpm
  • Check the ChangeLog file in the top level of the media for a chronological log of all changes made to the updated packages.

  • Find more information in the docu directory of the media of SUSE Linux Enterprise Server 12 SP4. This directory includes PDF versions of the SUSE Linux Enterprise Server 12 SP4 Installation Quick Start and Deployment Guides. Documentation (if installed) is available below the /usr/share/doc/ directory of an installed system.

2.4.2 Externally Provided Documentation

2.5 How to Obtain Source Code

This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires SUSE to provide the source code that corresponds to the GPL-licensed material. The source code is available for download at http://www.suse.com/download-linux/source-code.html. Also, for up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Requests should be sent by e-mail to mailto:sle_source_request@suse.com or as otherwise instructed at http://www.suse.com/download-linux/source-code.html. SUSE may charge a reasonable fee to recover distribution costs.

2.6 Support Statement for SUSE Linux Enterprise Server

To receive support, you need an appropriate subscription with SUSE. For more information, see http://www.suse.com/products/server/services-and-support/.

The following definitions apply:


Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.


Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or alternatively prepare for Level 3.


Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.

For contracted customers and partners, SUSE Linux Enterprise Server 12 SP4 and its Modules are delivered with L3 support for all packages, except the following:

SUSE will only support the usage of original (that is, unchanged and un-recompiled) packages.

2.7 General Support

To learn about supported kernel, virtualization, and file system features, as well as supported Java versions, see Section 10, “Technical Information”.

2.8 Software Requiring Specific Contracts

The following packages require additional support contracts to be obtained by the customer in order to receive full support:

  • PostgreSQL Database

  • LibreOffice

2.9 Technology Previews

Technology previews are packages, stacks, or features delivered by SUSE which are not supported. They may be functionally incomplete, unstable or in other ways not suitable for production use. They are included for your convenience and give you a chance to test new technologies within an enterprise environment.

Whether a technology preview becomes a fully supported technology later depends on customer and market feedback. Technology previews can be dropped at any time and SUSE does not commit to providing a supported version of such technologies in the future.

Give your SUSE representative feedback, including your experience and use case.

2.9.1 Technology Previews for AMD64/Intel 64 64-Bit (x86_64) KVM Nested Virtualization

KVM Nested Virtualization is available in SLE 12 SP4 as a technology preview. For more information, see the Linux kernel documentation (https://www.kernel.org/doc/html/latest/virt/kvm/nested-vmx.html). Support for AMD Secure Encrypted Virtualization

As a technology preview, SLE 12 SP4 now supports AMD Secure Encrypted Virtualization (SEV). SEV integrates main memory encryption capabilities (SME) with the existing AMD-V virtualization architecture to support encrypted virtual machines. Encrypting virtual machines helps protect them from physical threats and other virtual machines or even the hypervisor itself. SEV represents a new approach to security that is particularly suited to cloud computing where virtual machines need not fully trust the hypervisor and administrator of their host system. As with SME, no application software modifications are required to support SEV.

See also Section 5.1, “Support for AMD Memory Encryption” .

2.10 Modules, Extensions, and Related Products

This section comprises information about modules and extensions for SUSE Linux Enterprise Server 12 SP4. Modules and extensions add parts or functionality to the system.

2.10.1 Available Modules

Modules are fully supported parts of SUSE Linux Enterprise Server with a different life cycle and update timeline. They are a set of packages, have a clearly defined scope and are delivered via an online channel only. Release notes for modules are contained in this document.

The following modules are available for SUSE Linux Enterprise Server 12 SP4:

NameContentLife Cycle
Advanced Systems Management ModuleCFEngine, Puppet, Salt and the Machinery toolFrequent releases
Containers ModuleDocker, tools, prepackaged imagesFrequent releases
HPC ModuleTools and libraries related to High Performance Computing (HPC)Frequent releases
Legacy Module* ksh No updates, supported through March 2022
Public Cloud ModulePublic cloud initialization code and toolsFrequent releases
SUSE Cloud Application Platform ToolsTools to interact with the SUSE Cloud Application Platform 1.0 Frequent releases
Toolchain ModuleGNU Compiler Collection (GCC)Yearly delivery
Web and Scripting ModulePHP, Python, Ruby on Rails3 years, ~18 months overlap

* Module is not available for the AArch64 architecture.

For more information about the life cycle of packages contained in modules, see https://scc.suse.com/docs/lifecycle/sle/12/modules.

2.10.2 Available Extensions

Extensions add extra functionality to the system and require their own registration key, usually at additional cost. Extensions are delivered via an online channel or physical media. In many cases, extensions have their own release notes documents that are available from https://www.suse.com/releasenotes/.

The following extensions are available for SUSE Linux Enterprise Server 12 SP4:

Additionally, there are the following extensions which are not covered by SUSE support agreements, available at no additional cost and without an extra registration key:

2.10.3 Derived and Related Products

This sections lists derived and related products. In many cases, these products have their own release notes documents that are available from https://www.suse.com/releasenotes/.

2.11 Security, Standards, and Certification

SUSE Linux Enterprise Server 12 SP4 has been submitted to the certification bodies for:

For more information about certification, see https://www.suse.com/security/certificates.html.

3 Installation and Upgrade

SUSE Linux Enterprise Server can be deployed in several ways:

  • Physical machine

  • Virtual host

  • Virtual machine

  • System containers

  • Application containers

3.1 Upgrade-Related Notes

This section includes upgrade-related information for SUSE Linux Enterprise Server 12 SP4. For information about general preparations and supported upgrade methods and paths, see the documentation at https://documentation.suse.com/sles/12-SP4/html/SLES-all/cha-update-sle.html.

3.1.1 Upgrading to PostgreSQL 10

If you are using PostgreSQL, make sure to upgrade to PostgreSQL 10 before upgrading to SLES 12 SP4. For more information, see Section 9.1.5, “PostgreSQL Has Been Upgraded to Version 10” .

3.1.2 Product Registration Changes for HPC Customers

For SUSE Linux Enterprise 12, there was a High Performance Computing subscription named "SUSE Linux Enterprise Server for HPC" (SLES for HPC). With SLE 15, this subscription does not exist anymore and has been replaced. The equivalent subscription is named "SUSE Linux Enterprise High Performance Computing" (SLE-HPC) and requires a different license key. Because of this requirement, a SLES for HPC 12 system will by default upgrade to a regular "SUSE Linux Enterprise Server".

To properly upgrade a SLES for HPC system to a SLE-HPC, the system needs to be converted to SLE-HPC first. SUSE provides a tool to simplify this conversion by performing the product conversion and switch to the SLE-HPC subscription. However, the tool does not perform the upgrade itself.

When run without extra parameters, the script assumes that the SLES for HPC subscription is valid and not expired. If the subscription has expired, you need to provide a valid registration key for SLE-HPC.

The script reads the current set of registered modules and extensions and after the system has been converted to SLE-HPC, it tries to add them again.

Important: Providing a Registration Key to the Conversion Script

The script cannot restore the previous registration state if the supplied registration key is incorrect or invalid.

  1. To install the script, run zypper in switch_sles_sle-hpc.

  2. Execute the script from the command line as root:

    switch_sles_sle-hpc -e <REGISTRATION_EMAIL> -r <NEW_REGISTRATION_KEY>

    The parameters -e and -r are only required if the previous registration has expired, otherwise they are optional. To run the script in batch mode, add the option -y. It answers all questions with yes.

For more information, see the man page switch_sles_sle-hpc(8) and README.SUSE.

3.2 For More Information

For more information, see Section 4, “Architecture Independent Information” and the sections relating to your respective hardware architecture.

4 Architecture Independent Information

Information in this section pertains to all architectures supported by SUSE Linux Enterprise Server 12 SP4.

4.1 Development

4.1.1 librdkafka Has Been Added

librdkafka version 0.11.6 has been added. librdkafka is a C library implementation of the Apache Kafka protocol, providing Producer, Consumer and Admin clients. It was designed with message delivery reliability and high performance in mind. For more information, see https://github.com/edenhill/librdkafka.

4.2 Kernel

4.2.1 Unprivileged eBPF usage has been disabled

A large amount of security issues was found and fixed in the Extended Berkeley Packet Filter (eBPF) code. To reduce the attack surface, its usage has been restricted to privileged users only.

Privileged users include root. Programs with the CAP_BPF capability in the newer versions of the Linux kernel can still use eBPF as-is.

To check the privileged state, you can check the value of the /proc/sys/kernel/unprivileged_bpf_disabled parameter. Value of 0 means "unprivileged enable", and value of 2 means "only privileged users enabled".

This setting can be changed by the root user:

  • to enable it temporarily for all users by running the command sysctl kernel.unprivileged_bpf_disabled=0

  • to enable it permanently by adding kernel.unprivileged_bpf_disabled=0 to the /etc/sysctl.conf file.

4.2.2 Support for SAP HANA Workloads on Intel Optane DC Memory

SUSE Linux Enterprise Server 12 SP4 and SUSE Linux Enterprise Server for SAP Applications 12 SP4 add support for Intel Optane DC memory. This enables SAP workloads, such as SAP HANA to benefit from persistent memory in the future to shorten start times of the system and provide better overall system stability. Currently, configurations up to 12 TB of NVDIMMs plus 3 TB of regular DIMMS of supported memory and 4 socket machines have been tested. Additional configurations will be tested over time.

From a file system perspective, the XFS file system is supported for the NVDIMMs, with SAP HANA running in DAX mode. SUSE intends to keep the leading position as technology provider, working closely with SAP on future developments.

If there are pmem namespaces, these need to be destroyed before the installation. To mount persistent memory directly on boot, we recommend adding the nofail mount option in /etc/fstab as it can take a long time for the /dev/pmem devices to become usable.

For example:

/dev/pmem0    /mnt/pmem0    xfs    dax,nofail    0  0
/dev/pmem1    /mnt/pmem1    xfs    dax,nofail    0  0

Namespaces need to be created individually. That means, you need to execute the following command for each namespace you want to create:

ndctl create-namespace --mode=fsdax --map=dev

4.2.3 Device Error Prevention Enabled (CONFIG_IO_STRICT_DEVMEM)

The kernel build option CONFIG_IO_STRICT_DEVMEM has been enabled in the SLE kernel to prevent device errors. This option disables tampering with device state while a kernel driver is using the device.

Unfortunately, some vendor tools currently use such functionality. If you depend on such a tool, make sure to set the kernel boot parameter iomem=relaxed. Among others, this affects several firmware flash tools for POWER9 machines.

4.3 Security

4.3.1 Support for YubiKey and Nitrokey using the U2F frameworks.

Some applications require stronger authentication methods, including second factor authentication using physical tokens.

Support for YubiKey and Nitrokey is now shipped in the form of libraries, PAM modules and CLI and UI utilities.

4.3.2 su Does Not Preserve the Value of PATH

For security reasons, the su command does not preserve the value of the environment variable PATH any more by default. To return to the behavior from SLE 12, open the file /etc/default/su and change the option ALWAYS_SET_PATH to no.

4.3.3 Support for TLS 1.3 in OpenSSL 1.1.1

TLS 1.3 is a new version of the Transport Layer Security protocol with some major differences and improvements over the established TLS 1.2. This new protocol version is only available in OpenSSL 1.1.1 or later. This new version is not binary-compatible with the default version of OpenSSL in SLE 12 SP4 (OpenSSL 1.0), and has known differences in the API that require making adjustments before applications can benefit from the changes.

OpenSSL 1.1.1 with support for TLSv1.3 is shipped as an option. In SLE 12 SP4, the libraries can be loaded into the same binary image along with OpenSSL 1.0 with symbol versioning enabled. To take advantage of this new protocol option, applications need to be built with OpenSSL 1.1.1 explicitly.

OpenSSL 1.0 remains the default for system libraries, services and tools.

4.4 Networking

4.4.1 NFS Client Support For NFSv4.2 Has Been Enabled

The CONFIG_NFS_V4_2 configuration option has been enabled. This option enables support for minor version 2 of the NFSv4 protocol in the kernel's NFS client.

4.4.2 Intel* Omni-Path Architecture (OPA) host software

Intel Omni-Path Architecture (OPA) host software is fully supported in SUSE Linux Enterprise Server 12 SP4. Intel OPA provides Host Fabric Interface (HFI) hardware with initialization and setup for high performance data transfers (high bandwidth, high message rate, low latency) between compute and I/O nodes in a clustered environment.

For information about installing Intel Omni-Path Architecture documentation, see the documentation from Intel at https://www.intel.com/content/dam/support/us/en/documents/network-and-i-o/fabric-products/Intel_OP_Software_SLES_12_4_RN_K34561.pdf (link may not yet be active during the prerelease phase of SLES 12 SP4).

4.4.3 New GeoIP Database Sources

The GeoIP databases allow approximately geo-locating users by their IP address. In the past, the company MaxMind made such data available for free in its GeoLite Legacy databases. On January 2, 2019, MaxMind discontinued the GeoLite Legacy databases, now offering only the newer GeoLite2 databases for download. To comply with new data protection regulation, since December 30, 2019, GeoLite2 database users are required to comply with an additional usage license. This change means users now need to register for a MaxMind account and obtain a license key to download GeoLite2 databases. For more information about these changes, see the MaxMind blog (https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/).

SLES includes the GeoIP package of tools that are only compatible with GeoLite Legacy databases. As an update for SLES 12 SP4, we introduce the following new packages to deal with the changes to the GeoLite service:

  • geoipupdate: The official Maxmind tool for downloading GeoLite2 databases. To use this tool, set up the configuration file with your MaxMind account details. This configuration file can also be generated on the Maxmind web page. For more information, see https://dev.maxmind.com/geoip/geoip2/geolite2/.

  • geolite2legacy: A script for converting GeoLite2 CSV data to the GeoLite Legacy format.

  • geoipupdate-legacy: A convenience script that downloads GeoLite2 data, converts it to the GeoLite Legacy format, and stores it in /var/lib/GeoIP. With this script, applications developed for use with the legacy geoip-fetch tool will continue to work.

4.5 Systems Management

4.5.1 Salt Has Been Updated to Version 3000

Salt has been upgraded to upstream version 3000, plus a number of patches, backports and enhancements by SUSE. In particular, CVE-2020-11651 and CVE-2020-11652 fixes are included in our release.

As part of this upgrade, cryptography is now managed by the Python-M2Crypto library (which is itself based on the well-known OpenSSL library).

We intend to regularly upgrade Salt to more recent versions.

For more details about changes in your manually-created Salt states, see the Salt 3000 upstream release notes (https://docs.saltstack.com/en/latest/topics/releases/3000.html).

Salt 3000 is the last version of Salt which will support the old syntax of the cmd.run module.

4.5.2 The YaST Module for SSH Server Configuration Has Been Removed

The YaST module for configuring an SSH server which was present in SLE 11, is not a part of SLE 12. It does not have any direct successor.

The module SSH Server only supported configuring a small subset of all SSH server capabilities. Therefore, the functionality of the module can be replaced by using a combination of 2 YaST modules: The /etc/sysconfig Editor and the Services Manager. This also applies to system configuration via AutoYaST.

4.6 Storage

4.6.1 NVMe Multipath Handling

The default state for multipath of NVMe differs for SUSE Linux Enterprise 12 and 15.

In SUSE Linux Enterprise 12, multipath is off by default. In SUSE Linux Enterprise 15, multipath is on by default.

If the new default behavior does not work in your case, you can override it with the kernel command-line option LIBSTORAGE_MULTIPATH_AUTOSTART=ON.

With multipath activated, the device numbering is independent of physical slots.

5 AMD64/Intel 64 (x86_64) Specific Information

Information in this section pertains to the version of SUSE Linux Enterprise Server 12 SP4 for the AMD64/Intel 64 architectures.

5.1 Support for AMD Memory Encryption

To provide protection against physical attacks on a system, AMD SME can provide full or partial memory encryption depending on the use case, on AMD family 17h CPU processors. Full memory encryption means all DRAM contents are encrypted using random keys. This provides strong protection against cold boot, DRAM interface snooping and similar types of attacks. This technology is especially prominent for systems equipped with NVDIMMs whose contents remain intact after powering down the system.

Memory encryption support is present in SLE 15 kernels but not enabled by default. To enable it on compatible hardware (AMD family 17h CPU, with proper BIOS/UEFI support), supply the boot option mem_encrypt=on.

5.2 System and Vendor Specific Information

5.2.1 Intel Optane DC Persistent Memory Operating Modes

With SLE 15 SP1, Intel Optane DIMMs can be used in different modes on YES-certified platforms:

  • In App Direct Mode, the Intel Optane memory is used as fast persistent storage, an alternative to SSDs and NVMe devices. Data is persistent: It is kept when the system is powered off.

    App Direct Mode has been supported since SLE 12 SP4.

  • In Memory Mode, the Intel Optane memory serves as a cost-effective, high-capacity alternative to DRAM. In this mode, separate DRAM DIMMs act as a cache for the most frequently-accessed data while the Optane DIMMs memory provide large memory capacity. However, compared with DRAM-only systems, this mode is slower under random access workloads. If you run applications without Optane-specific enhancements that take advantage of this mode, memory performance may decrease. Data is not persistent: It is lost when the system is powered off.

    Memory Mode has been supported since SLE 15 SP1

  • In Mixed Mode, the Intel Optane memory is partitioned, so it can serve in both modes simultaneously.

    Mixed Mode has been supported since SLE 15 SP1.

Not all certified platforms support all modes mentioned above. Direct hardware-related questions at your hardware partner. SUSE works with all major hardware vendors to make use of Intel Optane a perfect experience on the OS- and open-source infrastructure level.

5.2.2 TPM 2.0 Software Stack Has Been Updated

The upstream projects for Intel's TPM 2.0 Software Stack have introduced major changes to the project structure. Notably, the resource manager daemon has been replaced by a new implementation that fixes stability and security issues.

The packaging has been adjusted to the upstream changes. The previous resource manager daemon, resourcemgr, which was previously part of the tpm2-0-tss package has been dropped. The new package tpm2.0-abrmd provides the new resource manager implementation (tpm2-abrmd / tabrmd).

6 POWER (ppc64le) Specific Information

Information in this section pertains to the version of SUSE Linux Enterprise Server 12 SP4 for the POWER architecture.

6.1 Support for ibmvnic Networking Driver

The kernel device driver ibmvnic provides support for vNIC (virtual Network Interface Controller) which is a PowerVM virtual networking technology that delivers enterprise capabilities and simplifies network management on IBM POWER systems. It is an efficient high-performance technology.

When combined with SR-IOV NIC, it provides bandwidth control Quality of Service (QoS) capabilities at the virtual NIC level. vNIC significantly reduces virtualization overhead resulting in lower latencies and fewer server resources (CPU, memory) required for network virtualization.

For a detailed support statement of ibmvnic in SLES, see https://www.suse.com/support/kb/doc/?id=7023703.

6.2 Reduced Memory Usage When Booting FADump Capture Kernel

One of the primary issues with Firmware Assisted Dump (FADump) on IBM POWER systems is that it needs a large amount of memory to be reserved. On large systems with terabytes of memory, this reservation can be significant.

Normally, the preserved memory is filtered to extract only relevant areas using the makedumpfile tool. While the tool allows determining what needs to be part of the dump and what memory to filter out, the default is to capture only kernel data and exclude everything else.

We take advantage of this default and the Linux kernel's Contiguous Memory Allocator (CMA) to fundamentally change the memory reservation model for FADump: Instead of setting aside a significant chunk of memory that cannot otherwise be used, the feature uses CMA instead. It reserves a significant chunk of memory that the kernel is prevented from using (due to MIGRATE_CMA), but applications are free to use it. With this, FADump will still be able to accurately capture all of the kernel memory and most of the user-space memory except for the user pages that are part of the CMA region reserved for FADump.

To disable this feature, pass the kernel parameter fadump=nocma instead of fadump=on. This ensures that the memory reserved for FADump is not used by applications. This option may be useful in scenarios where you prefer to also capture application data in the dump file.

6.3 SDT Markers in Select Applications and Libraries

SDT markers are static tracepoints included in the source code that expose certain information deemed useful by the application/library developers for various purposes including debugging and performance monitoring. Tools such as perf and systemtap can be used to record data provided at these tracepoints, and for subsequent processing.

In SLES 12 SP4, certain userspace applications and libraries (for example, glibc) are built with SDT markers enabled. This enhances the serviceability tooling.

6.4 Support for POWER9 PMU Events Has Been Added to the perf Tool

When executed on a POWER9 system, the perf tool now supports listing or specifying POWER9 PMU events by name.

6.5 Support for POWER9 24x7 Counters Has Been Added

SLES 12 SP4 adds support for the new version of the hypervisor API which is used to access 24x7 performance counters on POWER9 systems.

6.6 OProfile Support for POWER9

The OProfile package has been updated to include support for POWER9 processors.

6.7 Support for POWER9 Has Been Added to LibPFM

The LibPFM package has been updated to include support for POWER9 processors.

6.8 Support for POWER9 Has Been Added to PAPI

PAPI package updated to include support for POWER9 processors.

6.9 Speed of ibmveth Interface Not Reported Accurately

The ibmveth interface is a paravirtualized interface. When communicating between LPARs within the same system, the interface's speed is limited only by the system's CPU and memory bandwidth. When the virtual Ethernet is bridged to a physical network, the interface's speed is limited by the speed of that physical network.

Unfortunately, the ibmveth driver has no way of determining automatically whether it is bridged to a physical network and what the speed of that link is. ibmveth therefore reports its speed as a fixed value of 1 Gb/s which in many cases will be inaccurate. To determine the actual speed of the interface, use a benchmark. Using ethtool, you can then set a more accurate displayed speed.

7 IBM Z (s390x) Specific Information

Information in this section pertains to the version of SUSE Linux Enterprise Server 12 SP4 for the IBM Z architecture. For more information, see https://www.ibm.com/developerworks/linux/linux390/documentation_suse.html.

IBM zEnterprise 196 (z196) and IBM zEnterprise 114 (z114) are in the following referred to as z196 and z114.

7.1 Hardware

  • The addition of IBM z14 hardware instructions and an expanded set of IBM z13 hardware instructions in glibc enables improved performance and hardware support.

  • The LLVM compiler supports IBM z14 instructions for improved performance.

  • OpenSSL (1.1), ibmca, and libica support IBM z14 instructions for AES-GCM-based encryption of data in flight.

  • KVM guests can now use CPU features, including CPACF functions, that were introduced with IBM z14.

  • With z14, the hardware provides an indication of the configuration level of SIE, for example LPAR or KVM. IBM z14 sample configurations help to analyze and optimize KVM performance.

  • libica supports hardware acceleration for the SHA3 algorithm (CPACF MSA6) using CPACF hardware in IBM z14 machines.

  • CPU-MF Hardware Counters are added for IBM z13 and z13s. You can now access counters from the MT-diagnostic counter set that is available with IBM z13. You can also specify z13 specific counters using their symbolic event names and obtain counter descriptions with the lscpumf utility.

  • Support for the True Random Number Generator (TRNG, CPACF MSA7) in IBM z14 machines via CPACF. This improves the availability of random data in the kernel entropy pool.

7.2 Virtualization

  • KVM guests can exploit the new hardware features of the new CPU model IBM z14 ZR1.

  • Machine checks caused by failing KVM guests are now targeted at the KVM virtual server instead of the KVM hypervisor, thus making the hypervisor more resilient.

  • TLB Purge Enhancements are supported under KVM. This improves performance for KVM guests, in particular when subject to memory pressure.

  • Store Hypervisor Information (STHYI) from LPAR is available in KVM. Non-privileged user-space applications running on KVM can retrieve hypervisor capacity data through the LPAR if not provided by the Linux kernel.

  • Guarded Storage Facility is supported for improved performance of all Java workloads on KVM virtual servers.

  • Standard network boot setups can be used to deploy KVM guests.

  • The script kvm_stat was formerly a part of QEMU. However, it moved into the kernel tree upstream. To account for the change in the upstream project, in SLES 12 SP4, the script is now available from the new package kvm_stat.

  • LOADPARM and BOOTPROG are fully supported. A boot menu selection is available during IPL, for example, to recover from a defective KVM guest operating system.

  • Keyless Guests are supported for performance gains through improved memory handling for workloads running on Linux.

  • The IBM Call Home feature is enabled for KVM.

7.3 Network

7.3.1 Shared Memory Communications - Direct (SMC-Direct)

SMC-direct can be used via a new socket family and the existing tooling via TCP handshake. A preload library can be used to enable applications to use the new socket family transparently.

7.3.2 Exploitation of Shared Memory Communications (SMC-R) is now Supported

The technology preview flag is removed for SMC-R, that enables RDMA-capable network interface cards (RNICs) to offer RDMA over Converged Ethernet (RoCE).

Its usage is enabled by a collection of tools (smc-tools).

7.3.3 Support for SET VNIC_CHARS in qeth

qeth now supports SET VNIC_CHARS. You can configure MAC address flooding, learning, forwarding, and takeover behavior for HiperSockets devices.

7.4 Security

7.4.1 dm-crypt with Protected Keys - Change Master Key Tool

Manage LUKS2 encryption keys for protected key cryptography if the master key of the associated Crypto Express adapter is changed.

7.4.2 Support Architectural Limit of Crypto Adapters in zcrypt Device Driver

The crypto device driver now supports the theoretical maximum of 255 adapters.

7.4.3 Protected Key dm-crypt Key Management Tool

Protected key crypto for dm-crypt disks in plain format can be used without a dependency on cryptsetup support for LUKS(2) with protected keys. A key management tool as part of the s390-tools enables to manage a key repository allowing to associate secure keys with disk partitions or logical volumes.

7.4.4 libica: Use TRNG to Seed DRBG (Crypto)

Improved generation of high (pseudo) quality random numbers via libica DRBG especially to generate safe random keys by use of the PRNO-TRNG instruction.

7.4.5 Elliptic Curve Support for Crypto

The strategic elliptic curve asymmetric cryptography that provides strong security with shorter keys is now supported by Crypto Express function offloads with opencryptoki, libica, icatoken and openssl-ibmca.

7.4.6 Support for the CEX6S Crypto Card

The CEX6S crypto card is fully supported.

7.4.7 In-Kernel Cryptography: GCM Enhancements

Kernel services like IPSec now exploit IBM z14 cryptography hardware for the AES-GCM cipher.

7.4.8 Enhanced OpenSSL Support for PKCS#11 Engine

With the version update to 1.0.2, the PKCS#11 can also be linked as a module.

7.5 Reliability, Availability, Serviceability (RAS)

7.5.1 Support for DASD Block Layer Discard

SLES 12 SP4 includes support for the Linux discard function that releases unused space on z/VM VDISKs.

7.6 Performance

7.6.1 Performance Counters for IBM z14 (CPUMF)

The performance counters of the IBM z14 are supported and can be handled and displayed with the perf tool for optimized performance tuning.

7.6.2 Guest Kernel Support to Avoid Unnecessary TLB Purges

The Linux kernel now tags pages that are not used as part of a page table, so that the hypervisor can avoid unnecessary purging of guest TLB (translation lookaside buffer) entries.

7.6.3 Kernel Interface for the Guarded Storage Facility Added to Improve Java Performance

Optimized Java processes improve performance for many Java applications.

7.6.4 Single Increment Assignment of Memory

A new option for the “Attach Storage Element” SCLP command to speed up memory hotplug is available.

7.7 Miscellaneous

7.7.1 Deprecated DMSVSMA Functionality Has Been Removed from snIPL

The DMSVSMA RPC protocol was only used to remote access machines running z/VM versions that are now out of maintenance. snIPL's support for this protocol was deprecated beginning with SLES 12 SP1.

snIPL's support for remote access to z/VM hosts via the DMSVSMA RPC protocol has now been removed.

We recommend using SMAPI to remotely access z/VM hosts instead which is provided by supported z/VM 5.4, and z/VM 6.x versions. For information about setting up your z/VM system for API access, see z/VM Systems Management Application Programming, SC24-6234.

8 ARM 64-Bit (AArch64) Specific Information

Information in this section pertains to the version of SUSE Linux Enterprise Server 12 SP4 for the AArch64 architecture.

8.1 Boot and Driver Enablement for Raspberry Pi

Bootloaders and a supported microSD card image of SUSE Linux Enterprise Server for ARM 12 SP4 for the Raspberry Pi are available. The template of the SUSE Linux image is available as profile "RaspberryPi" in the package kiwi-templates-SLES12-JeOS to derive custom appliances.

Expansion Boards

The Raspberry Pi 3 Model B/B+ offers a 40-pin General Purpose I/O connector, with multiple software-configurable functions such as UART, I²C and SPI. This pin mux configuration along with any external devices attached to the pins is defined in the Device Tree which is passed by the bootloader to the kernel.

SUSE does not currently provide support for any particular HATs or other expansion boards attached to the 40-pin GPIO connector. However, insofar as drivers for pin functions and for attached chipsets are included in SUSE Linux Enterprise, they can be used. SUSE does not provide support for making changes to the Device Tree, but successful changes will not affect the support status of the operating system itself. Be aware that errors in the Device Tree can stop the system from booting successfully or can even damage the hardware.

The bootloader and firmware in SUSE Linux Enterprise Server 12 SP4 now support Device Tree Overlays. The new recommended way of configuring GPIO pins is to create a file extraconfig.txt on the FAT volume (/boot/efi/extraconfig.txt in the SUSE image) with a line dtoverlay=filename-without-.dtbo per Overlay. For more information about the syntax, see the documentation by the Raspberry Pi Foundation.

As a side effect, no separate /boot partition is needed anymore. This allows booting Btrfs snapshots in the SUSE image.

If not already shipped in the /boot/efi/overlays/ directory (raspberrypi-firmware-dt package), .dtbo files can be obtained from the manufacturer of the HAT or compiled from self-authored sources.

For More Information

For more information, see the SUSE Best Practices documentation for the Raspberry Pi at https://documentation.suse.com/sbp/all/html/SLES12SP3-rpiquick/index.html.

8.2 Toolchain Module Enabled in Default Installation


This entry has appeared in a previous release notes document.

The system compiler (gcc4.8) is not supported on the AArch64 architecture. To work around this issue, you previously had to enable the Toolchain module manually and use the GCC version from that module.

On AArch64, the Toolchain Module is now automatically pre-selected after registering SLES during installation. This makes the latest SLE compilers available on all installations. You now only need to make sure to also use that compiler.

Important: When Using AutoYaST, Make Sure to Enable Toolchain Module

Be aware that when using AutoYaST to install, you have to explicitly add the Toolchain module into the XML installation profile.

9 Packages and Functionality Changes

This section comprises changes to packages, such as additions, updates, removals and changes to the package layout of software. It also contains information about modules available for SUSE Linux Enterprise Server. For information about changes to package management tools, such as Zypper or RPM, see Section 4.5, “Systems Management”.

9.1 Updated Packages

9.1.1 Xorg Server Has Been Updated to Version 1.19.6-4.3.1

SLES 12 SP4 now includes version 1.19.6-4.3.1 of these two packages:

  • xorg-x11-server

  • xorg-x11-server-extra

The previous version was 7.6_1.15.2-36.21.

9.1.3 LibreOffice Has Been Updated to Version

LibreOffice has been updated to version For information about major changes, see the LibreOffice release notes at https://wiki.documentfoundation.org/ReleaseNotes/6.4.

9.1.4 KIWI Has Been Updated to 9.15.3

There was a widening gap between the KIWI version shipped in previous SLE 12 service packs and the upstream version of KIWI.

In SLE 12 SP4, KIWI has been updated to version 9.15.3, the same version that was also shipped in SLE 15 GA. Version 9 of KIWI is a complete rewrite of the software that, while keeping general compatibility, also includes many new features. This update also fixes several bugs related to building JeOS. Given the newer codestream, this update also simplifies support of the tool.

For a comparison between KIWI 7 and KIWI 9, see https://opensource.suse.com/kiwi/overview/legacy_kiwi.html.

9.1.5 PostgreSQL Has Been Upgraded to Version 10

SLES 12 SP4 and SLES 15 ship with PostgreSQL 10 by default. To enable an upgrade path for customers, SLE 12 SP3 now includes PostgreSQL 10 in addition to PostgreSQL 9.6 (the version that was originally shipped).

To upgrade a PostgreSQL server installation from an older version, the database files need to be converted to the new version.

Important: PostgreSQL Upgrade Needs to Be Performed Before Upgrade to New SLES Version

Neither SLES 12 SP4 nor SLES 15 include PostgreSQL 9.6. However, availability of PostgreSQL 9.6 is a requirement for performing the database upgrade to the PostgreSQL 10 format. Therefore, you must upgrade the database to the PostgreSQL 10 format before upgrading to the desired new SLES version.

Major New Features

The following major new features are included in PostgreSQL 10:

  • Logical replication: a publish/subscribe framework for distributing data

  • Declarative table partitioning: convenience in dividing your data

  • Improved query parallelism: speed up analyses

  • Quorum commit for synchronous replication: distribute data with confidence

  • SCRAM-SHA-256 authentication: more secure data access

PostgreSQL 10 also brings an important change to the versioning scheme that is used for PostgreSQL: It now follows the format major.minor. This means that minor releases of PostgreSQL 10 are for example 10.1, 10.2, ... and the next major release will be 11. Previously, both the parts of the version number were significant for the major version. For example, PostgreSQL 9.3 and PostgreSQL 9.4 were different major versions.

For the full PostgreSQL 10 release notes, see https://www.postgresql.org/docs/10/release-10.html (https://www.postgresql.org/docs/10/release-10.html).


Before starting the migration, make sure the following preconditions are fulfilled:

  1. The packages of your current PostgreSQL version must have been upgraded to their latest maintenance update.

  2. The packages of the new PostgreSQL major version need to be installed. For SLE 12, this means installing postgresql10-server and all the packages it depends on. Because pg_upgrade is contained in the package postgresql10-contrib, this package must be installed as well, at least until the migration is done.

  3. Unless pg_upgrade is used in link mode, the server must have enough free disk space to temporarily hold a copy of the database files. If the database instance was installed in the default location, the needed space in megabytes can be determined by running the following command as root: du -hs /var/lib/pgsql/data. If there is little disk space available, run the command VACUUM FULL SQL command on each database in the PostgreSQL instance that you want to migrate. This command can take very long.

Upstream documentation about pg_upgrade including step-by-step instructions for performing a database migration can be found locally at file:///usr/share/doc/packages/postgresql10/html/pgupgrade.html (if the postgresql10-docs package is installed), or online at https://www.postgresql.org/docs/10/pgupgrade.html (https://www.postgresql.org/docs/10/pgupgrade.html). The online documentation explains how you can install PostgreSQL from the upstream sources (which is not necessary on SLE) and also uses other directory names (/usr/local instead of the update-alternatives based path as described above).

9.1.6 MariaDB Has Been Upgraded to 10.2

The MariaDB packages have been upgraded to the 10.2 series that brings many new features and bug fixes.

The list of major changes for 10.2 series can be found at https://mariadb.com/kb/en/library/changes-improvements-in-mariadb-102/. The update to the new MariaDB version generally does not cause issues. However, there are the following notable incompatible changes:

  • InnoDB is now the default storage engine.

  • Some options have updated default values.

  • Some options have been removed/renamed.

For more information about upgrading, see the upgrade notes at https://mariadb.com/kb/en/library/upgrading-from-mariadb-100-to-mariadb-101/ and https://mariadb.com/kb/en/library/upgrading-from-mariadb-101-to-mariadb-102/.

Apart from the changes in MariaDB Server itself, there are also packaging changes:

  • All configuration snippets placed in my.cnf.d were merged to my.cnf file (omit default_plugins.cnf as all configuration here was commented out).

  • By default, MariaDB will not listen for TCP/IP connections.

  • The list of binaries was changed:

    • The mytop utility was removed and it is packaged separately

    • The following binaries were added: mariabackup, mbstream, myrocks_hotbackup, sst_dump, mysql_ldb, etc.

  • systemd services were renamed from mysql.service to mariadb.service. A mysql alias is still provided for the backward compatibility.

9.2 Removed and Deprecated Functionality

9.2.1 libcgroup1 Removed From SLE 12 SP4 and Later

Most functionality of libcgroup1 is also provided by systemd. In fact, the cgroup handling of libcgroup1 can conflict with that of systemd.

Starting with SLE 12 SP4, libcgroup1 has been removed. Migrate to the equivalent functionality in systemd.

For more information, see https://www.suse.com/support/kb/doc/?id=7018741.

9.3 Changes in Packaging and Delivery

9.3.1 MPI Implementations Identify in mpi-selector's list Command By Name Only

Previously, the MPI implementations openmpi, mvapich2, and mpich (and their variants) were configured to identify themselves with their name and exact version in mpi-selector --list. However, this behavior created a package upgrade issue where newly updated MPI packages would not be registered automatically.

As part of a maintenance update to SLE, the registration issue was fixed by making the packages identify only by their name but not their exact version number in mpi-selector --list. As this functionality was never meant as a way to support multiple versions of the same MPI implementation side by side, this should not cause practical issues.

Note that as an exception from the rule, it continues to be possible to install all available major versions of openMPI side by side (those can be, depending on the operating system version and installed extensions, openmpi, openmpi2, and openmpi3).

9.3.2 Kernel Firmware Only Shipped as Part of the kernel-firmware Package

In past releases, the kernel-default package used to contain firmware for in-kernel drivers.

Starting with SLES 12 SP3, such firmware is now delivered as part of the package kernel-firmware.

10 Technical Information

This section contains information about system limits, a number of technical changes and enhancements for the experienced user.

When talking about CPUs, we use the following terminology:

CPU Socket

The visible physical entity, as it is typically mounted to a motherboard or an equivalent.

CPU Core

The (usually not visible) physical entity as reported by the CPU vendor.

On IBM Z, this is equivalent to an IFL.

Logical CPU

This is what the Linux Kernel recognizes as a "CPU".

We avoid the word "thread" (which is sometimes used), as the word "thread" would also become ambiguous subsequently.

Virtual CPU

A logical CPU as seen from within a Virtual Machine.

10.1 Kernel Limits

This table summarizes the various limits which exist in our recent kernels and utilities (if related) for SUSE Linux Enterprise Server 12 SP4.

SLES 12 SP4 (Linux 4.12) AMD64/Intel 64 (x86_64)IBM Z (s390x)POWER (ppc64le)AArch64 (ARMv8)

CPU bits





Maximum number of logical CPUs





Maximum amount of RAM (theoretical/certified)

> 1 PiB/64 TiB

10 TiB/256 GiB

1 PiB/64 TiB

256 TiB/n.a.

Maximum amount of user space/kernel space

128 TiB/128 TiB


512 TiB 1/2 EiB

256 TiB/128 TiB

Maximum amount of swap space

Up to 29 * 64 GB (x86_64) or 30 * 64 GB (other architectures)

Maximum number of processes


Maximum number of threads per process

Upper limit depends on memory and other parameters (tested with more than 120,000)2

Maximum size per block device

Up to 8 EiB



1 By default, the userspace memory limit on the POWER architecture is 128 TiB. However, you can explicitly request mmaps up to 512 TiB.

2 The total number of all processes and all threads on a system may not be higher than the maximum number of processes.

10.2 KVM Limits

SLES 12 SP4 Virtual Machine (VM) Limits

Maximum VMs per host

Unlimited (total number of virtual CPUs in all guests being no greater than 8 times the number of CPU cores in the host)

Maximum Virtual CPUs per VM


Maximum Memory per VM

4 TiB

Virtual Host Server (VHS) limits are identical to those of SUSE Linux Enterprise Server.

10.3 Xen Limits

Since SUSE Linux Enterprise Server 11 SP2, we removed the 32-bit hypervisor as a virtualization host. 32-bit virtual guests are not affected and are fully supported with the provided 64-bit hypervisor.

SLES 12 SP4 Virtual Machine (VM) Limits

Maximum number of virtual CPUs per VM

FV: 128; PV: 512

Maximum amount of memory per VM

x86-64: 2 TiB; x86: 16 GiB

SLES 12 SP4 Virtual Host Server (VHS) Limits

Maximum number of physical CPUs


Maximum number of virtual CPUs

Unlimited (total number of virtual CPUs in all guests must be no greater than 8 times the number of CPU cores in the host)

Maximum amount of physical memory

16 TiB

Maximum amount of Dom0 physical memory

500 GiB

Maximum number of block devices

12,000 SCSI logical units

  • PV:  Paravirtualization

  • FV:  Full virtualization

For more information about acronyms, see the virtualization documentation provided at https://documentation.suse.com/sles/12-SP4/.

AMD Rome-based CPUs are not supported by Xen on SLES 12 SP4. These CPUs are only supported by SLES 12 SP5 and higher.

10.4 File Systems

10.4.1 Comparison of Supported File Systems

SUSE Linux Enterprise was the first enterprise Linux distribution to support journaling file systems and logical volume managers back in 2000. Later, we introduced XFS to Linux, which today is seen as the primary work horse for large-scale file systems, systems with heavy load and multiple parallel reading and writing operations. With SUSE Linux Enterprise 12, we went the next step of innovation and started using the copy-on-write file system Btrfs as the default for the operating system, to support system snapshots and rollback.

+ supported

FeatureBtrfsXFSExt4OCFS 2 1 ReiserFS 2

Support in products






Data/metadata journaling

N/A 3

– / +

+ / +

– / +

– / +

Journal internal/external

N/A 3

+ / +

+ / +

+ / –

+ / +

Journal checksumming

N/A 3






Offline extend/shrink

+ / +

– / –

+ / +

+ / – 4

+ / –

Online extend/shrink

+ / +

+ / –

+ / –

– / –

+ / –

Inode allocation map





u. B*-tree

Sparse files






Tail packing


Small files stored inline

+ (in metadata)

+ (in inode)

+ (in inode)

+ (in metadata)





Extended file attributes/ACLs

+ / +

+ / +

+ / +

+ / +

+ / +

User/group quotas

– / –

+ / +

+ / +

+ / +

+ / +

Project quotas



Subvolume quotas






Data dump/restore


Block size default

4 KiB 5

Maximum file system size

16 EiB

8 EiB

1 EiB

4 PiB

16 TiB

Maximum file size

16 EiB

8 EiB

1 EiB

4 PiB

1 EiB

1 OCFS 2 is fully supported as part of the SUSE Linux Enterprise High Availability Extension.

2 ReiserFS is supported for existing file systems. The creation of new ReiserFS file systems is discouraged.

3 Btrfs is a copy-on-write file system. Instead of journaling changes before writing them in-place, it writes them to a new location and then links the new location in. Until the last write, the changes are not committed. Because of the nature of the file system, quotas are implemented based on subvolumes (qgroups).

4 To extend an OCFS 2 file system, the cluster must be online but the file system itself must be unmounted.

5 The block size default varies with different host architectures. 64 KiB is used on POWER, 4 KiB on other systems. The actual size used can be checked with the command getconf PAGE_SIZE.

Additional Notes

Maximum file size above can be larger than the file system's actual size because of the use of sparse blocks. All standard file systems on SUSE Linux Enterprise Server have LFS, which gives a maximum file size of 263 bytes in theory.

The numbers in the above table assume that the file systems are using a 4 KiB block size which is the most common standard. When using different block sizes, the results are different.

In this document: 1024 Bytes = 1 KiB; 1024 KiB = 1 MiB; 1024 MiB = 1 GiB; 1024 GiB = 1 TiB; 1024 TiB = 1 PiB; 1024 PiB = 1 EiB. See also http://physics.nist.gov/cuu/Units/binary.html.

NFSv4 with IPv6 is only supported for the client side. An NFSv4 server with IPv6 is not supported.

The version of Samba shipped with SUSE Linux Enterprise Server 12 SP4 delivers integration with Windows Active Directory domains. In addition, we provide the clustered version of Samba as part of SUSE Linux Enterprise High Availability Extension 12 SP4.

Some file system features are available in SUSE Linux Enterprise Server 12 SP4 but are not supported by SUSE. By default, the file system drivers in SUSE Linux Enterprise Server 12 SP4 will refuse mounting file systems that use unsupported features (in particular, in read-write mode). To enable unsupported features, set the module parameter allow_unsupported=1 in /etc/modprobe.d or write the value 1 to /sys/module/MODULE_NAME/parameters/allow_unsupported. However, note that setting this option will render your kernel and thus your system unsupported.

10.4.2 Supported Btrfs Features

The following table lists supported and unsupported Btrfs features across multiple SLES versions.

+ supported

FeatureSLES 11 SP4SLES 12 SP3SLES 12 SP4SLES 15 GA
Copy on Write++++
Metadata Integrity++++
Data Integrity++++
Online Metadata Scrubbing++++
Automatic Defragmentation
Manual Defragmentation++++
In-band Deduplication
Out-of-band Deduplication++++
Quota Groups++++
Metadata Duplication++++
Multiple Devices+++
RAID 0+++
RAID 1+++
RAID 10+++
Hot Add/Remove+++
Device Replace
Seeding Devices
Big Metadata Blocks+++
Skinny Metadata+++
Send Without File Data+++
Inode Cache
Fallocate with Hole Punch+++

10.5 Supported Java Versions

The following table lists Java implementations available in SUSE Linux Enterprise Server 12 SP4:

Name (Package Name)VersionPart of SUSE Linux Enterprise ServerSupport
OpenJDK (java-1_8_0-openjdk)1.8.0SLESSUSE, L3
OpenJDK (java-1_7_0-openjdk)1.7.0SLESSUSE, L3
IBM Java (java-1_8_0-ibm)1.8.0SLESExternal only
IBM Java (java-1_7_1-ibm)1.7.1SLESExternal only
IBM Java (java-1_6_0-ibm)1.6.0Legacy ModuleExternal only
Print this page