SUSE Linux Enterprise Server 15 SP5
Release Notes #
Abstract#
SUSE Linux Enterprise Server is a modern, modular operating system for both multimodal and traditional IT. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Enterprise Server 15 SP5 and highlights important product updates.
These release notes are updated periodically. The latest version of these release notes is always available at https://www.suse.com/releasenotes. General documentation can be found at https://documentation.suse.com/sles/15-SP5.
- 1 About the release notes
- 2 SUSE Linux Enterprise Server
- 3 Modules, extensions, and related products
- 4 Installation and upgrade
- 5 Changes affecting all architectures
- 6 POWER-specific changes (ppc64le)
- 7 IBM Z-specific changes (s390x)
- 8 Arm 64-bit-specific changes (AArch64)
- 9 Removed and deprecated features and packages
- 10 Obtaining source code
- 11 Legal notices
- A Changelog for 15 SP5
- B Kernel parameter changes
1 About the release notes #
These Release Notes are identical across all architectures, and the most recent version is always available online at https://www.suse.com/releasenotes.
Entries are only listed once but they can be referenced in several places 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 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 15 SP5 is a multimodal operating system that paves the way for IT transformation in the software-defined era. It is a modern and modular OS that helps simplify multimodal IT, makes traditional IT infrastructure efficient and provides an engaging platform for developers. As a result, you can easily deploy and transition business-critical workloads across on-premises and public cloud environments.
SUSE Linux Enterprise Server 15 SP5, with its multimodal design, helps organizations transform their IT landscape by bridging traditional and software-defined infrastructure.
2.1 Interoperability and hardware support #
Designed for interoperability, SUSE Linux Enterprise Server integrates into classical Unix and 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-performance guest on leading hypervisors. This makes SUSE Linux Enterprise Server the perfect guest operating system for virtual computing.
2.2 What is new? #
2.2.1 General changes in SLE 15 #
SUSE Linux Enterprise Server 15 introduces many innovative changes compared to SUSE Linux Enterprise Server 12. The most important changes are listed below.
- Migration from openSUSE Leap to SUSE Linux Enterprise Server
SLE 15 SP2 and later support migrating from openSUSE Leap 15 to SUSE Linux Enterprise Server 15. Even if you decide to start out with the free community distribution, you can later easily upgrade to a distribution with enterprise-class support. For more information, see the Upgrade Guide at https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-upgrade-online.html#sec-upgrade-online-opensuse-to-sle.
- Extended package search
Use the new Zypper command
zypper search-packages
to search across all SUSE repositories available for your product, even if they are not yet enabled. For more information see Section 5.10.5, “Searching packages across all SLE modules”.- Software Development Kit
In SLE 15, packages formerly shipped as part of the Software Development Kit are now integrated into the products. Development packages are packaged alongside other packages. In addition, the Development Tools module contains tools for development.
- RMT replaces SMT
SMT (Subscription Management Tool) has been removed. Instead, RMT (Repository Mirroring Tool) now allows mirroring SUSE repositories and custom repositories. You can then register systems directly with RMT. In environments with tightened security, RMT can also proxy other RMT servers. If you are planning to migrate SLE 12 clients to version 15, RMT is the supported product to handle such migrations. If you still need to use SMT for these migrations, beware that the migrated clients will have all installation modules enabled. For more information see Section 4.2.4, “SMT has been replaced by RMT”.
- Media changes
The Unified Installer and Packages media known from SUSE Linux Enterprise Server 15 SP1 have been replaced by the following media:
Online Installation Medium: Allows installing all SUSE Linux Enterprise 15 products. Packages are fetched from online repositories. This type of installation requires a registration key. Available SLE modules are listed in Section 3.1, “Modules in the SLE 15 SP5 product line”.
Full Installation Medium: Allows installing all SUSE Linux Enterprise Server 15 products without a network connection. This medium contains all packages from all SLE modules. SLE modules need to be enabled manually during installation. RMT (Repository Mirroring Tool) and SUSE Manager provide additional options for disconnected or managed installations.
Major updates to the software selection: #
- Salt
SLE 15 SP5 can be managed via Salt, making it integrate better with modern management solutions such as SUSE Manager.
- Python 3
As the first enterprise distribution, SLE 15 offers full support for Python 3 development in addition to Python 2.
- Directory Server
389 Directory Server replaces OpenLDAP as the LDAP directory service. OpenLDAP has been re-added to SLE 15 SP5 and SLE SP6 to prolong the time window for a migration to 389 Directory Server. Support for OpenLDAP on SLE 15 will end with the SLE 15 SP6 lifecycle. Future versions and service packs of SLE will not include OpenLDAP.
2.2.2 Changes in 15 SP5 #
SUSE Linux Enterprise Server 15 SP5 introduces changes compared to SUSE Linux Enterprise Server 15 SP4. The most important changes are listed below:
2.2.3 Package and module changes in 15 SP5 #
The full list of changed packages compared to 15 SP4 can be seen at this URL:
The full list of changed modules compared to 15 SP4 can be seen at this URL:
2.3 Important sections of this document #
If you are upgrading from a previous SUSE Linux Enterprise Server release, you should review at least the following sections:
2.4 Security, standards, and certification #
SUSE Linux Enterprise Server 15 SP5 will not be submitted for certification to either Common Criteria or NIST FIPS 140-3. As a practice, SUSE only submits even-numbered Service Packs (for example: SLES 15, SP2, SP4, etc.) for certification.
For more information about certification, see https://www.suse.com/support/security/certifications/.
2.5 Documentation and other information #
2.5.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 installation medium for a chronological log of all changes made to the updated packages.Find more information in the
docu
directory of the installation medium of SUSE Linux Enterprise Server 15 SP5. This directory includes PDF versions of the SUSE Linux Enterprise Server 15 SP5 Installation Quick Start Guide.
2.5.2 Online documentation #
For the most up-to-date version of the documentation for SUSE Linux Enterprise Server 15 SP5, see https://documentation.suse.com/sles/15-SP5.
2.6 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 15 has a 13-year life cycle, with 10 years of General Support and three years of Extended Support. The current version (SP5) will be fully maintained and supported until six months after the release of SUSE Linux Enterprise Server 15 SP6.
If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support duration. You can buy an additional 12 to 36 months in twelve month increments. This means that you receive a total of three to five years of support per Service Pack.
For more information, see the pages Support Policy and Long Term Service Pack Support.
2.7 Support statement for SUSE Linux Enterprise Server #
To receive support, you need an appropriate subscription with SUSE. For more information, see https://www.suse.com/support/?id=SUSE_Linux_Enterprise_Server.
The following definitions apply:
- L1
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering, and basic troubleshooting using the documentation.
- L2
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate the problem area, and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
- L3
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 is delivered with L3 support for all packages, except for the following:
Technology Previews, see Section 2.8, “Technology previews”
Sound, graphics, fonts and artwork
Packages that require an additional customer contract, see Section 2.7.2, “Software requiring specific contracts”
Some packages shipped as part of the module Workstation Extension are L2-supported only
Packages with names ending in
-devel
(containing header files and similar developer resources) will only be supported together with their main packages.
SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.
2.7.1 General support #
To learn about supported features and limitations, refer to the following sections in this document:
2.7.2 Software requiring specific contracts #
Certain software delivered as part of SUSE Linux Enterprise Server may require an external contract.
Check the support status of individual packages using the RPM metadata that can be viewed with rpm
, zypper
, or YaST.
Major packages and groups of packages affected by this are:
PostgreSQL (all versions, including all subpackages)
2.7.3 Software under GNU AGPL #
SUSE Linux Enterprise Server 15 SP5 (and the SUSE Linux Enterprise modules) includes the following software that is shipped only under a GNU AGPL software license:
Ghostscript (including subpackages)
SUSE Linux Enterprise Server 15 SP5 (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:
MySpell dictionaries and LightProof
ArgyllCMS
2.8 Technology previews #
Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations. Technology previews are included for your convenience to give you a chance to test new technologies within your environment. We would appreciate your feedback! If you test a technology preview, contact your SUSE representative and let them know about your experience and use cases. Your input is helpful for future development.
Technology previews come with the following limitations:
Technology previews are still in development. Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.
Technology previews are not supported.
Technology previews may only be available for specific hardware architectures. Details and functionality of technology previews are subject to change. As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.
Technology previews can be removed from a product at any time. This may be the case, for example, if SUSE discovers that a preview does not meet the customer or market needs, or does not comply with enterprise standards.
2.8.1 Technology previews for Arm 64-Bit (AArch64) #
2.8.1.1 KVM virtualization with 64K page size kernel flavor #
As a technology preview, SUSE Linux Enterprise Server for Arm 15 SP3 added a kernel flavor
64kb
.
SUSE Linux Enterprise Server for Arm 15 SP5 introduces support for this 64kb
kernel flavor (Section 8.3, “64K page size kernel flavor is supported”).
KVM virtualization with this 64kb
kernel flavor remains a technology preview.
Use the default
kernel flavor for virtualization support.
2.8.1.2 Driver enablement for NVIDIA BlueField-2 DPU as host platform #
SUSE Linux Enterprise Server for Arm 15 SP1 and later kernels include drivers for installing on NVIDIA* BlueField* Data Processing Unit (DPU) based server platforms and SmartNIC (Network Interface Controller) cards.
As a technology preview, the SUSE Linux Enterprise Server for Arm 15 SP4 and SP5 kernels include drivers for running on NVIDIA BlueField-2 DPU.
Should you wish to use SUSE Linux Enterprise Server for Arm on NVIDIA BlueField-2 or BlueField-2X (or BlueField-3) in production, contact your SUSE representative.
Note: Host drivers and tools for NVIDIA BlueField-2 SmartNICs
This Technology Preview status applies only to installing SUSE Linux Enterprise Server for Arm 15 SP5 on NVIDIA BlueField-2 DPUs.
For an NVIDIA BlueField-2 DPU PCIe card inserted as SmartNIC into a
SUSE Linux Enterprise Server 15 SP5 or SUSE Linux Enterprise Server for Arm 15 SP5 based server,
check Section 2.8, “Technology previews” and Section 5.4, “Kernel” for support status or known
limitations of NVIDIA ConnectX* network drivers for BlueField-2 DPUs
(mlx5_core
and others).
The rshim
tool is available from SUSE Package Hub (Section 5.9, “SUSE Package Hub”).
2.8.1.4 lima driver for Arm Mali Utgard GPUs available #
The Xilinx* Zynq* UltraScale*+ MPSoC contains an Arm* Mali*-400 Graphics Processor Unit (GPU).
Prior to SUSE Linux Enterprise Server for Arm 15 SP2, this GPU needed third-party drivers and libraries from your hardware vendor.
As a technology preview, the SUSE Linux Enterprise Server for Arm 15 SP2 kernel added
lima
, a Display Rendering Infrastructure (DRI) driver for Mali Utgard
microarchitecture GPUs, such as Mali-400, and the Mesa-dri
package
contains a matching lima_dri
graphics driver library.
Note
To use them, the Device Tree passed by the bootloader to the kernel needs to include a description of the Mali GPU for the kernel driver to get loaded. You may need to contact your hardware vendor for a bootloader firmware upgrade.
Note
The panfrost
driver for Mali Midgard microarchitecture GPUs
is supported since SUSE Linux Enterprise Server for Arm 15 SP2.
2.8.1.5 mali-dp driver for Arm Mali Display Processors available #
The NXP* Layerscape* LS1028A/LS1018 System-on-Chip contains an Arm* Mali*-DP500 Display Processor.
As a technology preview, the SUSE Linux Enterprise Server for Arm 15 SP2 kernel added mali-dp
,
a Display Rendering Manager (DRM) driver for Mali Display Processors.
It has undergone only limited testing because it requires an accompanying
physical-layer driver for DisplayPort* output (see Section 8.4.3, “No DisplayPort graphics output on NXP LS1028A and LS1018A”).
2.8.1.6 Btrfs file system is enabled in U-Boot bootloader #
For Raspberry Pi* devices, SUSE Linux Enterprise Server for Arm 12 SP3 and later include Das U-Boot as bootloader, in order to align the boot process with other platforms. By default, it loads GRUB as UEFI application from a FAT-formatted partition, and GRUB then loads Linux kernel and ramdisk from a file system such as Btrfs.
As a technology preview, SUSE Linux Enterprise Server for Arm 15 SP2 added a Btrfs driver to
U-Boot for the Raspberry Pi (package u-boot-rpiarm64
).
This allows its commands ls
and load
to access files on Btrfs-formatted
partitions on supported boot media, such as microSD and USB.
The U-Boot command btrsubvol
lists Btrfs subvolumes.
2.8.2 Technology previews for Intel 64/AMD64 (x86-64) #
2.8.2.1 Support for AMD Wheat Nas GPU #
SLES 15 SP5 includes the kernel driver support for AMD Wheat Nas GPU (Navi32 dGPU). However because the corresponding firmware is still not publicly released yet, this feature is considered a technology preview.
4 Installation and upgrade #
SUSE Linux Enterprise Server can be deployed in several ways:
Physical machine
Virtual host
Virtual machine
System containers
Application containers
4.1 Installation #
This section includes information related to the initial installation of SUSE Linux Enterprise Server 15 SP5.
Important: Installation documentation
The following release notes contain additional notes regarding the installation of SUSE Linux Enterprise Server. However, they do not document the installation procedure itself.
For installation documentation, see the Deployment Guide at https://documentation.suse.com/sles/15-SP5/html/SLES-all/book-deployment.html.
4.1.1 New media layout #
The set of media has changed with 15 SP2. There still are two different installation media, but the way they can be used has changed:
You can install with registration using either the online-installation medium (as with SUSE Linux Enterprise Server 15 SP1) or the full medium.
You can install without registration using the full medium. The installer has been added to the full medium and the full medium can now be used universally for all types of installations.
You can install without registration using the online-installation medium. Point the installer at the required SLE repositories, combining the
install=
andinstsys=
boot parameters:With the
install=
parameter, select a path that contains either just the product repository or the full content of the media.With the
inst-sys=
parameter, point at the installer itself, that is,/boot/ARCHITECTURE/root
on the medium.
For more information about the parameters, see https://en.opensuse.org/SDB:Linuxrc#p_install.
4.1.2 SUSE Manager installation option not available #
Because the release of version 4.4 of SUSE Manager was dropped, there is no SUSE Manager Server 4.4 option available under the Available Extensions and Modules section during installation. See https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/4.3/index.html#_important_note for more information.
4.1.3 Storage requirements for Btrfs installation on PowerPC #
There is a known issue with using guided partitioning to install SUSE Linux Enterprise Server on PowerPC architecture. The root filesystem needs more storage that the listed minimum. It is recommended to allocate at least 20 gigabytes.
4.1.4 Installation via SSH on s390x #
Before starting the installation using yast.ssh
, it is neccessary to set the environmental variable QT_XCB_GL_INTEGRATION
to xcb_egl
:
export QT_XCB_GL_INTEGRATION=xcb_egl
4.2 Upgrade-related notes #
This section includes upgrade-related information for SUSE Linux Enterprise Server 15 SP5.
Important: Upgrade documentation
The following release notes contain additional notes regarding the upgrade of SUSE Linux Enterprise Server. However, they do not document the upgrade procedure itself.
For upgrade documentation, see the Upgrade Guide at https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-upgrade-online.html.
4.2.1 Hibernation requires manual intervention #
Previously, it was possible for data loss to occur due to the system not hibernating correctly.
In 15 SP5, a sanity check was introduced to prevent this.
It works by removing the kernel resume
parameter if it points to a non-existent device.
However, that means a system would not use the hibernation data.
To fix it, do the following:
Edit
/etc/default/grub
and correct theresume
parameter to point to an existing device.Regenerate
initrd
.Reboot.
4.2.2 Make sure the current system is up-to-date before upgrading #
Upgrading the system is only supported from the most recent patch level.
Make sure the latest system updates are installed by either running zypper patch
or by starting the YaST module Online Update.
An upgrade on a system that is not fully patched may fail.
4.2.3 Skipping service packs requires LTSS #
Skipping service packs during an upgrade is only supported if you have a Long Term Service Pack Support contract. Otherwise, you need to first upgrade to SLE 15 SP4 before upgrading to SLE 15 SP5.
4.2.4 SMT has been replaced by RMT #
SLE 12 is the last codestream that SMT (Subscription Management Tool) is available for.
When upgrading your OS installation to SLE 15, we recommend also upgrading from SMT to its replacement RMT (Repository Mirroring Tool). RMT provides the following functionality:
Mirroring of SUSE-originated repositories for the SLE 12-based and SLE 15-based products your organization has valid subscriptions for.
Synchronization of subscriptions from SUSE Customer Center using your organization’s mirroring credentials. (These credentials can be found in SCC under Select Organization, Organization, Organization Credentials)
Selecting repositories to be mirrored locally via
rmt-cli
tool.Registering systems directly to RMT to get required updates.
Adding custom repositories from external sources and distributing them via RMT to target systems.
Improved security with proxying: If you have strict security requirements, an RMT instance with direct Internet access can proxy to another RMT instance without direct Internet access.
Nginx as Web server: The default Web server of RMT is Nginx which has a smaller memory footprint and comparable performance than that used for SMT.
Note that unlike SMT, RMT does not support installations of SLE 11 and earlier.
For more feature comparison between RMT and SMT, see https://github.com/SUSE/rmt/blob/master/docs/smt_and_rmt.md.
For more information about RMT, also see the new RMT Guide at https://documentation.suse.com/sles/15-SP3/html/SLES-all/book-rmt.html.
4.3 Minimal VM and Minimal Image #
SUSE Linux Enterprise Server Minimal VM and Minimal Image is a slimmed-down form factor of SUSE Linux Enterprise Server that is ready to run in virtualization environments and the cloud. With SUSE Linux Enterprise Server Minimal VM and Minimal Image, you can choose the right-sized SUSE Linux Enterprise Server option to fit your needs.
SUSE provides virtual disk images for Minimal VM and Minimal Image in the file formats .qcow2
, .vhdx
, and .vmdk
, compatible with KVM, Xen, OpenStack, Hyper-V, and VMware environments.
All Minimal VM and Minimal Image images set up the same disk size (24 GB) for the system.
Due to the properties of different file formats, the size of Minimal VM and Minimal Image image downloads differs between formats.
4.4 JeOS renamed Minimal VM and Minimal Image #
We have received feedback from users confused by the name JeOS, as a matter of fact the acronym JeOS, which meant Just enough Operating System, was not well understood and could be confused with other images provided by SUSE or openSUSE.
We have decided to go with simplicity and rename JeOS by "Minimal VM" for all our Virtual Machine Images and "Minimal Image" for the Raspberry Pi Image. We have also removed a few other characters, in the full images name to make it more simple and clear:
SLES15-SP4-Minimal-VM.x86_64-kvm-and-xen-GM.qcow2
SLES15-SP4-Minimal-VM.x86_64-OpenStack-Cloud-GM.qcow2
SLES15-SP4-Minimal-VM.x86_64-MS-HyperV-GM.vhdx.xz
SLES15-SP4-Minimal-VM.x86_64-VMware-GM.vmdk.xz
SLES15-SP4-Minimal-VM.aarch64-kvm-GM.qcow2
SLES15-SP4-Minimal-Image.aarch64-RaspberryPi-GM.raw.xz
4.5 New Minimal VM and Minimal Image for IBM Z (s390x) #
Per request, we have built and released new SLES Minimal VM and Minimal Image for IBM Z (s390x architecture).
Our Minimal VM and Minimal Image are supported on the 3 different type of storage used by IBM Z:
DASDs (Direct Access Storage Devices) which works for z/VM guests and LPARs,
FBA (Fixed-Block Architecture) which works for z/VM guests,
and the regular qcow2 for KVM.
And to provide deployment choice, we have made 2 flavours for each type of storage, one with the regular jeos-firstboot
, one with cloud-init
.
So in total we have 6 new images:
KVM:
SLES15-SP5-Minimal-VM.s390x-kvm-GM.qcow2
SLES15-SP5-Minimal-VM.s390x-Cloud-GM.qcow2
DASD:
SLES15-SP5-Minimal-Image.s390x-dasd-GM.raw.xz
SLES15-SP5-Minimal-Image.s390x-dasd-Cloud-GM.raw.xz
FBA:
SLES15-SP5-Minimal-Image.s390x-fba-GM.raw.xz
SLES15-SP5-Minimal-Image.s390x-fba-Cloud-GM.raw.xz
Note that our regular images uses jeos-firstboot
and Btrfs as the root filesystem by default, while our Cloud images use XFS as it’s usually recommended in cloud environment.
4.5.1 Alternative modern Python 3 interpreter upgraded to Python 3.11 #
Warning: Changing system Python is not supported
Changing the system Python interpreter (located at /usr/bin/python3
) is not supported.
The recommended method of using non-system Python is an explicit shebang in the script file or using a virtual environment.
SLE 15 comes with a complete stack of Python 3.6 (interpreter, setuptools, wheel, pip plus hundreds of modules). Python 3.6 is fully supported by SUSE throught the complete lifecycle of SLE 15.
However, there are very few pip
installable modules that are still compatible with 3.6 or older.
Therefore, starting with SLE 15 SP4, SUSE introduced a new Python 3 Module.
It includes additional modern Python interpreter (plus setuptool
, wheel
, pip
and pypi support, but no additional modules).
This new allows more flexibility in providing a fully supported more recent Python interpreter in SLE.
Packages within the Python 3 module can be installed alongside existing Python packages and they can coexist within the same system without impacting any ongoing Python 3.6 workloads.
In SLE 15 SP5 the Python 3 Module ships with Python 3.11.
In SLE 15 SP4, which originally shipped with Python 3.10, Python 3.11 packages have been added in addition to the existing Python 3.10 packages. If you are using Python 3.10 in SLE 15 SP4 make sure to update the packages from the Python 3 Module to version 3.11 before upgrading to SLE SP5.
SLE 15 SP3 was shipped with the alternative Python version 3.9 included in Basesystem Module.
Python 3.11 is compatible with versions 3.10 and 3.9. Code written in 3.9 or 3.10 should run without or with only minimal changes in 3.11.
4.6 For more information #
For more information, see Section 5, “Changes affecting all architectures” and the sections relating to your respective hardware architecture.
5 Changes affecting all architectures #
Information in this section applies to all architectures supported by SUSE Linux Enterprise Server 15 SP5.
5.1 Containers #
5.1.1 Podman upgrade from 3.4.x to 4.3.1 #
Podman 4.x is a major release with 60 new features and more than 50 bug fixes compared to Podman 3. It also includes a complete rewrite of the network stack.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x . The new stack brings 3 important improvement:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing break with this major change, the old CNI stack will remain the default on existing installations, while new installs will use Netavark.
New installations can opt to use CNI by explicitly specifying it via the containers.conf
configuration file, using the network_backend
field.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
There is a marker in Podman’s local storage that indicates this.
In order to begin using Podman 4, you need to destroy that marker with podman system reset
.
This will destroy the marker, all of the images, all of the networks, and all of the containers.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks. You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
Last but not least CNI will be deprecated from upstream at a future date: https://github.com/containers/podman/tree/main/cni
For a complete overview of the changes, please check out the upstream 4.0.0 but also 4.1.1, 4.2.0 and 4.3.0 to be informed about all the new features and changes.
5.1.2 suse/sle15
container uses NDB as the database back-end for RPM #
Starting with SUSE Linux Enterprise 15 SP3, the rpm
package in the suse/sle15
container image no longer supports the BDB back-end (based on Berkeley DB) and switches to the NDB back-end.
Tools for scanning, diffing, and building container image using the rpm
binary of the host for introspection can fail or return incorrect results if the host’s version of rpm
does not recognize the NDB format.
To use such tools, make sure that the host supports reading NDB databases, such as hosts with SUSE Linux Enterprise 15 SP2 and later.
5.2 Desktop #
5.2.1 nouveau
disabled for Nvidia Turing and Ampere GPUs / openGPU recommendation #
The nouveau
driver is still considered experimental for Nvidia Turing and Ampere GPUs.
Therefore it has been disabled by default on systems with these GPUs.
Instead of using the nouveau
driver we recommend using Nvidia’s new openGPU driver.
Install this driver by installing these following packages:
nvidia-open-driver-G06-signed-kmp-default
kernel-firmware-nvidia-gsp-G06
Then uncomment the options nvidia
line in the /etc/modprobe.d/50-nvidia-default.conf
file so that it looks like the following afterwards:
### Enable support on *all* Turing/Ampere GPUs: Alpha Quality!
options nvidia NVreg_OpenRmEnableUnsupportedGpus=1
If you prefer using nouveau
driver anyway, add nouveau.force_probe=1
to your kernel boot parameters, and do not install the above openGPU package.
5.3 Development #
5.3.1 Alternative modern Python 3 interpreter upgraded to Python 3.11 #
Warning: Changing system Python is not supported
Changing the system Python interpreter (located at /usr/bin/python3
) is not supported.
The recommended method of using non-system Python is an explicit shebang in the script file or using a virtual environment.
SLE 15 comes with a complete stack of Python 3.6 (interpreter, setuptools, wheel, pip plus hundreds of modules). Python 3.6 is fully supported by SUSE throught the complete lifecycle of SLE 15.
However, there are very few pip
installable modules that are still compatible with 3.6 or older.
Therefore, starting with SLE 15 SP4, SUSE introduced a new Python 3 Module.
It includes additional modern Python interpreter (plus setuptool
, wheel
, pip
and pypi support, but no additional modules).
This new allows more flexibility in providing a fully supported more recent Python interpreter in SLE.
Packages within the Python 3 module can be installed alongside existing Python packages and they can coexist within the same system without impacting any ongoing Python 3.6 workloads.
In SLE 15 SP5 the Python 3 Module ships with Python 3.11.
In SLE 15 SP4, which originally shipped with Python 3.10, Python 3.11 packages have been added in addition to the existing Python 3.10 packages. If you are using Python 3.10 in SLE 15 SP4 make sure to update the packages from the Python 3 Module to version 3.11 before upgrading to SLE SP5.
SLE 15 SP3 was shipped with the alternative Python version 3.9 included in Basesystem Module.
Python 3.11 is compatible with versions 3.10 and 3.9. Code written in 3.9 or 3.10 should run without or with only minimal changes in 3.11.
5.3.1.1 Details #
Although fully supported throughout the entire lifecycle of SLE 15, Python 3.6 is no longer developed by the Python community and it won’t any receive new functionality. Providing a modern Python versions as an alternative allows you to migrate to the newer version and to benefit from increased performance, compatibility with the latest syntax and new standard library versions. You will also be able to utilize contemporary modules provided by pypi.org.
The Python 3.11 interpreter and the SUSE provided Python modules will be supported in SLE 15 until at least 31st of December 2027. The interpreter will be regularly updated to the latest patch version. The Python modules will remain stable unless there is a security vulnerabiltiy or other significant issues. In such cases, the preferred approach will be to backport patches and maintain the released version.
Added Python 3.11 interpreter and a basic set of modules (see the module’s package list for details)
All python 3.11 packages are prefixed with
python311-
to distinguish from the default (3.6) Python packagesComes with significant performance improvments compared to Python 3.6
Compatible to Python 3.10 and 3.9
Supported on SLE 15 until at least 2027-12-31
The Python 3 Module containing Python 3.11 will be activated by default
The Python 3.6 interpreter and modules stay the default and remain supported throughout the SLE 15 lifecycle.
We will continue delivering new interpreters (along with the respective
setuptools
/wheel
/pip
and pypi support, but no additional modules) with the Python 3 Module with each new service pack.
5.3.1.2 TCK compliance testing in SUSE Linux Enterprise #
We run the TCK test suite provided by Oracle to ensure that our version of OpenJDK is in compliance with the Java specification.
5.3.2 Supported Java versions #
The following Java implementations are available in SUSE Linux Enterprise Server 15 SP5:
Name (Package Name) | Version | Module | Support |
---|---|---|---|
OpenJDK | 11 | Base System | SUSE, L3, until 2026-12-31 |
OpenJDK | 17 | Base System | SUSE, L3, until 2028-06-30 |
OpenJDK | 1.8.0 | Legacy | SUSE, L3, until 2026-12-31 |
IBM Java | 1.8.0 | Legacy | External, until 2025-04-30 |
5.4 Kernel #
5.4.1 Kernel limits #
This table summarizes the various limits which exist in our recent kernels and utilities (if related) for SUSE Linux Enterprise Server 15 SP5.
SLES 15 SP5 (Linux 5.14.21) | AMD64/Intel 64 (x86_64) | IBM Z (s390x) | POWER (ppc64le) | ARMv8 (AArch64) |
---|---|---|---|---|
CPU bits | 64 | 64 | 64 | 64 |
Maximum number of logical CPUs | 8192 | 256 | 2048 | 768 |
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 | n.a. | 4 PiB1/2 EiB | 256 TiB/256 TiB |
Maximum amount of swap space | Up to 29 * 64 GB | Up to 30 * 64 GB | ||
Maximum number of processes | 1,048,576 | |||
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 on all 64-bit architectures | |||
FD_SETSIZE | 1024 |
1 By default, the user space memory limit on the POWER architecture is 128 TiB. However, you can explicitly request mmaps up to 4 PiB.
2 The total number of all processes and all threads on a system may not be higher than the "maximum number of processes".
5.4.2 Restoring default Btrfs file compression #
Previously in kernel 5.14, it was possible to disable compression by passing an empty string instead of explicitly mentioning none
or no
.
In SLES 15 SP5, this behavior is changed to the more expected one. From kernel 5.14 onwards, empty string will reset the default setting instead of disabling compression.
5.5 Miscellaneous #
5.5.1 TigerVNC’s vncserver
has been removed #
The vncserver
wrapper script around Xvnc has been removed upstream.
See the official documentation for information on using Xvnc in version 1.11.0 or newer.
5.5.2 cpuid
has been added #
The cpuid
package has been added.
It provides detailed information about the CPU.
For more information see http://etallen.com/cpuid.html.
5.6 Networking #
5.6.1 frr
(FRRouting Routing daemon) has been added #
The frr
package has been added.
It manages TCP/IP based routing protocols.
FRR is a fork of Quagga, which has stopped development in 2018. Its developers moved to the FRR project and thus Quagga will receive no further updates.
We recommend migrating to frr
.
The configuration is mostly backward compatible, including the vtysh
shell to configure the routing protocols.
However, there were several changes, improvements, and new functionality added to frr
.
See https://frrouting.org/ for more information.
5.6.2 Samba #
The version of Samba shipped with SUSE Linux Enterprise Server 15 SP5 delivers integration with Windows Active Directory domains. In addition, we provide the clustered version of Samba as part of SUSE Linux Enterprise High Availability 15 SP5.
5.7 Security #
5.7.1 TLS 1.1 and 1.0 are no longer recommended for use #
The TLS 1.0 and 1.1 standards have been superseded by TLS 1.2 and TLS 1.3. TLS 1.2 has been available for considerable time now.
SUSE Linux Enterprise Server packages using OpenSSL, GnuTLS, or Mozilla NSS already support TLS 1.3. We recommend no longer using TLS 1.0 and TLS 1.1, as SUSE plans to disable these protocols in a future service pack. However, not all packages, for example, Python, are TLS 1.3-enabled yet as this is an ongoing process.
5.7.2 Replacement of gpg
as recommended tool for file encryption #
A new rage-encryption
package has been added.
The package provides the rage
executable.
rage
is an implementation of the age
file encryption format using Rust.
This replaces gpg
as the preferred tool over gpg
for file encryption.
The main reasons are that gpg
has a history of security issues, and is well known for its complexity.
In comparison, rage
focuses on usability and security.
It especially tries to make key handling as simple as handling SSH keys (essentially short lines of text), which it also supports.
For more information, see:
5.8 Storage and file systems #
5.8.1 dracut default persistent policy change #
The previously used by-path
policy had the following shortcomings:
doesn’t work for multi-path
very fragile for iSCSI
can change with hardware changes
To avoid the above problems, the persistent policy of dracut
is now set to by-uuid
.
5.8.2 Comparison of supported file systems #
SUSE Linux Enterprise was the first enterprise Linux distribution to support journaling file systems and logical volume managers in 2000. Later, we introduced XFS to Linux, which allows for reliable large-scale file systems, systems with heavy load, and multiple parallel reading and writing operations. With SUSE Linux Enterprise 12, we started using the copy-on-write file system Btrfs as the default for the operating system, to support system snapshots and rollback.
The following table lists the file systems supported by SUSE Linux Enterprise.
Support status: + supported / ‒ unsupported
Feature | Btrfs | XFS | Ext4 | OCFS 21 |
---|---|---|---|---|
Supported in product | SLE | SLE | SLE | SLE HA |
Data/metadata journaling | N/A2 | ‒ / + | + / + | ‒ / + |
Journal internal/external | N/A2 | + / + | + / + | + / ‒ |
Journal checksumming | N/A2 | + | + | + |
Subvolumes | + | ‒ | ‒ | ‒ |
Offline extend/shrink | + / + | ‒ / ‒ | + / + | + / ‒3 |
Inode allocation map | B-tree | B+-tree | Table | B-tree |
Sparse files | + | + | + | + |
Tail packing | ‒ | ‒ | ‒ | ‒ |
Small files stored inline | + (in metadata) | ‒ | + (in inode) | + (in inode) |
Defragmentation | + | + | + | ‒ |
Extended file attributes/ACLs | + / + | + / + | + / + | + / + |
User/group quotas | ‒ / ‒ | + / + | + / + | + / + |
Project quotas | ‒ | + | + | ‒ |
Subvolume quotas | + | N/A | N/A | N/A |
Data dump/restore | ‒ | + | ‒ | ‒ |
Block size default | 4 KiB4 | |||
Maximum file system size | 16 EiB | 8 EiB | 1 EiB | 4 PiB |
Maximum file size | 16 EiB | 8 EiB | 1 EiB | 4 PiB |
1 OCFS 2 is fully supported as part of the SUSE Linux Enterprise High Availability.
2 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
).
3 To extend an OCFS 2 file system, the cluster must be online but the file system itself must be unmounted.
4 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 table above 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.
Some file system features are available in SUSE Linux Enterprise Server 15 SP5 but are not supported by SUSE.
By default, the file system drivers in SUSE Linux Enterprise Server 15 SP5 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.
5.8.3 Supported Btrfs features #
The following table lists supported and unsupported Btrfs features across multiple SLES versions.
Support status: + supported / ‒ unsupported
Feature | SLES 11 SP4 | SLES 12 SP5 | SLES 15 GA | SLES 15 SP1 | SLES 15 SP2 | SLES 15 SP3 |
---|---|---|---|---|---|---|
Copy on write | + | + | + | + | + | + |
Free space tree (Free Space Cache v2) | ‒ | ‒ | ‒ | + | + | + |
Snapshots/subvolumes | + | + | + | + | + | + |
Swap files | ‒ | ‒ | ‒ | + | + | + |
Metadata integrity | + | + | + | + | + | + |
Data integrity | + | + | + | + | + | + |
Online metadata scrubbing | + | + | + | + | + | + |
Automatic defragmentation | ‒ | ‒ | ‒ | ‒ | ‒ | ‒ |
Manual defragmentation | + | + | + | + | + | + |
In-band deduplication | ‒ | ‒ | ‒ | ‒ | ‒ | ‒ |
Out-of-band deduplication | + | + | + | + | + | + |
Quota groups | + | + | + | + | + | + |
Metadata duplication | + | + | + | + | + | + |
Changing metadata UUID | ‒ | ‒ | ‒ | + | + | + |
Multiple devices | ‒ | + | + | + | + | + |
RAID 0 | ‒ | + | + | + | + | + |
RAID 1 | ‒ | + | + | + | + | + |
RAID 5 | ‒ | ‒ | ‒ | ‒ | ‒ | ‒ |
RAID 6 | ‒ | ‒ | ‒ | ‒ | ‒ | ‒ |
RAID 10 | ‒ | + | + | + | + | + |
Hot add/remove | ‒ | + | + | + | + | + |
Device replace | ‒ | ‒ | ‒ | ‒ | ‒ | ‒ |
Seeding devices | ‒ | ‒ | ‒ | ‒ | ‒ | ‒ |
Compression | ‒ | + | + | + | + | + |
Big metadata blocks | ‒ | + | + | + | + | + |
Skinny metadata | ‒ | + | + | + | + | + |
Send without file data | ‒ | + | + | + | + | + |
Send/receive | ‒ | + | + | + | + | + |
Inode cache | ‒ | ‒ | ‒ | ‒ | ‒ | ‒ |
Fallocate with hole punch | ‒ | + | + | + | + | + |
5.9 SUSE Package Hub #
SUSE Package Hub brings open-source software packages from openSUSE to SUSE Linux Enterprise Server and SUSE Linux Enterprise Desktop.
Usage of software from SUSE Package Hub is not covered by SUSE support agreements. At the same time, usage of software from SUSE Package Hub does not affect the support status of your SUSE Linux Enterprise systems. SUSE Package Hub is available at no additional cost and without an extra registration key.
5.9.1 Important package additions to SUSE Package Hub #
Among others, the following packages have been added to SUSE Package Hub:
5.10 System management #
5.10.1 Effective user limits in systemd setup #
Before, the lookup of the effective session limit in a systemd setup was not trivial. Now these new properties have been added:
EffectiveMemoryMax
EffectiveMemoryHigh
EffectiveTasksMax
5.10.2 Silence KillMode=None
messages #
The log level of the deprecation warnings regarding killmode=None
have been reduced.
Instead of warning
, they are now logged at the debug
log level.
5.10.3 yast2-iscsi-client
drops open-iscsi
and iscsiuio
as dependencies #
The yast2-iscsi-client
package no longer automatically installs open-iscsi
and iscsiuio
.
The two packages need to be installed manually before using yast2-iscsi-client
.
5.10.4 Support for System V init.d scripts is deprecated #
systemd in SUSE Linux Enterprise Server 15 SP5 automatically converts System V init.d
scripts to service files.
Support for System V init.d scripts is deprecated and will be removed with the next major version of SUSE Linux Enterprise Server.
In the next major version of SUSE Linux Enterprise Server, systemd will also stop converting System V init.d
scripts to systemd service files.
To prepare for this change, use the automatically generated systemd service files directly instead of using System V init.d
scripts.
To do so, copy the generated service files to /etc/systemd/system
.
To then control the associated services, use systemctl
.
The automatic conversion provided by systemd (specifically, systemd-sysv-generator
) is only meant to ensure backward compatibility with System V init.d scripts.
To take full advantage of systemd features, it can be beneficial to manually rewrite the service files.
This deprecation also causes the following changes:
The
/etc/init.d/halt.local
initscript is deprecated. Use systemd service files instead.rcSERVICE
controls of systemd services are deprecated. Use systemd service files instead.insserv.conf
is deprecated.
5.10.5 Searching packages across all SLE modules #
In SLE 15 SP5 you can search for packages both within and outside of currently enabled SLE modules using the following command:
zypper search-packages -d SEARCH_TERM
This command contacts the SCC and searches all modules for matching packages. This functionality makes it easier for administrators and system architects to find the software packages needed.
5.11 Virtualization #
For more information about acronyms used below, see https://documentation.suse.com/sles/15-SP5/html/SLES-all/book-virtualization.html.
Important: Virtualization limits and supported hosts/guests
These release notes only document changes in virtualization support compared to the immediate previous service pack of SUSE Linux Enterprise Server. Full information regarding virtualization limits for KVM and Xen as well as supported guest and host systems is now available as part of the SUSE Linux Enterprise Server documentation.
See the Virtualization Guide at https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-virt-support.html.
5.11.1 KVM #
We increase the support from 288 up 768 VCPU per virtual Machine.
5.11.2 Xen #
Xen has been updated to version 4.17:
The x86 MCE command line option info is now updated.
__ro_after_init
support, for marking data as immutable after boot.The project has officially adopted 4 directives and 24 rules of MISRA-C, added MISRA-C checker build integration, and defined how to document deviations.
IOMMU superpage support on x86, affecting PV guests as well as HVM/PVH ones when they don’t share page tables with the CPU (HAP/EPT/NPT).
Support for
VIRT_SSBD
andMSR_SPEC_CTRL
for HVM guests on AMD.Improved TSC, CPU, and APIC clock frequency calibration on x86.
Support for Xen using x86 Control Flow Enforcement technology for its own protection. Both Shadow Stacks (ROP protection) and Indirect Branch Tracking (COP/JOP protection).
Add
mwait-idle
support for SPR and ADL on x86.Extend security support for hosts to 12 TiB of memory on x86.
Add command line option to set cpuid parameters for dom0 at boot time on x86.
It is possible to use PV drivers with dom0less guests, allowing statically booted dom0less guests with PV devices.
Add Xue - console over USB 3 Debug Capability.
dropped support for the (x86-only)
vesa-mtrr
andvesa-remap
command line optionslaunch_security
: Use SEV-ES policy=0x07 if host supports it
5.11.3 QEMU #
QEMU has been updated to version 7.1:
Raise the maximum number of vCPUs a VM can have to 1024 (only 768 is supported)
Improve dependency handling (for example, what is recommended compared to what is required)
Add the
qemu-headless
subpackage that brings in all the packages that are needed for creating VMs with tools likevirt-install
orVirtManager
; it can be run either locally or from a remote hostThe old
qemu-binfmt
wrappers around the variousqemu-$ARCH
Linux user emulation binaries are not necessary any longerEnable` aio=io_uring` on all KVM architectures
For more information see the following:
Note: Deprecation notice
In previous versions, if no explicit image format was provided, some QEMU tools tried to guess the format of the image, and then process it accordingly. Because this feature is a potential source of security issues, it has been deprecated and removed. It is now necessary to explicitly specify the image format. For more information, see https://qemu-project.gitlab.io/qemu/about/removed-features.html#qemu-img-backing-file-without-format-removed-in-6-1.
5.11.4 libvirt #
libvirt
has been updated to version 9.0.0:
New
virt-qemu-sev-validate
utility for validating the measurement reported for a domain launched with AMD SEVNew subpackage
libvirt-client-qemu
providing client utilities to interact with QEMU-specific features oflibvirt
Migration to
/usr/etc
: saving user changed configuration files in/etc
and restoring them while an RPM update
For more information see the following:
5.11.5 VMware #
5.11.5.1 open-vm-tools #
open-vm-tools
has been updated to version 12.1.5:
Migration of PAM settings to
/usr/lib/pam.d
Remove libgrpc++, libgrpc, and libprotobuf from containerinfo
Requires
section. The dependencies will be added automatically.Add
containerInfo
pluginAdd dependencies on grpc, protobuf, and containerd for container introspection
A number of Coverity reported issues have been addressed.
The
deployPkg
plugin may prematurely reboot the guest VM before cloud-init has completed user data setup. If both the Perl based Linux customization script and cloud-init run when the guest VM boots, the deployPkg plugin may reboot the guest before cloud-init has finished. ThedeployPkg
plugin has been updated to wait for a running cloud-init process to finish before the guest VM reboot is initiated.A
SIGSEGV
may be encountered when a non-quiesing snapshot times outUnwanted
vmtoolsd
service error message if not on a VMware hypervisor Whenopen-vm-tools
comes preinstalled in a base Linux release, thevmtoolsd
services are started automatically at system start and desktop login. If running on physical hardware or in a non-VMware hypervisor, the services will emit an error message to the systemd’s logging service before stopping.
5.11.6 Others #
5.11.6.1 Deprecating host network management with libvirt
#
Managing host network devices with libvirt
's virInterface*
APIs is deprecated and may be removed in a future service pack.
Any users of these APIs or virsh
's iface-*
subcommands should use the distribution networking tools instead.
For more information see the Basic networking chapter of the Administration Guide at https://documentation.suse.com/sles/15-SP5/single-html/SLES-administration/#cha-network.
5.11.6.2 NVIDIA GRID #
Support for NVIDIA Virtual GPU (vGPU) v15.1 has been added. The support does NOT include NVIDIA vGPU live migration support.
5.11.6.3 virt-manager
#
virt-manager
has been updated to version 4.1.0:
Specifying
--boot
no longer impliesno_install=yes
add UI and cli support for
qemu-vdagent
channelcli: More
--iothreads
suboptionscli: Add support for URL query with disks
5.11.6.4 sanlock
#
sanlock
has been updated to version 3.8.5:
Add support for Python 3
Add support for 4k sector size
Support
SANLOCK_RUN_DIR
andSANLOCK_PRIVILEGED
environment variables
5.11.6.5 Perl-Sys-Virt #
Update to 0.9.0: * Add all new APIs and constants in libvirt 9.0.0
5.11.6.6 numactl
#
numactl
has been updated to version 2.0.15.0.g01a39cb:
Update to support multiple nodes
numademo: Add a new test for multiple-preferred-nodes policy
numactl: Simplify preferred selection
5.11.6.7 libguestfs #
libguestfs
has been updated to version 1.48.4:
Drop reiserfs
Multiple fixes to the OCaml bindings
Inspection of guests which use LUKS encryption on top of LVM logical volumes should now work
guestfs_remove_drive
has been deprecated and now returns an error.guestfs_add_drive
no longer supports hotpluggingIn
guestfs_xfs_admin
thelazycounter
parameter is deprecated because it is no longer supported in recent versions of XFS.The User-mode Linux ("uml") backend has been removed.
This release has moved many virt tools like virt-builder, virt-cat, virt-customize, virt-df, etc. to the guestfs-tools project. This makes libguestfs a bit easier to build and manage.
We now use the
qemu
/libvirt
feature-cpu max
to select the best CPU to run the appliance.The
qemu -enable-fips
option is no longer used. It was not needed and has been deprecated byqemu
.Using the equivalent SeaBIOS feature instead of `qemu’s Serial Graphics Adapter option ROM
Renamed packages:
guestfs-winsupport
→libguestfs-winsupport
guestfsd
→libguestfsd
New packages:
libguestfs
,libguestfs-typelib-Guestfs
,libguestfs-gobject
,libguestfs-gobject-devel
libguestfs-rescue
,libguestfs-rsync
,libguestfs-xfs
Dropped packages:
libguestfs-test
5.11.6.8 virt-v2v #
Update to version 2.0.7:
Virt-v2v has been modularised allowing external programs to examine the state of the conversion and inject their own copying step. Further enhancements will be made to this new architecture in forthcoming releases.
The command line is almost identical apart from some debugging features that were removed (see below). The only significant difference is that the output format (-of) now has to be specified if it is different from the input format, whereas previous versions of virt-v2v would use the same output formatas input format automatically.
A lot of time was spent improving the performance of virt-v2v in common cases.
Many bug fixes and performance enhancements were made to oVirt imageio output (Nir Soffer).
There is a new virt-v2v-in-place(1) tool which replaces the existing virt-v2v --in-place option.
Virt-v2v can now convert guests which use LUKS encrypted logical volumes.
Option -oo rhv-direct has been replaced by -oo rhv-proxy, and direct mode (which is much faster) is now the default when writing to oVirt, with proxy mode available for restricted network configurations.
The following command line options were removed: -print-estimate, --debug-overlays, --no-copy.
Virt-v2v no longer installs the RHEV-APT tool in Windows guests. This tool was deprecated and then removed in oVirt 4.3.
Deprecated tool virt-v2v-copy-to-local has been removed.
5.11.6.9 sevctl
#
The sevctl
package version 0.3.2 has been added.
It replaces the deprecated sev-tool
package.
6 POWER-specific changes (ppc64le) #
Information in this section applies to SUSE Linux Enterprise Server for POWER 15 SP5.
Also see the following notes elsewhere:
6.1 Security #
There were also the following changes:
POWER10 performance enhancements for cryptography: NSS FreeBL
6.1.1 POWER10 performance enhancements for cryptography: nettle #
There were the following improvements:
Use defined structure constants of P1305 in
asm.m4
Implement Poly1305 single block update based on radix 2^64
Workaround for qemu bug affecting the ppc instruction vmsumudm
6.1.2 POWER10 performance enhancements for cryptography: libgcrypt #
There were the following improvements:
Chacha20/poly1305 - Optimized chacha20/poly1305 for P10 operation
AES-GCM: Bulk implementation of AES-GCM acceleration for ppc64le
hwf-ppc: fix missing HWF_PPC_ARCH_3_10 in HW feature
6.1.3 POWER10 performance enhancements for cryptography: OpenSSL #
There were the following improvements:
AES-GCM
AES-GCM performance optimization with stitched method for p9+ ppc64le
Chacha20
chacha20 performance optimizations for ppc64le with 8x lanes, Performance increase around 50%
6.2 Storage #
6.2.1 NVMe-oF on LVM with multiple NVMe disks #
The installation of NVMe Over Fabrics (NVMe-oF) does not work with Logical Volume Management when the root Volume Group utilizes a storage pool consisting of multiple NVMe-oF disks, which necessitates discovery beyond the boot disk.
6.3 Virtualization #
There were also the following changes:
Added NVMf-FC kdump support
6.3.1 Support for the new H_WATCHDOG hypercall included with P10 firmware #
Added a pseries-wdt
driver that exposes these hypercall-based watchdog timers to userspace via the Linux watchdog API.
6.3.2 ibmveth
driver performance improvement #
Changed the ibmveth
driver to implement a more efficient way of giving packets to the hypervisor for transmit.
Instead of DMA mapping and unmapping every outgoing data buffer, the buffer is copied into a reusable DMA mapped buffer.
Also implemented multiple transmit queues for parallel packet processing.
6.3.3 Adding changes in ibmvnic
driver to assign IRQ affinity to all #
CPUs after hotplug events (CPU or vnic device): irqbalance daemon provides --banmod
option so that IRQ affinities will be preserved with driver settings.
But the irqbalance --banmod
option is not working with vnic IRQs and this feature fixes the bug in the irqbalance daemon code.
6.4 Miscellaneous #
6.4.1 Transactional memory is deprecated and disabled #
On POWER9, transactional memory is partially emulated by the hypervisor, but this does not give the expected performance.
Therefore, transactional memory is now disabled by default in the kernel.
For legacy applications on platforms that still support transactional memory, it can be enabled with the ppc_tm=on
kernel parameter.
7 IBM Z-specific changes (s390x) #
Information in this section applies to SUSE Linux Enterprise Server for IBM Z and LinuxONE 15 SP5. For more information, see https://www.ibm.com/docs/en/linux-on-systems?topic=distributions-suse-linux-enterprise-server
7.1 Hardware #
There were the following hardware-related changes:
Support for IBM z16 and LinuxONE 4 in qclib
Exploitation support of new IBM Z crypto hardware in zcrypt DD
Support for a new set of crypto performance counters of the IBM z16 and LinuxONE 4
Add new CPU-MF Counters for IBM z16 and LinuxONE 4 in kernel,` s390-tools` and libpfm part.
Support for "Crypto Compliance" feature of the IBM z16 and LinuxONE 4 Processor-Activity-Instrumentation Facility in kernel and` s390-tools`
7.2 Networking #
7.2.1 Enablement for MIO Instructions - kernel and rdma-core
parts #
Make use of the new PCI Load/Store instructions in the rdma-core
package for increased performance.
7.3 Performance #
7.3.1 zlib CRC32 optimization for s390x #
This new feature utilizes SIMD instructions to accelerate the zlib CRC32 implementation, resulting in significant performance improvements for applications that rely heavily on zlib.
7.4 Security #
7.4.1 Secure Execution #
If you want to use IBM Secure Execution see https://www.ibm.com/docs/en/linux-on-systems?topic=execution-prerequisites-restrictions
7.4.2 openCryptoki: p11sak
support Dilithium and Kyber keys #
The openCryptoki p11sak
tool has been extended to manage Dilithium and Kyber keys.
7.4.3 In-kernel crypto: SIMD implementation of chacha20
#
Recent kernel releases provide support for the chacha20
cipher and the goal of this feature is to use z System SIMD instruction to accelerate the chacha20
implementation on IBM Z and LinuxONE.
7.4.4 openCryptoki ep11 token: master key consistency #
Ensuring that all APQNs used by an openCryptoki ep11 token are configured with the same master key, if not print an error message and fail initialization.
7.4.5 zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware for kernel and s390-tools
#
zcrypt DD: exploitation support of new IBM Z crypto hardware by recognizing and supporting the CEX8 adapters.
7.4.6 Display PAI (Processor Activity Instrumentation) CPACF counters (s390-tools
) #
Provides a tool to display CPACF usage counters from the IBM z16 and LinuxONE 4 Processor Activity Instrumentation Facility.
7.4.7 openCryptoki EP11 token: IBM z16 and LinuxONE 4 support #
The openCryptoki EP11 token supports new vendor specific mechanisms for quantum safe ciphers (Dilithium and Kyber) supported by the CEX8S crypto adapter.
7.4.8 openCryptoki EP11 token: vendor-specific key derivation #
Support of a new function from EP11 7.2 by the openCryptoki EP11 token. Comprises the support of vendor-specific mechanisms for a key derivation function used with cryptocurrencies and Schnorr signatures.
7.4.9 openCryptoki: support crypto profiles #
Support for a new configuration option to restrict cryptographic functions/mechanisms.
7.4.10 openCryptoki key generation with expected MKVP only on CCA and EP11 tokens #
For the EP11 and CCA tokens allow to configure expected master key verification pattern (MKVPs) configured in the crypto adapter(s) and upon generation of a new secure keys ensures that the MKVP of the generated key is equal to an expected MKVP.
7.4.11 libica: extend statistics to reflect security measures (crypto) #
Adds new -k
parameter to icastats
to display detailed counters to reflect security measures (key size/curve/hash size).
7.4.12 libica
: eliminate SW fall backs - stage 2 #
Eliminates implementations of SW fallback functions for RSA in libica
.
7.4.13 zcryptctl
support for control domains - kernel and s390-tools parts #
Improves access control to crypto resources via device nodes, for example, for Docker containers by allowing to assign control domains to a device node created by zcryptctl
.
7.4.14 openCryptoki: PKCS #11 3.1 - support CKA_DERIVE_TEMPLATE #
In openCryptoki, support the new attribute CKA_DERIVE_TEMPLATE
introduced with PKCS #11 v3.1.
7.4.15 p11-kit
: add IBM specific mechanisms and attributes #
Adds support for IBM-specific attributes and mechanisms to the PKCS11 client-server implementation of p11-kit
.
7.4.16 libica
: FIPS 140-3 compliance #
Update of libica
to fulfill FIPS 140-3 requirements.
7.5 Storage #
7.5.1 Transparent DASD PPRC (Peer-to-Peer Remote Copy) handling #
Enables user of Linux on Z to use DASD volumes in a PPRC (Peer-to-Peer Remote Copy) relation like a normal DASD volume thereby enabling platform support along with improving user experience.
7.5.2 zdev: Site-aware device configuration #
Enables a Linux on Z admin to prepare a Linux root/boot volume so that it can be started on a different system (site) or with different device IDs and parameters without manually changing the configuration.
7.5.3 zipl
support for Secure Boot IPL and Dump from ECKD DASD #
Enables zipl
to use an ECKD DASD for Secure Boot IPL and Dump.
7.5.4 zipl
: Site-aware environment block #
Enables a Linux on Z admin to create a zipl
configuration file that enables different kernel parameters depending on the IPL site.
7.5.5 Transparent PCI device recovery #
Improves reliability and reduces downtime by using cooperative recovery strategies that allow the drivers to recover from error scenarios automatically (without intervention from userspace), and without going through a complete tear-down and subsequent re-init.
7.5.6 ROCE: Independent Usage of Secondary Physical Function #
This feature enables zLinux running in an LPAR to use the Phisical Function (PF) that corresponds to the second oprt of a ConnectX-5/6 card even if the PF that corresponds to the first port is assigned to a different LPAR.
7.6 Virtualization #
The following new features are supported in SUSE Linux Enterprise Server 15 SP5 under KVM:
7.6.1 KVM: Enable GISA support for Secure Execution guests #
GISA (Guest Interruption State Area) is now supported for Secure Execution Guests. This allows the direct injection of interrupts into running VMs, which results in reduced processing overhead.
7.6.2 Enhanced Interpretation for PCI Functions #
For improving performance, the interpretive execution of the PCI store and PCI load instructions are enabled. Further improvement is achieved by enabling the Adapter-Event-Notification Interpretation which enables customers to run PCI I/O intensive workloads in KVM guests. This feature also allows KVM guests to use the Shared Memory Communications - Direct (SMC-D) protocol.
7.6.3 vfio-ap
enhancements #
This feature adds hotplug support, which allows to dynamically assign and remove crypto adapters to or from a running KVM guest. This additionally provides a tool to persistently define the configuration of crypto adapters and domains that are allowed for passthrough usage as well as the configuration of the matrix/vfio-ap devices to be passed through to avoid that customers have to reconfigure after every IPL.
7.6.4 Secure Execution guest dump encryption with customer keys, tool to process encrypted Secure Execution guest dumps #
These features implements dumps created in a way that can only be decrypted by the owner of the guest image and be used for problem determination hence mitigating the outcomes of situations where kdump
hypervisor-initiated dumps are not helpful.
7.6.5 KVM: Attestation support for Secure Execution (crypto), KVM: Secure Execution Attestation Userspace Tool #
Provides attestation support, for example, for external frameworks, specific deployment models or potentially regulatory requirements.
7.6.6 KVM: Provide virtual CPU topology to guests #
This feature allows to specify a virtual CPU topology which can help to configure the guest for better performance.
7.6.7 KVM: Allow long kernel command lines for Secure Execution guests and QEMU #
This feature allows Secure Execution guests to use larger command lines.
7.6.8 Allow to list persisted driverctl
definitions #
Updated driverctl
to version newer than 0.111 because the previous version did not allow to list persisted override definitions.
7.6.9 KVM: Enablement of device busid for subchannels #
Displaying the original CCW device numbers for` vfio-ap` devices improves the usability of vfio-ccw
device passthrough to KVM guests.
7.7 Kernel #
7.7.1 NVMe stand-alone dump support #
Supports the HW roadmap, full exploitation of NVMe on the IBM Z platform.
7.7.2 Support IBM z16 and LinuxONE 4 Processor-Activity-Instrumentation Facility #
Support for the Crypto Compliance feature of the IBM z16 and LinuxONE 4 Processor-Activity-Instrumentation Facility.
7.7.3 New CPU-MF Counters for IBM z16 and LinuxONE 4 #
Added new CPU-MF Counters for IBM z16 and LinuxONE 4.
7.7.4 Support Processor Activity Instrumentation Extension 1 #
Support for a new set of crypto performance counters of the IBM z16 and LinuxONE 4.
7.7.5 Add additional information to SCLP CPI #
Includes distribution, release number, and detailed kernel version in CPI data to be displayed on the HMC.
7.8 Miscellaneous #
7.8.1 Auto scale crashkernel
size with hardware changes #
kdump
now has a configuration option called KDUMP_AUTO_RESIZE
.
This option makes the boot-time init script call kdumptool-calibrate --shrink
.
This performs the same reservation size estimate that kdumptool calibrate
normally does and shrinks the memory reservation to the calculated value by writing to /sys/kernel/kexec_crash_size
.
YaST now has an option to turn this run-time auto-detection on.
The result will be a very large crashkernel=
value (around half the RAM) passed to the kernel and the reservation is reduced during boot using the KDUMP_AUTO_RESIZE
option.
7.8.2 Enabled installer to configure PCI-attached networking devices #
The installer now supports PCI-attached networking devices.
7.8.3 Removed ESCON from installer #
Removed the ESCON entry from the menu because it is no longer supported by the YaST module for network configuration.
8 Arm 64-bit-specific changes (AArch64) #
Information in this section applies to SUSE Linux Enterprise Server for Arm 15 SP5.
8.1 System-on-Chip driver enablement #
SUSE Linux Enterprise Server for Arm 15 SP5 includes driver enablement for the following System-on-Chip (SoC) chipsets:
AMD* Opteron* A1100
Ampere* X-Gene*, eMAG*, Altra*, Altra Max, AmpereOne*
AWS* Graviton, Graviton2, Graviton3
Broadcom* BCM2837/BCM2710, BCM2711
Fujitsu* A64FX
Huawei* Kunpeng* 916, Kunpeng 920
Marvell* ThunderX*, ThunderX2*; OCTEON TX*; Armada* 7040, Armada 8040
NVIDIA* Grace; Tegra* X1, Tegra X2, Xavier*, Orin; BlueField*, BlueField-2
NXP* i.MX 8M, 8M Mini; Layerscape* LS1012A, LS1027A/LS1017A, LS1028A/LS1018A, LS1043A, LS1046A, LS1088A, LS2080A/LS2040A, LS2088A, LX2160A
Qualcomm* Centriq* 2400
Rockchip RK3399
Socionext* SynQuacer* SC2A11
Xilinx* Zynq* UltraScale*+ MPSoC
Note
Driver enablement is done as far as available and requested. Refer to the following sections for any known limitations.
Some systems might need additional drivers for external chips, such as a Power Management Integrated Chip (PMIC), which may differ between systems with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
or the Embedded Base Boot Requirements (EBBR),
that is, the Unified Extensible Firmware Interface (UEFI) either
implementing the Advanced Configuration and Power Interface (ACPI) or
providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
will default to the Device Tree; the kernel command line argument acpi=force
can
override this default behavior.
Check for SUSE YES! certified systems, which have undergone compatibility testing.
8.2 New features #
8.2.1 Driver enablement for NVIDIA Orin #
SUSE Linux Enterprise Server for Arm 15 SP5 adds initial enablement for the NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin, Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM).
Warning: Firmware/kernel ABI break in NVIDIA JetPack 6.0 SDK
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5 changed the Application Binary Interface (ABI) for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary for NVIDIA Orin based systems.
A SUSE Linux Enterprise Server for Arm 15 SP5 kernel maintenance update adopts the behavior of the latest kernels and is fully compatible only with JetPack 6.0 and later:
Firmware | SLES 15 SP5 GM | SLES 15 SP5 QU1 | SLES 15 SP5 QU2 | SLES 15 SP5 QU3 |
---|---|---|---|---|
JetPack 5.x | + | + | + | ‒ |
JetPack 6.x | ‒ | ‒ | ‒ | + |
This is known to affect some peripherals on the following modules or systems:
NVIDIA Jetson AGX Orin Developer Kit:
USB Type-C controller
Ethernet controller
Camera sensors
PCIe endpoint mode
NVIDIA Jetson Orin NX:
Camera sensors
NVIDIA Jetson Orin Nano:
Camera sensors
For others, check with your system vendor.
For installed systems running JetPack firmware versions prior to 6.0, suggested steps are:
Update the kernel packages from the installed system, but do not reboot into the new kernel yet.
Shut the system down in order to enter its Recovery Mode.
Flash the latest JetPack firmware according to system vendor instructions. Be careful to not overwrite your SUSE Linux Enterprise Server for Arm installation. For example:
sudo ./flash.sh device-identifier-and-boot-medium external
Boot the system into the new kernel.
For new installations, consider these options:
SUSE Linux Enterprise Server for Arm 15 SP5 Quarterly Update 3 (QU3) media from SUSE Customer Center are expected to include the updated kernel suited for systems with NVIDIA JetPack 6.0 and later. Flash the latest vendor firmware before installing from these updated media.
In the meantime, with 15 SP5 Quarterly Update 2 and earlier media, consider installing from an earlier version of JetPack and following above update steps.
If a firmware downgrade is not available for your system, contact SUSE Customer Support for whether a custom kISO medium can be created.
SUSE Linux Enterprise Server for Arm 15 SP6 will only support NVIDIA JetPack 6.0 and later.
Drivers for the integrated, NVIDIA Ampere microarchitecture-based Graphics Processor Unit (GPU) are not included (Section 8.4.2, “No graphics drivers on NVIDIA Jetson”).
8.2.2 Driver enablement for NVIDIA Grace #
A SUSE Linux Enterprise Server for Arm 15 SP4 maintenance update added partial enablement for the NVIDIA Grace* SoC (T241).
SUSE Linux Enterprise Server for Arm 15 SP5 adds further enablement for the NVIDIA Grace SoC.
This also covers the NVIDIA Grace Hopper* SoC with an integrated, Hopper microarchitecture-based Graphics Processor Unit (GPU). Drivers for this integrated GPU are not included (Section 8.4.1, “No graphics drivers on NVIDIA Grace Hopper”).
NVIDIA recommend to use kernel-64kb
on NVIDIA Grace and Grace Hopper SoCs
(Section 8.3, “64K page size kernel flavor is supported”).
8.3 64K page size kernel flavor is supported #
SUSE Linux Enterprise Server for Arm 12 SP2 and later kernels have used a page size of 4K. This offers the widest compatibility also for small systems with little RAM, allowing to use Transparent Huge Pages (THP) where large pages make sense.
As a technology preview, SUSE Linux Enterprise Server for Arm 15 SP3 added a kernel flavor
64kb
, offering a page size of 64 KiB and physical/virtual address size
of 52 bits.
Same as the default
kernel flavor, it does not use preemption.
SUSE Linux Enterprise Server for Arm 15 SP5 largely removes this technology preview status,
offering support for kernel-64kb
on select platforms, such as
NVIDIA Grace* (Section 8.2.2, “Driver enablement for NVIDIA Grace”).
KVM virtualization remains a technology preview on this 64kb
kernel flavor
(Section 2.8.1.1, “KVM virtualization with 64K page size kernel flavor”).
Note: Default file system no longer needs to be changed
SUSE Linux Enterprise Server for Arm 15 SP4 and later allow the use of Btrfs based file systems with 4 KiB block size also with 64 KiB page size kernels.
Important: Swap needs to be re-initialized
After booting the 64K kernel, any swap partitions need to re-initialized to be usable.
To do this, run the swapon
command with the --fixpgsz
parameter on the swap partition.
Note that this process deletes data present in the swap partition (for example, suspend data).
In this example, the swap partition is on /dev/sdc1
:
swapon --fixpgsz /dev/sdc1
Warning: RAID 5 uses page size as stripe size
It is currently possible to configure stripe size by setting the following kernel parameter:
echo 16384 > /sys/block/md1/md/stripe_size
Keep in mind that stripe_size
must be in multiples of 4KB and not bigger than PAGE_SIZE
. Also, it is only supported on systems where PAGE_SIZE
is not 4096, such as arm64.
Avoid RAID 5 volumes when benchmarking 64K vs. 4K page size kernels.
See the Storage Guide for more information on software RAID.
Note: Cross-architecture compatibility considerations
The SUSE Linux Enterprise Server 15 SP5 kernels on x86-64 use 4K page size.
The SUSE Linux Enterprise Server for POWER 15 SP5 kernel uses 64K page size.
8.4 Known limitations #
8.4.1 No graphics drivers on NVIDIA Grace Hopper #
The NVIDIA Grace Hopper* System-on-Chip contains an integrated, Hopper microarchitecture-based Graphics Processor Unit (GPU).
SUSE Linux Enterprise Server for Arm 15 SP5 maintenance updates currently provide packages
nvidia-open-driver-G06-signed-kmp-default
and kernel-firmware-nvidia-gspx-G06
in version 535.104.05
, which does not yet enable NVIDIA Grace Hopper GH200.
Check for maintenance updates of those packages with version 545.29.02
or later,
or contact the system vendor or chip vendor NVIDIA for whether third-party
graphics drivers are available for SUSE Linux Enterprise Server for Arm 15 SP5.
Note: PCIe GPUs not affected
Discrete GPU cards with Hopper microarchitecture, such as NVIDIA H100, are already enabled in shipping package versions.
8.4.2 No graphics drivers on NVIDIA Jetson #
The NVIDIA* Tegra* System-on-Chip chipsets include an integrated Graphics Processor Unit (GPU).
SUSE Linux Enterprise Server for Arm 15 SP5 does not include graphics drivers for any of the NVIDIA Jetson*, NVIDIA IGX or NVIDIA DRIVE* platforms.
Contact the chip vendor NVIDIA for whether third-party graphics drivers are available for SUSE Linux Enterprise Server for Arm 15 SP5.
8.4.3 No DisplayPort graphics output on NXP LS1028A and LS1018A #
The NXP* Layerscape* LS1028A/LS1018A System-on-Chip contains an Arm* Mali*-DP500 Display Processor, whose output is connected to a DisplayPort* TX Controller (HDP-TX) based on Cadence* High Definition (HD) Display Intellectual Property (IP).
A Display Rendering Manager (DRM) driver for the Arm Mali-DP500 Display Processor is available as technology preview (Section 2.8.1.5, “mali-dp driver for Arm Mali Display Processors available”).
However, there was no HDP-TX physical-layer (PHY) controller driver ready yet. Therefore no graphics output will be available, for example, on the DisplayPort* connector of the NXP LS1028A Reference Design Board (RDB).
Contact the chip vendor NXP for whether third-party graphics drivers are available for SUSE Linux Enterprise Server for Arm 15 SP5.
Alternatively, contact your hardware vendor for whether a bootloader update
is available that implements graphics output, allowing to instead use efifb
framebuffer graphics in SUSE Linux Enterprise Server for Arm 15 SP5.
Note
The Vivante GC7000UL GPU driver (etnaviv
) is available as a
technology preview (Section 2.8.1.3, “etnaviv drivers for Vivante GPUs are available”).
9 Removed and deprecated features and packages #
This section lists features and packages that were removed from SUSE Linux Enterprise Server or will be removed in upcoming versions.
Note: Package and module changes in 15 SP5
For more information about all package and module changes since the last version, see Section 2.2.3, “Package and module changes in 15 SP5”.
9.1 Removed features and packages #
The following features and packages have been removed in this release.
The
samba-ad-dc-libs
package has been removed. It was previously available as technical preview.Setting up Kerberos with LDAP backend via YaST has been removed.
The thunderbolt-user-space package has been removed.
zypper-docker
has been removed.xpram
device driver has been removed.
Also see the following notes elsewhere:
9.2 Deprecated features and packages #
The following features and packages are deprecated and will be removed in a future version of SUSE Linux Enterprise Server.
PostgreSQL 13 has been deprecated and moved to the Legacy module.
TLS 1.0 and 1.1 are deprecated and will be removed in a future service pack of SUSE Linux Enterprise Server 15. For more information, see Section 5.7.1, “TLS 1.1 and 1.0 are no longer recommended for use”.
OSN support on IBM Z has been deprecated.
The
mkinitrd
wrapper has been replaced withdracut
everywhere and will be removed in the next major version of SUSE Linux Enterprise Server.The
lftp_wrapper
package has been deprecated and will be removed in the near future. It is still available as anupdate-alternative
forftp
, but it is no longed used by default. The default implementation offtp
is now thelftp
executable.Support for System V
init.d
scripts is deprecated and will be removed with the next major version of SUSE Linux Enterprise Server. In consequence, the/etc/init.d/halt.local
initscript,rcSERVICE
controls, andinsserv.conf
are also deprecated. For more information, see Section 5.10.4, “Support for System V init.d scripts is deprecated”.lftp_wrapper
is deprecated. Uselftp
directly instead.On the POWER architecture, transactional memory is deprecated. For more information, see Section 6.4.1, “Transactional memory is deprecated and disabled”.
The
opa-fmgui
package is not maintained upstream anymore. It has been deprecated, moved to the Legacy module, and will be removed in a future service pack.NIS is deprecated and will be removed with the next major version of SUSE Linux Enterprise Server. This includes packages implementing NIS, like
ypserv
. NIS code will be removed from SUSE tools and all NIS client code will be dropped with the next major version of SUSE Linux Enterprise Server.389 Directory Server replaces OpenLDAP as the LDAP directory service. OpenLDAP has been re-added to SLE 15 SP5 and SLE SP6 to prolong the time window for a migration to 389 Directory Server. Support for OpenLDAP on SLE 15 will end with the SLE 15 SP6 lifecycle. Future versions and service packs of SLE will not include OpenLDAP.
9.2.1 Public Cloud module deprecations #
The following packages in the Public Cloud module have been deprecated and will be removed in SUSE Linux Enterprise Server 15 SP6:
azure-cli-acr
azure-cli-acs
azure-cli-advisor
azure-cli-ams
azure-cli-appservice
azure-cli-backup
azure-cli-batch
azure-cli-batchai
azure-cli-billing
azure-cli-cdn
azure-cli-cloud
azure-cli-cognitiveservices
azure-cli-component
azure-cli-configure
azure-cli-consumption
azure-cli-container
azure-cli-cosmosdb
azure-cli-dla
azure-cli-dls
azure-cli-dms
azure-cli-eventgrid
azure-cli-eventhubs
azure-cli-extension
azure-cli-feedback
azure-cli-find
azure-cli-interactive
azure-cli-iot
azure-cli-keyvault
azure-cli-lab
azure-cli-monitor
azure-cli-network
azure-cli-profile
azure-cli-rdbms
azure-cli-redis
azure-cli-reservations
azure-cli-resource
azure-cli-role
azure-cli-search
azure-cli-servicebus
azure-cli-servicefabric
azure-cli-sql
azure-cli-storage
azure-cli-taskhelp
azure-cli-vm
blue-horizon-config-deploy-cap-eks
cfn-lint
gcimagebundle
google-cloud-sdk
google-compute-engine
google-daemon
google-startup-scripts
python-azure-storage
python-ravello-sdk
python-vsts-cd-manager
python-vsts
regionServiceClientConfigHP
regionServiceClientConfigSAPAzure
regionServiceClientConfigSAPEC2
regionServiceClientConfigSAPGCE
terraform-provider-aws
terraform-provider-azurerm
terraform-provider-external
terraform-provider-google
terraform-provider-helm
terraform-provider-kubernetes
terraform-provider-local
terraform-provider-null
terraform-provider-openstack
terraform-provider-random
terraform-provider-susepubliccloud
terraform-provider-template
terraform-provider-tls
WALinuxAgent
9.2.2 Miscellaneous #
sev-tool
has been deprecated. Usesevctl
instead.gnote
has been deprecated. Usebijiben
instead.We have switched from
openmpi2
toopenmpi4
as the defaultopenmpi
implementation. This is becauseopenmpi2
andopenmpi3
have been EOL for some time now. They will be removed in SLES 15 SP6.
10 Obtaining 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 https://www.suse.com/products/server/download/ on Medium 2. For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Send requests by e-mail to sle_source_request@suse.com. SUSE may charge a reasonable fee to recover distribution costs.
11 Legal notices #
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses. Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2010-2024 SUSE LLC.
This release notes document is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License (CC-BY-ND-4.0). You should have received a copy of the license along with this document. If not, see https://creativecommons.org/licenses/by-nd/4.0/.
SUSE has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at https://www.suse.com/company/legal/ and one or more additional patents or pending patent applications in the U.S. and other countries.
For SUSE trademarks, see the SUSE Trademark and Service Mark list (https://www.suse.com/company/legal/). All third-party trademarks are the property of their respective owners.