SUSE Linux Enterprise Server Release Notes #

For the most up-to-date version of the documentation for SUSE Linux Enterprise Server, see:

To read more about the differences and high-level changes between SUSE Linux Enterprise Server 16.0 and SUSE Linux Enterprise Server 15 SP7, see these documents:

To receive support, you need an appropriate subscription with SUSE. For more information, see https://www.suse.com/support/policy.html.

The following definitions apply:

For contracted customers and partners, SUSE Linux Enterprise Server is delivered with L3 support for all packages, except for the following:

SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.

To learn about supported features and limitations, refer to the following sections in this document:

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:

The version of Samba shipped with SUSE Linux Enterprise Server 16.1 includes support for the SMB over QUIC protocol as a technology preview. This protocol enables secure and efficient access to file shares over public networks.

SUSE Linux Enterprise Server 16.1 includes systemd-boot as a technology preview for Boot Loader Specification (BLS) support on UEFI systems.

The following limitations apply to this technology preview:

Full support is planned for a future release.

As a technology preview, remote and local attestation for AMD and Intel is available with the following packages in SUSE Linux Enterprise Server 16.1:

Full support is planned for a future release after validation.

Previously, only the SLE HA extension included HAProxy and Keepalived. The base SUSE Linux Enterprise Server distribution now includes both HAProxy and Keepalived. This change makes these packages available on standard installations without a separate High Availability subscription.

A new Base Container Image (BCI) is now available to build and run kernel modules on SUSE Linux Enterprise Server, comparable to the upstream driver-toolkit. The container includes the necessary kernel headers for both default and RT kernels on x86_64 and aarch64 architectures, providing a simple way to prototype and test drivers without giving access to SLE kernel binaries.

A SUSE Linux Enterprise Server containerdisk image is now available in the SUSE Registry (registry.suse.com). The image contains a minimal, bootable SUSE Linux Enterprise Server system in the OCI container format. Use the image to create virtual machines in cloud-native environments, for example SUSE Virtualization, Harvester, or KubeVirt.

To get the image, use the path registry.suse.com/suse/sles/16.1/containerdisk-minimal:latest.

An update of the util-linux package to version 2.42.2 fixes five critical security issues (CVE-2026-13595, CVE-2026-27456, CVE-2026-53612, CVE-2026-53613, CVE-2026-53614). These fixes change the behavior of mount operations for non-root processes. These changes stop privilege escalation and time-of-check-to-time-of-use (TOCTOU) race conditions.

The following changes apply:

If the system needs these restricted mount features, update to SUSE Linux Enterprise Server 16.2. The mountfd API in SUSE Linux Enterprise Server 16.2 uses file descriptors instead of paths, which makes operations safe against TOCTOU attacks.

For more information, see the upstream release notes at https://www.kernel.org/pub/linux/utils/util-linux/v2.42/v2.42.2-ReleaseNotes.

The boot menu of the live installation medium now has a timeout of 60 seconds. Previously, the timeout was ten seconds. This change provides more time to select options from the boot menu. This change does not affect the boot timeout of the installed system.

New installations of mozilla-nss now install p11-kit-nss-trust by default to provide libnssckbi.so. This change replaces the default installation of mozilla-nss-certs. The p11-kit-nss-trust package allows central configuration of system-wide root certificates. Firefox and other NSS consumers automatically inherit these central certificates. This avoids manual importing of enterprise certificates into individual profiles. Existing installations maintain their configuration during system upgrades. NSS static certificates remain available via the mozilla-nss-certs package and can be installed manually if required.

To simplify selection and validation, the number of pre-built immutable system images is now smaller. This release removes the Default image variant. Only the Base image variant remains available. Additionally, on the POWER architecture (ppc64le), this release removes the pre-built images for 512-byte sector sizes. Only images for 4096-byte (4 kB) sector sizes are now provided for ppc64le.

SUSE Linux Enterprise Server 16.1 updates Network UPS Tools (NUT) to version 2.8.5. This version upgrade introduces new hardware drivers, STARTTLS handling improvements, and support for name aliasing. A security patch resolves CVE-2026-54161, which prevented a potential remote command injection vulnerability in NOTIFYCMD. For a complete list of changes, see the upstream release notes.

The Berkeley Packet Filter (BPF) subsystem in the Linux kernel has been updated to align with the upstream kernel versions v6.13 through v6.18.

Key changes and system requirements:

This release updates BPF (Berkeley Packet Filter) tooling to the latest upstream versions. The following packages are updated:

These updates provide new features and bug fixes.

The Pressure Stall Information (PSI) metric collection is now enabled by default. In SLES 16.0, PSI was compiled into the kernel but disabled by default (CONFIG_PSI_DEFAULT_DISABLED=y). In SLES 16.1, this default has been changed to enabled (CONFIG_PSI_DEFAULT_DISABLED=n).

Enabling PSI allows system monitoring tools (such as sysstat version 12.7.5 included in SLES 16.1) to consume global PSI values out of the box. Benchmarking shows that the performance impact of PSI is negligible for almost all workloads, including database and compute-heavy tasks. A minor performance overhead (mostly between 2% and 8%) is restricted to scheduling- and wakeup-intensive microbenchmarks.

If you encounter performance regressions on scheduling-intensive workloads, you can disable PSI at boot time by passing psi=0 to the kernel command line.

High CPU load can make a container wait when it shares kernel locks. Previously, a container with CPU limits could keep a shared kernel lock when the system restricted its CPU usage. Because the container kept the lock, other containers had to wait. This waiting occurred even if the other containers had no CPU limits. The new task-based model changes this behavior. The kernel does not restrict a task when the task holds a critical lock. This change prevents delays and improves the separation of container workloads.

SUSE Linux Enterprise Server 16.1 now includes both the traditional zlib and the newer, high-performance zlib-ng compression libraries. The zlib-ng library provides substantial performance optimizations by utilizing modern CPU instruction sets. While both libraries are fully supported in this release, SUSE intends to only support zlib-ng in the future.

To provide a consistent administration experience, systemd service presets have been unified between standard and immutable installation modes. As part of this unification, several standard service presets have been newly enabled by default on standard installations, including the cloud-init stack, container-image-prune.timer, kubelet.service, and others. Similarly, standard service presets such as firewalld.service, chronyd.service, gdm.service, and virtualization helpers have been enabled by default on immutable installations. Only specific presets directly related to transactional system management (such as transactional-update.timer and health-checker.service) remain restricted to their respective modes.

SUSE Linux Enterprise Server now includes distrobox pre-installed by default, replacing the older toolbox utility. distrobox enables launching mutable, persistent containerized environments utilizing podman or docker. These environments are tightly integrated with the host system, sharing access to the home directory, external storage devices, audio and video streams, and graphical servers. This integration allows running and debugging tools from any Linux distribution directly within the terminal without modifying the underlying operating system.

With the introduction of the real-time kernel in SUSE Linux Enterprise Server 16.1, some third-party kernel modules are not compatible. The NVIDIA drivers are only built for the default kernel. Consequently, NVIDIA drivers are not available when running the real-time kernel.

SUSE Linux Enterprise Server 16.1 includes the Repository Mirroring Tool (RMT) server. RMT allows mirroring of SUSE repositories and client registration inside a private network. RMT has been updated to version 3, which is compatible with Ruby 3, ensuring long-term support.

To ensure consistent security and management preset behavior, firewalld is now enabled by default. This unification aligns the default service states across standard and immutable operating modes on SUSE Linux Enterprise Server 16.1. You can customize the firewalld presets or disable the service if necessary.

The iptables and nftables packages have been added to SLES Minimal Cloud and VMware VM images. This addition enables the successful provisioning of Rancher-deployed RKE2 and K3s clusters on SLES Minimal images without requiring manual package installation or Subscription Management (RMT) registration.

SUSE Linux Enterprise Server 16.1 introduces a transactional OS option. To support this option, clustering packages have been refactored to fully comply with Immutable Mode best practices. Specifically, the file placement and RPM scriptlets for crmsh, corosync-qdevice, resource-agents, and corosync have been updated. These packages can now be safely installed and updated via the transactional-update tool. This ensures they do not attempt to write to non-transactional or non-snapshotted areas (such as /var) during transactions.

The Agama installer supports SSH public key authentication for all accounts created during installation, including the first non-root account. This eliminates the need for temporary passwords and improves post-installation security.

The Agama installer uses JSON or Jsonnet profiles for automated installations. The agama config subcommand provides capabilities to export, convert, validate, and load these profiles. For detailed instructions, command usage, and complete working examples, see the Automated Installation Using Agama guide.

SAP installation patterns have been updated to optimize and simplify the installation process.

mkfs.xfs now automatically aligns the log stripe unit (lsunit) to the hardware’s reported minimum I/O size (such as a RAID controller’s stripe unit) to optimize physical disk layout. While this prevents unaligned write cycles on write-through storage devices, it may impact performance for certain types of fsync-heavy workloads on systems equipped with battery-backed or non-volatile write-back caches.

For those types of storage systems, performance can be optimized by manually setting the log stripe unit back to the block size during formatting (e.g., mkfs.xfs -l sunit=8 for 4KB). Alternatively, for highly demanding transactional workloads, utilizing a dedicated external XFS log on a non-striped device is recommended in order to entirely bypass storage layout trade-offs.

SLE maintains backward compatibility for legacy XFS v4 filesystems via the kernel configuration CONFIG_XFS_SUPPORT_V4=y. This support ensures uninterrupted access for existing environments. However, XFS v4 is deprecated, and creating new v4 filesystems is strongly discouraged.

September 2030 is the EOL target for upstream Linux kernel support for XFS v4. Any release post-September 2030 based on updated upstream kernels will omit XFS v4 support entirely. Legacy v4 filesystems will no longer be mountable on those versions.

Upgrading underlying filesystems from v4 to v5 is transparent to applications and requires no changes to userspace software.

To check the format version of an existing XFS filesystem, run:

xfs_info /path/to/mountpoint

An output including crc=1 indicates the modern v5 format, while crc=0 indicates the legacy v4 format.

There is no in-place or online upgrade path from XFS v4 to v5. Migration requires backing up data, reformatting the block device to XFS v5, and restoring the content. Migrating the root filesystem and any other critical data partitions requires planned downtime.

The operating system generates warnings when v4 format interaction occurs:

The alternate German keymap qwertz/de_alt_UTF-8 no longer supports characters in the Private Use Area (characters equal to or greater than U+F000). This change aligns the keymap with the upstream configuration and drops the custom legacy patch. Configurations that rely on custom characters mapped to this range require manual adjustment.

SUSE Linux Enterprise Server 16.1 includes Simple DirectMedia Layer 3 (SDL 3). Compatibility for SDL 2.0 applications is now provided through the sdl2-compat library layer. The legacy SDL2 package has been removed.

FreeRDP has been updated to version 3.26.0. This update introduces support for FIDO2 redirection ([MS-RDPEWA]), experimental AV1 codec extension, and performance improvements for SDL3 client drawing.

Performance Co-Pilot (PCP) has been upgraded from version 6.2.0 to 6.3.8. This version upgrade introduces AMD GPU metric monitoring support in pcp-htop. It adds Valkey support alongside Redis in libpcp_web. This version upgrade also resolves multiple security vulnerabilities, including CVE-2024-45769 (bsc#1230551). For a complete list of changes, see the upstream release notes at https://pcp.io/ and the package changelog.

SUSE Linux Enterprise Server 16.1 includes curl version 8.21.0. For a complete list of changes, see the curl 8.21.0 changelog.

SUSE Linux Enterprise Server 16.1 includes PHP version 8.5. For more information, see the PHP 8.5 release announcement and the PHP Packages Lifecycle documentation.

SUSE Linux Enterprise Server 16.1 includes the poppler PDF rendering library version 26.x.

This version update introduces several important changes for system administrators:

The GNU patch package will be updated to version 2.8 in SUSE Linux Enterprise Server 16.2. For a complete list of upcoming changes, see the GNU patch release announcement.

GNU patch version 2.8 enforces stricter header parsing. Ensure patch-generating tools do not inject NUL bytes or raw control characters into header lines or diff directives, as they are no longer accepted in version 2.8.

Direct root login to the Cockpit web interface is disabled by default. A login hint is now displayed upon a failed root login attempt to clarify that root access is disabled. The hint also provides instructions on logging in with a regular account, elevating privileges, or enabling root access via /etc/cockpit/disallowed-users.

SUSE Linux Enterprise Server 16.1 includes the new cockpit-bootloader package. This package provides a Cockpit interface module to configure bootloader settings. This module replaces the previous YaST bootloader configuration functionality. SUSE Linux Enterprise Server 16.1 also includes the required dependency package bootkitd.

Currently, SUSE Linux Enterprise Server ships only the Ansible runtime (ansible-core and ansible). SUSE Linux Enterprise Server 16.1 introduces a curated set of Ansible development and testing tools. These tools enable testing, linting, and building Ansible content.

The following packages are now included:

The distribution default has changed for a certain set of block devices: rotating disks that have only a single I/O queue. On SLES, such devices would previously be driven by the bfq I/O scheduler by default. Now we are using the same default as the kernel, which is mq-deadline for most devices, and none for some.

To help identify and mitigate Year 2038 (Y2K38) 32-bit time_t rollover issues, GCC now provides new compile-time warnings. These warnings highlight legacy 32-bit timestamp interactions in C/C++ code (such as file or network I/O using int types). It is recommended to review these warnings and update affected code to use 64-bit structures where necessary.

Running of the SAP software stack is not supported in immutable mode:

Note that this applies to traditional software. SAP software running in containers (like SAP Edge Integration Cell) is supported in immutable mode.

To better support immutable systems and transactional updates, the update-alternatives mechanism is no longer used to set the default PostgreSQL version. For more details on how to set the default PostgreSQL version, refer to the README.SUSE file provided in the postgresql main package.

The Agama installer supports both standard and immutable installation modes. Standard mode installs the system with a traditional read-write root directory. Immutable mode installs the system with a read-only root directory and enables transactional updates. The Agama configuration profile supports specifying the installation mode. The installation mode cannot be changed after the installation is complete.

To facilitate pre-installation configuration before launching the Agama installer, the Combustion tool is now included in the live installer image. This provides a convenient and reliable way to apply complex setups repeatedly without typing commands manually, which also covers advanced scenarios that standard graphical tools cannot handle.

Combustion does not run automatically by default. To run Combustion scripts, Combustion must be explicitly enabled by adding the rd.systemd.wants=firstboot.target boot option at the boot prompt. Ignition is not included because its configuration mechanism is unsuitable for live installer media, and Combustion is better suited for pre-installation scripting.

For root-over-NVMeoF setups, in SLES 16.0 and prior releases, the network interfaces were renamed to nbft0, nbft1, and so on. In SLES 16.1, on new installations, network interfaces keep their standard names.

The upstream kernel community has moved away from conservative scheduler preemption models (PREEMPT_NONE and PREEMPT_VOLUNTARY), and these models have been removed in kernel 7.0 for architectures that support PREEMPT_LAZY. To align with upstream changes, SUSE Linux Enterprise Server 16.1 switches the preemption model from PREEMPT_VOLUNTARY to PREEMPT_LAZY for all supported architectures, except for IBM Z (s390x), which lacks architectural support.

The PREEMPT_LAZY model provides a less conservative approach to preemption, while still being suitable for throughput-oriented workloads. If you experience performance issues with the new preemption model, you can optionally switch back to PREEMPT_VOLUNTARY by setting preempt=voluntary on the kernel command line.

Standard SUSE Linux Enterprise Server installations now include the real-time kernel (kernel-rt). Previously, the real-time kernel was only available on systems with the Transactional Server role. All system roles now support the real-time kernel. This change provides deterministic latency and predictable execution times for standard server installations.

The real-time kernel (kernel-rt) now maintains a stable kernel Application Binary Interface (kABI) during maintenance updates. This stability ensures that compatible third-party kernel modules do not require recompilation for every kernel update. Note that the real-time kernel and the default kernel do not share a common kABI. Therefore, drivers built for the default kernel cannot be used with the real-time kernel and must be built separately. While SUSE aims to keep the real-time kABI stable, rare technical requirements might still require changes in future updates.

RAID configuration is currently not supported through the installer Web UI. As a workaround, you can configure RAID either manually via the command line or by using JSON or JSONNet storage profiles. For more information, see https://agama-project.github.io/docs/user/reference/profile/storage. RAID support in the installer Web UI is planned for a future release.

Network time synchronization is now supported during both the early boot phase and the installation process. Specifying an NTP server IP address or hostname using the new rd.ntp=<server> kernel command-line parameter enables time synchronization before the installer launches, ensuring accurate log timestamps and correct HTTPS certificate validation. The Agama installer supports NTP configuration through a dedicated ntp section in the installer profile or via input fields in the user interface. Legacy AutoYaST ntp-client configurations are automatically converted into the native ntp configuration block on profile import. The configured NTP settings are written to the target system to persist after installation.

Kiwi now supports a new containerdisk format for building KubeVirt-compatible container images from OEM disk builds.

The new format combines qcow2 disk image creation with OCI container packaging in a single workflow. The resulting container image contains the disk image at /disk and includes the necessary KubeVirt metadata.

The disk format (e.g. qcow2, raw, vmdk) and target container transport (e.g. docker://, oci://, obs://) are configurable via the format parameter.

Example format syntax: format="oci:qcow2:docker://registry.example.com/kubevirt-disk:latest"

SSSD has been updated to version 2.10, which adds support for running as an unprivileged user instead of root. This allows containerized deployments to comply with security requirements that limit root privileges within containers.

By default, SSSD runs as root with the sssd supplementary group, which provides access to SSSD-owned files. To switch to unprivileged mode, create a systemd service override:

sudo systemctl edit sssd.service

Add the following:

[Service]
User=sssd
Group=sssd
SupplementaryGroups=

Then reload and restart the service:

sudo systemctl daemon-reload
sudo systemctl restart sssd

Note that running as an unprivileged user requires filesystem support for POSIX capabilities. On filesystems that do not support capabilities (such as NFS), SSSD must continue to run as root.

SELinux is now used as the primary LSM (Linux Security Module) as compared to AppArmor that was used previously.

Apart from SELinux, we have also enabled:

Previously, location of kernel or initrams would differ based on architecture.

Now these are stored in the same location regardless of architecture: boot/$arch/loader/

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

SUSE Linux Enterprise Server 16.1 continues to use Python 3.13 as the primary Python interpreter and stack. SUSE supports the primary Python interpreter for the entire product lifecycle. This interpreter provides the default /usr/bin/python3 executable and a full stack of python3- packages (approximately 700 packages).

Additionally, SUSE Linux Enterprise Server 16.1 introduces Python 3.14 as a short-term interpreter. SUSE supports the short-term interpreter for a limited two-year lifecycle (until November 2028). This interpreter only includes the runtime and essential package management tools (setuptools, venv, pip, and pipx). It does not include the full library stack. SUSE does not provide additional python314- packages.

The Python support strategy for SUSE Linux Enterprise Server 16 introduces a new short-term interpreter with each minor version (every year). The primary Python interpreter changes every odd minor version (for example, version 3.13 in 16.0 and 16.1, and version 3.15 in 16.3 and 16.4).

On HPE UV5 platforms (such as Google Compute Engine X4 bare-metal instances), the kernel clocksource watchdog previously monitored the Time Stamp Counter (TSC). This monitoring could cause system instability. Previously, preventing this instability required disabling the watchdog manually with the kernel command-line parameter tsc=nowatchdog and restarting the system. The kernel now automatically disables the clocksource watchdog for the TSC on all HPE UV5 platforms. Manual kernel parameter configuration and system restarts are no longer required.

SUSE Linux Enterprise Server 16.1 now supports Intel’s "Wildcat Lake-U" CPU platform. This hardware enablement includes updated graphics drivers for Intel Xe3 integrated graphics via the DRM kernel driver and Mesa 26.0.1. It adds device ID support for SMBus and I3C input/output interfaces. Additionally, this release enables Intel Platform Monitoring Technology (PMT) features, including Crash Log and Telemetry Aggregator, by adding the required VSEC device IDs.

SLES 16.1 includes driver enablement for the following System-on-Chip (SoC) chipsets:

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.

Non-blocking console (nbcon) support is enabled on the AArch64 architecture. The common AMBA PL011 serial console driver (amba-pl011) is converted to the new nbcon API. This allows the kernel to log messages atomically and reliably to the console even from non-maskable interrupt (NMI) contexts (such as during an nmi_panic). This ensures critical post-crash details are captured immediately without relying on legacy printing locks or threads.

SUSE Linux Enterprise Server includes libzpc version 2 for IBM Z.

The new libzpc-tools package provides the zpckey tool. Use zpckey to create and manage protected key origins, such as Secure Execution retrievable secrets. zpckey writes each key origin to a file. The OpenSSL provider module in the libzpc-provider package then reads the file. For more information, see the zpckey(1) man page.

Version 2 does not provide the libzpc C API as a shared library. Applications must use the OpenSSL provider module instead. The libzpc-legacy package provides the version 1 packages libzpc1 and libzpc-devel. The package is deprecated and will be removed in a future release.

SUSE Linux Enterprise Server now supports and automatically proposes Secure Boot during installation for ECKD DASD disks. This support is available on IBM z16, LinuxONE 4, or newer systems. The bootloader installer (zipl) automatically writes both secure boot (list-directed IPL) and non-secure boot (CCW) boot records. This ensures that the installed system remains bootable on older systems that do not support Secure Boot.

Support for IBM 3480 and 3590 tape drives, including the tape390_display and tape390_crypt tools, has been removed. In s390-tools, support for 3480 and 3590 FICON tape devices as well as the related tape390 utilities is removed. Other tape technologies are not affected by this removal. Virtual tape servers, such as the emulated IBM TS7700 Virtual Tape Server, continue to be supported via the tape.ko, tape_34xx.ko, and tape_3590.ko kernel modules.

The Agama installer now supports pervasive encryption (PAES) for storage volumes on IBM Z. The unattended storage JSON profile supports pervasive encryption properties, such as Crypto Express APQNs and key types. The storage schema includes the new apqns and keyType properties under the pervasiveLuks2 encryption configuration. During installation, the encryption planner assigns the specified APQN objects and key types to the planned encrypted devices.

Several IBM libraries and development tools now support the IBM z17 hardware platform. The system libraries libzdnn, libzpc, and libica include updates for the new hardware capabilities. Development and debugging tools, such as the GNU C Library (glibc) and Valgrind, also support the new processor instructions.

IPL has the following minimum system requirements, depending on the boot device to be IPLed:

If these requirements are not met, the system can be IPLed in non-secure mode only.

On PowerVM, configuring the PReP boot partition and the root file system on different storage subsystems causes boot failures. During POST, the system firmware initializes only the boot storage subsystem, which prevents GRUB from accessing secondary devices such as SAN multipath storage.

To avoid this issue, configure the PReP boot partition and the root file system on the same storage subsystem.

During kdump execution, attempting to capture a dump file to an NVMe over Fibre Channel (NVMe-FC) target on a Horton adapter fails. This issue occurs because the NVMe-FC driver maps numerous buffers for DMA, but not enough Translation Control Entries (TCEs) are freed from the Dynamic DMA Window (DDW) at kdump time. As a workaround, use Firmware-Assisted Dump (FADUMP), which is unaffected by this limitation.

If you install SUSE Linux Enterprise Server 16.1 with the GNOME desktop on LPAR and try to login via the HMC virtual terminal, the login may time out while entering your credentials.

To work around this issue, disable the Plymouth graphical boot screen by appending the boot parameter plymouth.enable=0 to the kernel command line.

The raw and qcow2 virtual machine guest images for the POWER architecture (ppc64le) are now built with cloud-init integration. Previously, provisioning virtual machines on KVM using these images required manual configuration steps. Automated initial guest provisioning is now fully supported.

SUSE Linux Enterprise Server 16.1 supports virtual persistent memory (vPMEM) in virtual machine guests on x86-64 and ppc64le. The guest kernel detects the vPMEM regions and loads the applicable driver without manual configuration. SUSE Linux Enterprise Server does not support physical Intel* Optane* Memory.

QEMU has been updated to version 11.0.0. For changes, see https://wiki.qemu.org/ChangeLog/11.0. For removed or deprecated features, see https://qemu-project.gitlab.io/qemu/about/removed-features.html and https://qemu-project.gitlab.io/qemu/about/deprecated.html.

libvirt has been updated to version 12.3.0, introducing modular daemons. For details, see https://libvirt.org/news.html#v12-3-0-2026-05-02.

The following virtualization utilities have been updated:

The following features and packages have been removed in this release.

The following features and packages are deprecated and will be removed in a future version of SUSE Linux Enterprise Server.