OpenSUSE Leap 16.1 Release Notes: Difference between revisions
Created openSUSE Leap 16.1 release notes |
Removed heading numbers |
||
| Line 3: | Line 3: | ||
openSUSE Leap is a modern, modular operating system suitable for both traditional IT and multimodal workloads. This document highlights major features, updates, and known limitations. | openSUSE Leap is a modern, modular operating system suitable for both traditional IT and multimodal workloads. This document highlights major features, updates, and known limitations. | ||
= | = About the release notes = | ||
These Release Notes are identical across all architectures, and the most recent version is always available online at [https://doc.opensuse.org/ https://doc.opensuse.org]. | These Release Notes are identical across all architectures, and the most recent version is always available online at [https://doc.opensuse.org/ https://doc.opensuse.org]. | ||
| Line 13: | Line 13: | ||
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. | 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. | ||
== | == Documentation and other information == | ||
For the most up-to-date version of the documentation for openSUSE Leap, see: | For the most up-to-date version of the documentation for openSUSE Leap, see: | ||
| Line 22: | Line 22: | ||
This section describes community-driven enhancements, features, and updates that extend the SLE core. These changes reflect the openSUSE project’s unique contributions, including desktop improvements, additional packages, and new workflows. | This section describes community-driven enhancements, features, and updates that extend the SLE core. These changes reflect the openSUSE project’s unique contributions, including desktop improvements, additional packages, and new workflows. | ||
= | = openSUSE Leap Community Additions = | ||
== | == Lifecycle == | ||
Each openSUSE Leap minor release is published once every 12 months. openSUSE Leap 16 provides maintenance updates over two minor releases, giving each release a full 24 months of community support. | Each openSUSE Leap minor release is published once every 12 months. openSUSE Leap 16 provides maintenance updates over two minor releases, giving each release a full 24 months of community support. | ||
| Line 34: | Line 34: | ||
For more than 24 months of support for a point release, the openSUSE migration tool makes it simple to move to SUSE Linux Enterprise, which provides decades of support. See [https://www.suse.com/support/policy.html Support Policy] and [https://www.suse.com/support/programs/long-term-service-pack-support.html Long Term Service Pack Support]. | For more than 24 months of support for a point release, the openSUSE migration tool makes it simple to move to SUSE Linux Enterprise, which provides decades of support. See [https://www.suse.com/support/policy.html Support Policy] and [https://www.suse.com/support/programs/long-term-service-pack-support.html Long Term Service Pack Support]. | ||
== | == openSUSE Leap Immutable replaces Leap Micro == | ||
<blockquote>'''Important:''' openSUSE Leap 16.1 installed in immutable mode is the direct successor of Leap Micro 6.2. There will be no Leap Micro 6.3.</blockquote> | <blockquote>'''Important:''' openSUSE Leap 16.1 installed in immutable mode is the direct successor of Leap Micro 6.2. There will be no Leap Micro 6.3.</blockquote> | ||
| Line 45: | Line 45: | ||
* Perform a clean installation using the immutable images from [https://get.opensuse.org/leap/16.1/ get.opensuse.org]. For convenience, the Immutable Self-install Image is available directly in the main download section. Other images, such as preconfigured, fully encrypted, VMware, and real-time images, are available in the Immutable section of the alternative downloads. | * Perform a clean installation using the immutable images from [https://get.opensuse.org/leap/16.1/ get.opensuse.org]. For convenience, the Immutable Self-install Image is available directly in the main download section. Other images, such as preconfigured, fully encrypted, VMware, and real-time images, are available in the Immutable section of the alternative downloads. | ||
== | == Upgrade from Leap 16.0 == | ||
For general upgrade instructions, refer to [https://en.opensuse.org/SDB:System_upgrade SDB:System_upgrade]. | For general upgrade instructions, refer to [https://en.opensuse.org/SDB:System_upgrade SDB:System_upgrade]. | ||
| Line 62: | Line 62: | ||
Future releases will use the Distribution Migration System (DMS, <code>suse-migration-services</code>) for upgrades of openSUSE Leap. This provides the same upgrade tool for both openSUSE Leap and SUSE Linux Enterprise Server. | Future releases will use the Distribution Migration System (DMS, <code>suse-migration-services</code>) for upgrades of openSUSE Leap. This provides the same upgrade tool for both openSUSE Leap and SUSE Linux Enterprise Server. | ||
== | == Migration from Leap 15.6 == | ||
The [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] (<code>zypper in opensuse-migration-tool</code>) is included as part of openSUSE Leap 15.6. Users migrating from older releases can run the tool from [https://github.com/openSUSE/opensuse-migration-tool Git repository]. | The [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] (<code>zypper in opensuse-migration-tool</code>) is included as part of openSUSE Leap 15.6. Users migrating from older releases can run the tool from [https://github.com/openSUSE/opensuse-migration-tool Git repository]. | ||
| Line 68: | Line 68: | ||
For more information, refer to [https://en.opensuse.org/SDB:System_upgrade SDB:System_upgrade]. | For more information, refer to [https://en.opensuse.org/SDB:System_upgrade SDB:System_upgrade]. | ||
== | == Installer and Desktop Environments == | ||
* openSUSE Leap 16 installer provides only Wayland variants of desktop environments. Xorg-based environments can be installed manually post-installation. | * openSUSE Leap 16 installer provides only Wayland variants of desktop environments. Xorg-based environments can be installed manually post-installation. | ||
=== | === LXQt 2.4 === | ||
The LXQt desktop environment is updated to version 2.4. The LXQt Wayland session (<code>lxqt-wayland-session</code>) is updated to version 0.4. The installer does not offer LXQt as an installation option; you can install it post-installation. LXQt will become an installer option in later releases after LXQt Miriway integration is completed (see [https://code.opensuse.org/leap/features/issue/192 https://code.opensuse.org/leap/features/issue/192]). | The LXQt desktop environment is updated to version 2.4. The LXQt Wayland session (<code>lxqt-wayland-session</code>) is updated to version 0.4. The installer does not offer LXQt as an installation option; you can install it post-installation. LXQt will become an installer option in later releases after LXQt Miriway integration is completed (see [https://code.opensuse.org/leap/features/issue/192 https://code.opensuse.org/leap/features/issue/192]). | ||
=== | === GDM no longer uses the xdm integration === | ||
The <code>gdm-xdm-integration</code> package is removed because openSUSE Leap no longer ships <code>update-alternatives</code>. A dedicated systemd service provided by the <code>gdm-systemd</code> package now starts GDM directly, instead of using the <code>xdm</code> wrapper script. Setting <code>DISPLAYMANAGER</code> in <code>/etc/sysconfig/displaymanager</code> no longer selects GDM as the display manager. | The <code>gdm-xdm-integration</code> package is removed because openSUSE Leap no longer ships <code>update-alternatives</code>. A dedicated systemd service provided by the <code>gdm-systemd</code> package now starts GDM directly, instead of using the <code>xdm</code> wrapper script. Setting <code>DISPLAYMANAGER</code> in <code>/etc/sysconfig/displaymanager</code> no longer selects GDM as the display manager. | ||
| Line 87: | Line 87: | ||
</pre> | </pre> | ||
=== | === NVIDIA and Graphics Issues with the Installation Image === | ||
Some users with NVIDIA GPUs may experience graphics-related issues during installation, such as [https://bugzilla.suse.com/show_bug.cgi?id=1247670 boo#1247670] where X server fails to start. This is due to the fact that openSUSE Leap install image contains <code>kernel-default-optional</code> and <code>kernel-default-extra</code> | Some users with NVIDIA GPUs may experience graphics-related issues during installation, such as [https://bugzilla.suse.com/show_bug.cgi?id=1247670 boo#1247670] where X server fails to start. This is due to the fact that openSUSE Leap install image contains <code>kernel-default-optional</code> and <code>kernel-default-extra</code> | ||
| Line 94: | Line 94: | ||
* For general graphics boot problems, use the option: <code>nomodeset</code> | * For general graphics boot problems, use the option: <code>nomodeset</code> | ||
=== | === Experimental Xfce Wayland session === | ||
Experimental Xfce Wayland session is available as an installation option. openSUSE Leap is one of the first distributions to provide Wayland support for [https://en.opensuse.org/Portal:Xfce Xfce]. We use <code>gtkgreet</code> with <code>greetd</code> as a Wayland-ready replacement for LightDM (used in the X11 variant). | Experimental Xfce Wayland session is available as an installation option. openSUSE Leap is one of the first distributions to provide Wayland support for [https://en.opensuse.org/Portal:Xfce Xfce]. We use <code>gtkgreet</code> with <code>greetd</code> as a Wayland-ready replacement for LightDM (used in the X11 variant). | ||
== | == Changes to the openSUSE Welcome == | ||
openSUSE Leap 16 now uses the <code>opensuse-welcome-launcher</code> to start the appropriate greeter application. This launcher, in combination with <code>gnome-tour</code> and <code>plasma-welcome</code>, replaces the legacy Qt5-based <code>opensuse-welcome</code>, which was previously the default greeter. | openSUSE Leap 16 now uses the <code>opensuse-welcome-launcher</code> to start the appropriate greeter application. This launcher, in combination with <code>gnome-tour</code> and <code>plasma-welcome</code>, replaces the legacy Qt5-based <code>opensuse-welcome</code>, which was previously the default greeter. | ||
| Line 104: | Line 104: | ||
The launcher also allows the openSUSE release team to update or refresh the displayed greeter via a package update, for example after a major GNOME update. To create a custom appliance without a welcome application, or to deploy a system where the greeter should never appear, remove <code>opensuse-welcome-launcher</code>. | The launcher also allows the openSUSE release team to update or refresh the displayed greeter via a package update, for example after a major GNOME update. To create a custom appliance without a welcome application, or to deploy a system where the greeter should never appear, remove <code>opensuse-welcome-launcher</code>. | ||
== | == Automated NVIDIA Driver and Repository Setup == | ||
On supported GPUs, NVIDIA’s open driver is installed by default along with the NVIDIA graphics driver repository. In openSUSE Leap 16, user-space drivers are also automatically installed, enabling graphical acceleration out of the box. | On supported GPUs, NVIDIA’s open driver is installed by default along with the NVIDIA graphics driver repository. In openSUSE Leap 16, user-space drivers are also automatically installed, enabling graphical acceleration out of the box. | ||
== | == Security == | ||
=== | === AppArmor === | ||
AppArmor has been updated from version 3.1 to 4.1. | AppArmor has been updated from version 3.1 to 4.1. | ||
| Line 117: | Line 117: | ||
* Version [https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.1.0 4.1] introduced the <code>priority=<number></code> rule prefix, which allows overriding rules. | * Version [https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.1.0 4.1] introduced the <code>priority=<number></code> rule prefix, which allows overriding rules. | ||
=== | === AppArmor not available by default on new installations === | ||
<blockquote>'''Warning:''' AppArmor is no longer available in SUSE Linux Enterprise 16.0. Leap users cannot select AppArmor as the Linux Security Module (LSM) during a new installation. AppArmor can still be enabled post-installation. For instructions, refer to [https://en.opensuse.org/SDB:AppArmor#Switching_from_SELinux_to_AppArmor_for_Leap_16.0_and_Tumbleweed AppArmor wiki page].</blockquote> | <blockquote>'''Warning:''' AppArmor is no longer available in SUSE Linux Enterprise 16.0. Leap users cannot select AppArmor as the Linux Security Module (LSM) during a new installation. AppArmor can still be enabled post-installation. For instructions, refer to [https://en.opensuse.org/SDB:AppArmor#Switching_from_SELinux_to_AppArmor_for_Leap_16.0_and_Tumbleweed AppArmor wiki page].</blockquote> | ||
| Line 123: | Line 123: | ||
Users migrating manually from 15.6 will retain AppArmor by default. Users migrating with [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] will be prompted to either switch to SELinux or preserve AppArmor during post-migration. | Users migrating manually from 15.6 will retain AppArmor by default. Users migrating with [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] will be prompted to either switch to SELinux or preserve AppArmor during post-migration. | ||
== | == Steam == | ||
<blockquote>'''Warning:''' The <code>Steam</code> package has been removed from the [https://en.opensuse.org/Package_repositories#Non-OSS Non-OSS repository] due to limited 32-bit library support. Users are advised to install it via [https://en.opensuse.org/Steam#Flatpak Flatpak].</blockquote> | <blockquote>'''Warning:''' The <code>Steam</code> package has been removed from the [https://en.opensuse.org/Package_repositories#Non-OSS Non-OSS repository] due to limited 32-bit library support. Users are advised to install it via [https://en.opensuse.org/Steam#Flatpak Flatpak].</blockquote> | ||
| Line 130: | Line 130: | ||
* SELinux users may also need <code>selinux-policy-targeted-gaming</code>. For details, refer to [https://en.opensuse.org/Portal:SELinux/Common_issues#Steam_Proton,_Bottles,_WINE,_Lutris,_not_working SELinux wiki page]. | * SELinux users may also need <code>selinux-policy-targeted-gaming</code>. For details, refer to [https://en.opensuse.org/Portal:SELinux/Common_issues#Steam_Proton,_Bottles,_WINE,_Lutris,_not_working SELinux wiki page]. | ||
== | == Wine == | ||
openSUSE Leap includes <code>wine</code> 10.10, available only in the [https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#shared-wow64 wow64] flavor. Users requiring 32-bit binary execution should consider using the Flatpak version or a similar solution. | openSUSE Leap includes <code>wine</code> 10.10, available only in the [https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#shared-wow64 wow64] flavor. Users requiring 32-bit binary execution should consider using the Flatpak version or a similar solution. | ||
== | == Cockpit desktop launcher == | ||
The new <code>cockpit-client-launcher</code> package provides a desktop launcher for the Cockpit GTK client without requiring Flatpak. It connects to the locally installed <code>cockpit-ws</code> service and automatically detects the port configured in <code>cockpit.socket</code>. If Cockpit is not running, the launcher offers to start <code>cockpit.socket</code> and to open the port in the firewall. | The new <code>cockpit-client-launcher</code> package provides a desktop launcher for the Cockpit GTK client without requiring Flatpak. It connects to the locally installed <code>cockpit-ws</code> service and automatically detects the port configured in <code>cockpit.socket</code>. If Cockpit is not running, the launcher offers to start <code>cockpit.socket</code> and to open the port in the firewall. | ||
| Line 142: | Line 142: | ||
</pre> | </pre> | ||
== | == Networking == | ||
=== | === Broken libvirt networking when using Docker === | ||
<blockquote>'''Warning:''' If networking inside libvirt-managed virtual machines fails while Docker is running, it is likely due to Docker not supporting <code>nftables</code>.</blockquote> | <blockquote>'''Warning:''' If networking inside libvirt-managed virtual machines fails while Docker is running, it is likely due to Docker not supporting <code>nftables</code>.</blockquote> | ||
| Line 166: | Line 166: | ||
This restores networking for libvirt VMs while Docker is active. | This restores networking for libvirt VMs while Docker is active. | ||
== | == GNU Health == | ||
[https://www.gnuhealth.org/ GNU Health] has been updated to major release 5.0.2. The underlying ERP framework, Tryton, has been updated to LTS version 7.0. Functional improvements include enhanced medical image workflows and better integration with Orthanc 1.12.9 (PACS server). | [https://www.gnuhealth.org/ GNU Health] has been updated to major release 5.0.2. The underlying ERP framework, Tryton, has been updated to LTS version 7.0. Functional improvements include enhanced medical image workflows and better integration with Orthanc 1.12.9 (PACS server). | ||
== | == PipeWire replaces PulseAudio == | ||
openSUSE Leap 16.1 uses PipeWire by default. Users upgrading from previous releases should be automatically migrated from PulseAudio. <code>opensuse-migration-tool</code> provides a post-migration script if migration does not occur automatically. | openSUSE Leap 16.1 uses PipeWire by default. Users upgrading from previous releases should be automatically migrated from PulseAudio. <code>opensuse-migration-tool</code> provides a post-migration script if migration does not occur automatically. | ||
| Line 176: | Line 176: | ||
If experiencing audio issues, ensure you are not using the <code>wireplumber-video-only-profile</code>. For details, refer to [https://en.opensuse.org/openSUSE:Pipewire#Installation PipeWire#Installation] for details. | If experiencing audio issues, ensure you are not using the <code>wireplumber-video-only-profile</code>. For details, refer to [https://en.opensuse.org/openSUSE:Pipewire#Installation PipeWire#Installation] for details. | ||
== | == Hexchat drop == | ||
Hexchat IRC client has been dropped as the [https://github.com/hexchat/hexchat upstream project] is archived. Alternatives include [https://software.opensuse.org/package/polari Polari] or the Flatpak version: [https://flathub.org/en/apps/io.github.Hexchat Flatpak]. | Hexchat IRC client has been dropped as the [https://github.com/hexchat/hexchat upstream project] is archived. Alternatives include [https://software.opensuse.org/package/polari Polari] or the Flatpak version: [https://flathub.org/en/apps/io.github.Hexchat Flatpak]. | ||
== | == nmap moved to non-oss repository == | ||
In openSUSE Leap 16 nmap was moved to the non-free repository due to its problematic licencing. To install it, first enable the non-free repository and then install the package: | In openSUSE Leap 16 nmap was moved to the non-free repository due to its problematic licencing. To install it, first enable the non-free repository and then install the package: | ||
| Line 191: | Line 191: | ||
</pre> | </pre> | ||
== | == Configuring boot entry with serial console == | ||
See [https://en.opensuse.org/SDB:SerialConsole https://en.opensuse.org/SDB:SerialConsole] for guidance. | See [https://en.opensuse.org/SDB:SerialConsole https://en.opensuse.org/SDB:SerialConsole] for guidance. | ||
== | == Memory limits in Java containers == | ||
Java containers using <code>-XX:MaxRAMPercentage</code> may not detect memory limits correctly on kernel 6.12 due to an upstream OpenJDK issue. | Java containers using <code>-XX:MaxRAMPercentage</code> may not detect memory limits correctly on kernel 6.12 due to an upstream OpenJDK issue. | ||
| Line 201: | Line 201: | ||
As a workaround, use fixed <code>-Xmx</code> values instead. This issues is fixed in OpenJDK 25. | As a workaround, use fixed <code>-Xmx</code> values instead. This issues is fixed in OpenJDK 25. | ||
= | = SUSE Linux Enterprise Core = | ||
This section describes the enterprise-grade foundation of openSUSE Leap, based on SUSE Linux Enterprise. Content here is adapted from the SUSE Linux Enterprise release notes to reflect core functionality, security updates, and enterprise features that openSUSE Leap inherits. | This section describes the enterprise-grade foundation of openSUSE Leap, based on SUSE Linux Enterprise. Content here is adapted from the SUSE Linux Enterprise release notes to reflect core functionality, security updates, and enterprise features that openSUSE Leap inherits. | ||
== | == What’s new? == | ||
=== | === Changes from SLES 15 Core === | ||
To read more about the differences and high-level changes between SUSE Linux 16.0 and SUSE Linux Enterprise 15, see these documents: | To read more about the differences and high-level changes between SUSE Linux 16.0 and SUSE Linux Enterprise 15, see these documents: | ||
| Line 214: | Line 214: | ||
* [https://documentation.suse.com/sles/16.0/html/SLE-comparison/ https://documentation.suse.com/sles/16.0/html/SLE-comparison/] | * [https://documentation.suse.com/sles/16.0/html/SLE-comparison/ https://documentation.suse.com/sles/16.0/html/SLE-comparison/] | ||
== | == Support and lifecycle == | ||
openSUSE Leap is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services. | openSUSE Leap is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services. | ||
| Line 232: | Line 232: | ||
For exact lifecycle dates, see [https://www.suse.com/lifecycle/#suse-linux-enterprise-server-16 SUSE Linux Enterprise Server Lifecycle] and [https://www.suse.com/lifecycle/#suse-linux-enterprise-server-for-sap-applications-16 SUSE Linux Enterprise Server for SAP applications Lifecycle]. For more information, see [https://www.suse.com/support/policy.html Support Policy], [https://www.suse.com/products/long-term-service-pack-support/ Long Term Support], and [https://documentation.suse.com/sles/16.0/html/SLE-packages-lifecycle/index.html Lifecycles of SUSE Linux Enterprise Components]. | For exact lifecycle dates, see [https://www.suse.com/lifecycle/#suse-linux-enterprise-server-16 SUSE Linux Enterprise Server Lifecycle] and [https://www.suse.com/lifecycle/#suse-linux-enterprise-server-for-sap-applications-16 SUSE Linux Enterprise Server for SAP applications Lifecycle]. For more information, see [https://www.suse.com/support/policy.html Support Policy], [https://www.suse.com/products/long-term-service-pack-support/ Long Term Support], and [https://documentation.suse.com/sles/16.0/html/SLE-packages-lifecycle/index.html Lifecycles of SUSE Linux Enterprise Components]. | ||
=== | === Support statement for openSUSE Leap === | ||
To receive support, you need an appropriate subscription with SUSE. For more information, see [https://forums.opensuse.org/ https://forums.opensuse.org]. | To receive support, you need an appropriate subscription with SUSE. For more information, see [https://forums.opensuse.org/ https://forums.opensuse.org]. | ||
| Line 244: | Line 244: | ||
For contracted customers and partners, openSUSE Leap is delivered with L3 support for all packages, except for the following: | For contracted customers and partners, openSUSE Leap is delivered with L3 support for all packages, except for the following: | ||
* Technology Previews, see [[# | * Technology Previews, see [[#Technology previews|“Technology previews”]] | ||
* Sound, graphics, fonts and artwork | * Sound, graphics, fonts and artwork | ||
* Packages that require an additional customer contract, see [[# | * Packages that require an additional customer contract, see [[#Software requiring specific contracts|“Software requiring specific contracts”]] | ||
* Some packages shipped as part of the module ''Workstation Extension'' are L2-supported only | * Some packages shipped as part of the module ''Workstation Extension'' are L2-supported only | ||
* Packages with names ending in <code>-devel</code> (containing header files and similar developer resources) will only be supported together with their main packages. | * Packages with names ending in <code>-devel</code> (containing header files and similar developer resources) will only be supported together with their main packages. | ||
| Line 252: | Line 252: | ||
SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled. | SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled. | ||
=== | === General support === | ||
To learn about supported features and limitations, refer to the following sections in this document: | To learn about supported features and limitations, refer to the following sections in this document: | ||
* [[# | * [[#Virtualization|“Virtualization”]] | ||
* [[# | * [[#Removed and deprecated features and packages|“Removed and deprecated features and packages”]] | ||
==== | ==== Software requiring specific contracts ==== | ||
Certain software delivered as part of openSUSE Leap may require an external contract. Check the support status of individual packages using the RPM metadata that can be viewed with <code>rpm</code> or <code>zypper</code>. | Certain software delivered as part of openSUSE Leap may require an external contract. Check the support status of individual packages using the RPM metadata that can be viewed with <code>rpm</code> or <code>zypper</code>. | ||
| Line 265: | Line 265: | ||
Currently, there are no major packages and groups of packages affected by this. | Currently, there are no major packages and groups of packages affected by this. | ||
==== | ==== Software under GNU AGPL ==== | ||
openSUSE Leap 16.1 (and the SUSE Linux Enterprise modules) includes the following software that is shipped ''only'' under a GNU AGPL software license: | openSUSE Leap 16.1 (and the SUSE Linux Enterprise modules) includes the following software that is shipped ''only'' under a GNU AGPL software license: | ||
| Line 278: | Line 278: | ||
* ArgyllCMS | * ArgyllCMS | ||
=== | === 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 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. | ||
| Line 289: | Line 289: | ||
* 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. | * 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. | ||
=== | === Technology Previews for scheduling === | ||
SUSE Linux Enterprise Server with the real-time kernel enables the <code>SCHED_DEADLINE</code> scheduling class as a Technology Preview (best-effort support). This scheduler predicts task scheduling based on application deadlines, which is particularly useful for realtime workload. | SUSE Linux Enterprise Server with the real-time kernel enables the <code>SCHED_DEADLINE</code> scheduling class as a Technology Preview (best-effort support). This scheduler predicts task scheduling based on application deadlines, which is particularly useful for realtime workload. | ||
=== | === SMB over QUIC support in Samba (technology preview) === | ||
The version of Samba shipped with openSUSE Leap 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. | The version of Samba shipped with openSUSE Leap 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. | ||
=== | === Boot Loader Specification (BLS) support with systemd-boot (technology preview) === | ||
openSUSE Leap 16.1 includes systemd-boot as a technology preview for Boot Loader Specification (BLS) support on UEFI systems. | openSUSE Leap 16.1 includes systemd-boot as a technology preview for Boot Loader Specification (BLS) support on UEFI systems. | ||
| Line 310: | Line 310: | ||
Full support is planned for a future release. | Full support is planned for a future release. | ||
=== | === Confidential Computing Remote and Local Attestation (technology preview) === | ||
As a technology preview, remote and local attestation for AMD and Intel is available with the following packages in openSUSE Leap 16.1: | As a technology preview, remote and local attestation for AMD and Intel is available with the following packages in openSUSE Leap 16.1: | ||
| Line 325: | Line 325: | ||
Full support is planned for a future release after validation. | Full support is planned for a future release after validation. | ||
== | == Included packages and quarterly updates == | ||
Both the online medium and the full medium are the same for all SUSE Linux 16.1 products and only need to be downloaded once. As the full medium includes all packages of the whole SUSE Linux 16.1 family, be aware that depending on your subscription the list of packages supported by SUSE varies. You can check packages included in products on [https://scc.suse.com/ https://scc.suse.com]. | Both the online medium and the full medium are the same for all SUSE Linux 16.1 products and only need to be downloaded once. As the full medium includes all packages of the whole SUSE Linux 16.1 family, be aware that depending on your subscription the list of packages supported by SUSE varies. You can check packages included in products on [https://scc.suse.com/ https://scc.suse.com]. | ||
| Line 331: | Line 331: | ||
Installation media, VM images and public cloud images are usually refreshed every 3 months (Quarterly Updates). | Installation media, VM images and public cloud images are usually refreshed every 3 months (Quarterly Updates). | ||
== | == Supported upgrade and migration paths == | ||
openSUSE Leap 16.1 supports upgrading from openSUSE Leap 16.0, as well as migrating from preceding SUSE product releases. | openSUSE Leap 16.1 supports upgrading from openSUSE Leap 16.0, as well as migrating from preceding SUSE product releases. | ||
| Line 344: | Line 344: | ||
For detailed instructions, pre-upgrade checklists, and step-by-step migration procedures, see the [https://documentation.suse.com/sles/16.1/html/SLES-upgrading/ Upgrade Guide]. | For detailed instructions, pre-upgrade checklists, and step-by-step migration procedures, see the [https://documentation.suse.com/sles/16.1/html/SLES-upgrading/ Upgrade Guide]. | ||
== | == Upgrade and migration checklist == | ||
Before upgrading to openSUSE Leap 16.1, review the following checklist of potential migration issues and preparation steps. | Before upgrading to openSUSE Leap 16.1, review the following checklist of potential migration issues and preparation steps. | ||
=== | === Before upgrading === | ||
* [[# | * [[#Immutable mode is unsupported for SAP workloads|“Immutable mode is unsupported for SAP workloads”]] | ||
* [[# | * [[#Supported upgrade and migration paths|“Supported upgrade and migration paths”]] | ||
=== | === During upgrade === | ||
* [[# | * [[#Agama live image includes Combustion|“Agama live image includes Combustion”]] | ||
=== | === After upgrading === | ||
* [[# | * [[#update-alternatives no longer used for PostgreSQL|“<code>update-alternatives</code> no longer used for PostgreSQL”]]. | ||
== | == Changes affecting all architectures == | ||
* <code>rasdaemon</code> has been updated to version 0.8.4. This version supports machine checks related to CXL memory. Since Intel® Optane™ Memory products have reached End of Life (EOL), openSUSE Leap 16.1 does not support them either. | * <code>rasdaemon</code> has been updated to version 0.8.4. This version supports machine checks related to CXL memory. Since Intel® Optane™ Memory products have reached End of Life (EOL), openSUSE Leap 16.1 does not support them either. | ||
=== | === <code>HAProxy</code> and <code>Keepalived</code> moved to <code>SUSE Linux Enterprise Server</code> === | ||
Previously, only the <code>SLE HA</code> extension included <code>HAProxy</code> and <code>Keepalived</code>. The base <code>SUSE Linux Enterprise Server</code> distribution now includes both <code>HAProxy</code> and <code>Keepalived</code>. This change makes these packages available on standard installations without a separate High Availability subscription. | Previously, only the <code>SLE HA</code> extension included <code>HAProxy</code> and <code>Keepalived</code>. The base <code>SUSE Linux Enterprise Server</code> distribution now includes both <code>HAProxy</code> and <code>Keepalived</code>. This change makes these packages available on standard installations without a separate High Availability subscription. | ||
=== | === SLE BCI for kernel modules (Driver Toolkit) === | ||
A new Base Container Image (BCI) is now available to build and run kernel modules on openSUSE Leap, comparable to the upstream <code>driver-toolkit</code>. The container includes the necessary kernel headers for both default and RT kernels on <code>x86_64</code> and <code>aarch64</code> architectures, providing a simple way to prototype and test drivers without giving access to SLE kernel binaries. | A new Base Container Image (BCI) is now available to build and run kernel modules on openSUSE Leap, comparable to the upstream <code>driver-toolkit</code>. The container includes the necessary kernel headers for both default and RT kernels on <code>x86_64</code> and <code>aarch64</code> architectures, providing a simple way to prototype and test drivers without giving access to SLE kernel binaries. | ||
=== | === openSUSE Leap containerdisk image now available === | ||
A openSUSE Leap containerdisk image is now available in the SUSE Registry (<code>registry.suse.com</code>). The image contains a minimal, bootable openSUSE Leap system in the OCI container format. Use the image to create virtual machines in cloud-native environments, for example SUSE Virtualization, Harvester, or KubeVirt. | A openSUSE Leap containerdisk image is now available in the SUSE Registry (<code>registry.suse.com</code>). The image contains a minimal, bootable openSUSE Leap system in the OCI container format. Use the image to create virtual machines in cloud-native environments, for example SUSE Virtualization, Harvester, or KubeVirt. | ||
| Line 379: | Line 379: | ||
To get the image, use the path <code>registry.suse.com/suse/sles/16.1/containerdisk-minimal:latest</code>. | To get the image, use the path <code>registry.suse.com/suse/sles/16.1/containerdisk-minimal:latest</code>. | ||
=== | === <code>debugfs</code> is not mounted by default === | ||
To reduce the attack surface and comply with Common Criteria requirements, openSUSE Leap 16.1 does not automatically mount <code>debugfs</code> at <code>/sys/kernel/debug</code> during boot. The <code>debugfs</code> file system can expose Address Space Layout Randomization (ASLR) information. | To reduce the attack surface and comply with Common Criteria requirements, openSUSE Leap 16.1 does not automatically mount <code>debugfs</code> at <code>/sys/kernel/debug</code> during boot. The <code>debugfs</code> file system can expose Address Space Layout Randomization (ASLR) information. | ||
| Line 395: | Line 395: | ||
</pre> | </pre> | ||
=== | === Support for AMD GPU Operator === | ||
The AMD GPU Operator automates the management and configuration of AMD GPUs in Kubernetes clusters. openSUSE Leap 16.1 supports deploying the upstream AMD GPU Operator. The operator uses prebuilt <code>amdgpu</code> driver container images from the SUSE Registry (<code>registry.suse.com</code>). Kernel Module Management (KMM) loads the driver modules onto the host without recompiling the drivers across kernel updates within the same Leap codestream. | The AMD GPU Operator automates the management and configuration of AMD GPUs in Kubernetes clusters. openSUSE Leap 16.1 supports deploying the upstream AMD GPU Operator. The operator uses prebuilt <code>amdgpu</code> driver container images from the SUSE Registry (<code>registry.suse.com</code>). Kernel Module Management (KMM) loads the driver modules onto the host without recompiling the drivers across kernel updates within the same Leap codestream. | ||
| Line 401: | Line 401: | ||
To deploy the operator on RKE2, see the [https://documentation.suse.com/cloudnative/rke2/latest/en/add-ons/gpu_operators.html#_deploy_amd_operator RKE2 documentation]. For installation instructions and configuration options, see the [https://instinct.docs.amd.com/projects/gpu-operator/en/latest/ AMD GPU Operator documentation]. | To deploy the operator on RKE2, see the [https://documentation.suse.com/cloudnative/rke2/latest/en/add-ons/gpu_operators.html#_deploy_amd_operator RKE2 documentation]. For installation instructions and configuration options, see the [https://instinct.docs.amd.com/projects/gpu-operator/en/latest/ AMD GPU Operator documentation]. | ||
=== | === Security update and changes in mount behavior for <code>util-linux</code> === | ||
An update of the <code>util-linux</code> 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. | An update of the <code>util-linux</code> 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. | ||
| Line 416: | Line 416: | ||
For more information, see the upstream release notes at [https://www.kernel.org/pub/linux/utils/util-linux/v2.42/v2.42.2-ReleaseNotes https://www.kernel.org/pub/linux/utils/util-linux/v2.42/v2.42.2-ReleaseNotes]. | For more information, see the upstream release notes at [https://www.kernel.org/pub/linux/utils/util-linux/v2.42/v2.42.2-ReleaseNotes https://www.kernel.org/pub/linux/utils/util-linux/v2.42/v2.42.2-ReleaseNotes]. | ||
=== | === Increased timeout for installer boot menu === | ||
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. | 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. | ||
=== | === <code>mozilla-nss</code> favors <code>p11-kit-nss-trust</code> over <code>mozilla-nss-certs</code> by default === | ||
New installations of <code>mozilla-nss</code> now install <code>p11-kit-nss-trust</code> by default to provide <code>libnssckbi.so</code>. This change replaces the default installation of <code>mozilla-nss-certs</code>. The <code>p11-kit-nss-trust</code> 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 <code>mozilla-nss-certs</code> package and can be installed manually if required. | New installations of <code>mozilla-nss</code> now install <code>p11-kit-nss-trust</code> by default to provide <code>libnssckbi.so</code>. This change replaces the default installation of <code>mozilla-nss-certs</code>. The <code>p11-kit-nss-trust</code> 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 <code>mozilla-nss-certs</code> package and can be installed manually if required. | ||
=== | === Reduced set of pre-built immutable system images === | ||
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. | 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. | ||
=== | === Network UPS Tools (NUT) updated to version 2.8.5 === | ||
openSUSE Leap 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 <code>NOTIFYCMD</code>. For a complete list of changes, see the upstream release notes. | openSUSE Leap 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 <code>NOTIFYCMD</code>. For a complete list of changes, see the upstream release notes. | ||
=== | === Linux kernel BPF subsystem updated to match upstream v6.13 to v6.18 === | ||
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. | 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. | ||
| Line 442: | Line 442: | ||
* See the upstream kernel changelogs from [https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.13 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.13] through [https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18]. | * See the upstream kernel changelogs from [https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.13 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.13] through [https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18]. | ||
=== | === BPF tooling updated to the latest upstream versions === | ||
This release updates BPF (Berkeley Packet Filter) tooling to the latest upstream versions. The following packages are updated: | This release updates BPF (Berkeley Packet Filter) tooling to the latest upstream versions. The following packages are updated: | ||
| Line 453: | Line 453: | ||
These updates provide new features and bug fixes. | These updates provide new features and bug fixes. | ||
=== | === Pressure Stall Information (PSI) enabled by default === | ||
The Pressure Stall Information (PSI) metric collection is now enabled by default. In Leap 16.0, PSI was compiled into the kernel but disabled by default (<code>CONFIG_PSI_DEFAULT_DISABLED=y</code>). In Leap 16.1, this default has been changed to enabled (<code>CONFIG_PSI_DEFAULT_DISABLED=n</code>). | The Pressure Stall Information (PSI) metric collection is now enabled by default. In Leap 16.0, PSI was compiled into the kernel but disabled by default (<code>CONFIG_PSI_DEFAULT_DISABLED=y</code>). In Leap 16.1, this default has been changed to enabled (<code>CONFIG_PSI_DEFAULT_DISABLED=n</code>). | ||
| Line 461: | Line 461: | ||
If you encounter performance regressions on scheduling-intensive workloads, you can disable PSI at boot time by passing <code>psi=0</code> to the kernel command line. | If you encounter performance regressions on scheduling-intensive workloads, you can disable PSI at boot time by passing <code>psi=0</code> to the kernel command line. | ||
=== | === Reduced kernel lock delays during CPU restriction === | ||
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. | 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. | ||
=== | === Coexistence of zlib and zlib-ng libraries === | ||
openSUSE Leap 16.1 now includes both the traditional <code>zlib</code> and the newer, high-performance <code>zlib-ng</code> compression libraries. The <code>zlib-ng</code> 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 <code>zlib-ng</code> in the future. | openSUSE Leap 16.1 now includes both the traditional <code>zlib</code> and the newer, high-performance <code>zlib-ng</code> compression libraries. The <code>zlib-ng</code> 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 <code>zlib-ng</code> in the future. | ||
=== | === Unified systemd service presets between standard and immutable modes === | ||
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 <code>cloud-init</code> stack, <code>container-image-prune.timer</code>, <code>kubelet.service</code>, and others. Similarly, standard service presets such as <code>firewalld.service</code>, <code>chronyd.service</code>, <code>gdm.service</code>, and virtualization helpers have been enabled by default on immutable installations. Only specific presets directly related to transactional system management (such as <code>transactional-update.timer</code> and <code>health-checker.service</code>) remain restricted to their respective modes. | 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 <code>cloud-init</code> stack, <code>container-image-prune.timer</code>, <code>kubelet.service</code>, and others. Similarly, standard service presets such as <code>firewalld.service</code>, <code>chronyd.service</code>, <code>gdm.service</code>, and virtualization helpers have been enabled by default on immutable installations. Only specific presets directly related to transactional system management (such as <code>transactional-update.timer</code> and <code>health-checker.service</code>) remain restricted to their respective modes. | ||
=== | === Distrobox pre-installed by default === | ||
openSUSE Leap now includes <code>distrobox</code> pre-installed by default, replacing the older <code>toolbox</code> utility. <code>distrobox</code> enables launching mutable, persistent containerized environments utilizing <code>podman</code> or <code>docker</code>. 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. | openSUSE Leap now includes <code>distrobox</code> pre-installed by default, replacing the older <code>toolbox</code> utility. <code>distrobox</code> enables launching mutable, persistent containerized environments utilizing <code>podman</code> or <code>docker</code>. 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. | ||
=== | === NVIDIA drivers not available for real-time kernel === | ||
With the introduction of the real-time kernel in openSUSE Leap 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. | With the introduction of the real-time kernel in openSUSE Leap 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. | ||
=== | === Repository Mirroring Tool (RMT) server now available === | ||
openSUSE Leap 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. | openSUSE Leap 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. | ||
=== | === Firewalld default presets === | ||
To ensure consistent security and management preset behavior, <code>firewalld</code> is now enabled by default. This unification aligns the default service states across standard and immutable operating modes on openSUSE Leap 16.1. You can customize the firewalld presets or disable the service if necessary. | To ensure consistent security and management preset behavior, <code>firewalld</code> is now enabled by default. This unification aligns the default service states across standard and immutable operating modes on openSUSE Leap 16.1. You can customize the firewalld presets or disable the service if necessary. | ||
=== | === Added iptables and nftables to SLES Minimal images === | ||
The <code>iptables</code> and <code>nftables</code> 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. | The <code>iptables</code> and <code>nftables</code> 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. | ||
=== | === Refactoring of clustering packages for Immutable Mode === | ||
openSUSE Leap 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 <code>crmsh</code>, <code>corosync-qdevice</code>, <code>resource-agents</code>, and <code>corosync</code> have been updated. These packages can now be safely installed and updated via the <code>transactional-update</code> tool. This ensures they do not attempt to write to non-transactional or non-snapshotted areas (such as <code>/var</code>) during transactions. | openSUSE Leap 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 <code>crmsh</code>, <code>corosync-qdevice</code>, <code>resource-agents</code>, and <code>corosync</code> have been updated. These packages can now be safely installed and updated via the <code>transactional-update</code> tool. This ensures they do not attempt to write to non-transactional or non-snapshotted areas (such as <code>/var</code>) during transactions. | ||
=== | === SSH public key support for all accounts created during installation === | ||
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 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. | ||
=== | === Automated generation and validation of Agama profiles === | ||
The Agama installer uses JSON or Jsonnet profiles for automated installations. The <code>agama config</code> subcommand provides capabilities to export, convert, validate, and load these profiles. For detailed instructions, command usage, and complete working examples, see the [https://documentation.suse.com/sles/16.0/html/SLES-x86-64-agama-automated-installation/ Automated Installation Using Agama] guide. | The Agama installer uses JSON or Jsonnet profiles for automated installations. The <code>agama config</code> subcommand provides capabilities to export, convert, validate, and load these profiles. For detailed instructions, command usage, and complete working examples, see the [https://documentation.suse.com/sles/16.0/html/SLES-x86-64-agama-automated-installation/ Automated Installation Using Agama] guide. | ||
=== | === SAP patterns updated === | ||
SAP installation patterns have been updated to optimize and simplify the installation process. | SAP installation patterns have been updated to optimize and simplify the installation process. | ||
| Line 512: | Line 512: | ||
* The <code>libatomic</code> package has been added to the SAP base pattern on SUSE Linux Enterprise Server to simplify the installation instructions for SAP HANA. | * The <code>libatomic</code> package has been added to the SAP base pattern on SUSE Linux Enterprise Server to simplify the installation instructions for SAP HANA. | ||
=== | === XFS log stripe unit alignment change === | ||
<code>mkfs.xfs</code> now automatically aligns the log stripe unit (<code>lsunit</code>) 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 <code>fsync</code>-heavy workloads on systems equipped with battery-backed or non-volatile write-back caches. | <code>mkfs.xfs</code> now automatically aligns the log stripe unit (<code>lsunit</code>) 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 <code>fsync</code>-heavy workloads on systems equipped with battery-backed or non-volatile write-back caches. | ||
| Line 518: | Line 518: | ||
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., <code>mkfs.xfs -l sunit=8</code> 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. | 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., <code>mkfs.xfs -l sunit=8</code> 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. | ||
=== | === Deprecation of legacy XFS v4 filesystem format === | ||
SUSE Linux Enterprise maintains backward compatibility for legacy XFS v4 filesystems via the kernel configuration <code>CONFIG_XFS_SUPPORT_V4=y</code>. This support ensures uninterrupted access for existing environments. However, XFS v4 is deprecated, and creating new v4 filesystems is strongly discouraged. | SUSE Linux Enterprise maintains backward compatibility for legacy XFS v4 filesystems via the kernel configuration <code>CONFIG_XFS_SUPPORT_V4=y</code>. This support ensures uninterrupted access for existing environments. However, XFS v4 is deprecated, and creating new v4 filesystems is strongly discouraged. | ||
| Line 547: | Line 547: | ||
</pre> | </pre> | ||
=== | === Characters in the private use area disabled in the alternate German keymap === | ||
The alternate German keymap <code>qwertz/de_alt_UTF-8</code> no longer supports characters in the Private Use Area (characters equal to or greater than <code>U+F000</code>). 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. | The alternate German keymap <code>qwertz/de_alt_UTF-8</code> no longer supports characters in the Private Use Area (characters equal to or greater than <code>U+F000</code>). 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. | ||
=== | === SDL 3 and sdl2-compat update === | ||
openSUSE Leap 16.1 includes Simple DirectMedia Layer 3 (SDL 3). Compatibility for SDL 2.0 applications is now provided through the <code>sdl2-compat</code> library layer. The legacy <code>SDL2</code> package has been removed. | openSUSE Leap 16.1 includes Simple DirectMedia Layer 3 (SDL 3). Compatibility for SDL 2.0 applications is now provided through the <code>sdl2-compat</code> library layer. The legacy <code>SDL2</code> package has been removed. | ||
=== | === FreeRDP has been updated to version 3.26.0 === | ||
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. | 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) upgraded to version 6.3.8 === | ||
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 <code>pcp-htop</code>. It adds Valkey support alongside Redis in <code>libpcp_web</code>. 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/ https://pcp.io/] and the package changelog. | 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 <code>pcp-htop</code>. It adds Valkey support alongside Redis in <code>libpcp_web</code>. 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/ https://pcp.io/] and the package changelog. | ||
=== | === <code>curl</code> updated to version 8.21.0 === | ||
openSUSE Leap 16.1 includes <code>curl</code> version 8.21.0. For a complete list of changes, see the [https://curl.se/ch/8.21.0.html curl 8.21.0 changelog]. | openSUSE Leap 16.1 includes <code>curl</code> version 8.21.0. For a complete list of changes, see the [https://curl.se/ch/8.21.0.html curl 8.21.0 changelog]. | ||
=== | === PHP updated to version 8.5 === | ||
openSUSE Leap 16.1 includes PHP version 8.5. For more information, see the [https://www.php.net/releases/8_5_0.php PHP 8.5 release announcement] and the [https://documentation.suse.com/sles/16.0/html/SLE-packages-lifecycle/index.html#packages-lifecycle-php PHP Packages Lifecycle documentation]. | openSUSE Leap 16.1 includes PHP version 8.5. For more information, see the [https://www.php.net/releases/8_5_0.php PHP 8.5 release announcement] and the [https://documentation.suse.com/sles/16.0/html/SLE-packages-lifecycle/index.html#packages-lifecycle-php PHP Packages Lifecycle documentation]. | ||
=== | === <code>poppler</code> updated to version 26.x === | ||
openSUSE Leap 16.1 includes the <code>poppler</code> PDF rendering library version 26.x. | openSUSE Leap 16.1 includes the <code>poppler</code> PDF rendering library version 26.x. | ||
| Line 582: | Line 582: | ||
* '''New signature features:''' The <code>pdfsig</code> utility includes a new <code>--assert-signer</code> option to verify the identity of the signer. | * '''New signature features:''' The <code>pdfsig</code> utility includes a new <code>--assert-signer</code> option to verify the identity of the signer. | ||
=== | === Upcoming update of GNU <code>patch</code> to version 2.8 in openSUSE Leap 16.2 === | ||
The GNU <code>patch</code> package will be updated to version 2.8 in openSUSE Leap 16.2. For a complete list of upcoming changes, see the [https://savannah.gnu.org/news/?id=10741 GNU patch release announcement]. | The GNU <code>patch</code> package will be updated to version 2.8 in openSUSE Leap 16.2. For a complete list of upcoming changes, see the [https://savannah.gnu.org/news/?id=10741 GNU patch release announcement]. | ||
| Line 588: | Line 588: | ||
GNU <code>patch</code> version 2.8 enforces stricter header parsing. Ensure patch-generating tools do not inject <code>NUL</code> bytes or raw control characters into header lines or diff directives, as they are no longer accepted in version 2.8. | GNU <code>patch</code> version 2.8 enforces stricter header parsing. Ensure patch-generating tools do not inject <code>NUL</code> bytes or raw control characters into header lines or diff directives, as they are no longer accepted in version 2.8. | ||
=== | === Login hint when attempting root login to Cockpit === | ||
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 <code>/etc/cockpit/disallowed-users</code>. | 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 <code>/etc/cockpit/disallowed-users</code>. | ||
=== | === Cockpit bootloader package added === | ||
openSUSE Leap 16.1 includes the new <code>cockpit-bootloader</code> package. This package provides a Cockpit interface module to configure bootloader settings. This module replaces the previous YaST bootloader configuration functionality. openSUSE Leap 16.1 also includes the required dependency package <code>bootkitd</code>. | openSUSE Leap 16.1 includes the new <code>cockpit-bootloader</code> package. This package provides a Cockpit interface module to configure bootloader settings. This module replaces the previous YaST bootloader configuration functionality. openSUSE Leap 16.1 also includes the required dependency package <code>bootkitd</code>. | ||
=== | === Curated set of Ansible development and testing tools === | ||
Currently, openSUSE Leap ships only the Ansible runtime (<code>ansible-core</code> and <code>ansible</code>). openSUSE Leap 16.1 introduces a curated set of Ansible development and testing tools. These tools enable testing, linting, and building Ansible content. | Currently, openSUSE Leap ships only the Ansible runtime (<code>ansible-core</code> and <code>ansible</code>). openSUSE Leap 16.1 introduces a curated set of Ansible development and testing tools. These tools enable testing, linting, and building Ansible content. | ||
| Line 610: | Line 610: | ||
* <code>ansible-creator</code>: Provides commands to scaffold new Ansible projects and content. | * <code>ansible-creator</code>: Provides commands to scaffold new Ansible projects and content. | ||
=== | === IO scheduler distribution default changed === | ||
The distribution default has changed for a certain set of block devices: rotating disks that have only a single I/O queue. On Leap, such devices would previously be driven by the <code>bfq</code> I/O scheduler by default. Now we are using the same default as the kernel, which is <code>mq-deadline</code> for most devices, and <code>none</code> for some. | The distribution default has changed for a certain set of block devices: rotating disks that have only a single I/O queue. On Leap, such devices would previously be driven by the <code>bfq</code> I/O scheduler by default. Now we are using the same default as the kernel, which is <code>mq-deadline</code> for most devices, and <code>none</code> for some. | ||
=== | === New GCC warnings for Year 2038 (Y2K38) issues === | ||
To help identify and mitigate Year 2038 (Y2K38) 32-bit <code>time_t</code> 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 <code>int</code> types). It is recommended to review these warnings and update affected code to use 64-bit structures where necessary. | To help identify and mitigate Year 2038 (Y2K38) 32-bit <code>time_t</code> 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 <code>int</code> types). It is recommended to review these warnings and update affected code to use 64-bit structures where necessary. | ||
=== | === Immutable mode is unsupported for SAP workloads === | ||
Running of the SAP software stack is not supported in immutable mode: | Running of the SAP software stack is not supported in immutable mode: | ||
| Line 629: | Line 629: | ||
Note that this applies to traditional software. SAP software running in containers (like SAP Edge Integration Cell) is 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. | ||
=== | === <code>update-alternatives</code> no longer used for PostgreSQL === | ||
To better support immutable systems and transactional updates, the <code>update-alternatives</code> 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 <code>README.SUSE</code> file provided in the <code>postgresql</code> main package. | To better support immutable systems and transactional updates, the <code>update-alternatives</code> 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 <code>README.SUSE</code> file provided in the <code>postgresql</code> main package. | ||
=== | === Agama installer supports both standard and immutable installation modes === | ||
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. | 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. | ||
=== | === Agama live image includes Combustion === | ||
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. | 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. | ||
| Line 643: | Line 643: | ||
Combustion does not run automatically by default. To run Combustion scripts, Combustion must be explicitly enabled by adding the <code>rd.systemd.wants=firstboot.target</code> 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. | Combustion does not run automatically by default. To run Combustion scripts, Combustion must be explicitly enabled by adding the <code>rd.systemd.wants=firstboot.target</code> 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. | ||
=== | === NVMeoF boot: network interfaces maintain standard names === | ||
For root-over-NVMeoF setups, in Leap 16.0 and prior releases, the network interfaces were renamed to <code>nbft0</code>, <code>nbft1</code>, and so on. In Leap 16.1, on new installations, network interfaces keep their standard names. | For root-over-NVMeoF setups, in Leap 16.0 and prior releases, the network interfaces were renamed to <code>nbft0</code>, <code>nbft1</code>, and so on. In Leap 16.1, on new installations, network interfaces keep their standard names. | ||
=== | === Kernel switches to PREEMPT_LAZY preemption model === | ||
The upstream kernel community has moved away from conservative scheduler preemption models (<code>PREEMPT_NONE</code> and <code>PREEMPT_VOLUNTARY</code>), and these models have been removed in kernel 7.0 for architectures that support <code>PREEMPT_LAZY</code>. To align with upstream changes, openSUSE Leap 16.1 switches the preemption model from <code>PREEMPT_VOLUNTARY</code> to <code>PREEMPT_LAZY</code> for all supported architectures, except for IBM Z (<code>s390x</code>), which lacks architectural support. | The upstream kernel community has moved away from conservative scheduler preemption models (<code>PREEMPT_NONE</code> and <code>PREEMPT_VOLUNTARY</code>), and these models have been removed in kernel 7.0 for architectures that support <code>PREEMPT_LAZY</code>. To align with upstream changes, openSUSE Leap 16.1 switches the preemption model from <code>PREEMPT_VOLUNTARY</code> to <code>PREEMPT_LAZY</code> for all supported architectures, except for IBM Z (<code>s390x</code>), which lacks architectural support. | ||
| Line 653: | Line 653: | ||
The <code>PREEMPT_LAZY</code> 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 <code>PREEMPT_VOLUNTARY</code> by setting <code>preempt=voluntary</code> on the kernel command line. | The <code>PREEMPT_LAZY</code> 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 <code>PREEMPT_VOLUNTARY</code> by setting <code>preempt=voluntary</code> on the kernel command line. | ||
=== | === Real-time kernel is available on standard openSUSE Leap installations === | ||
Standard openSUSE Leap installations now include the real-time kernel (<code>kernel-rt</code>). 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. | Standard openSUSE Leap installations now include the real-time kernel (<code>kernel-rt</code>). 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. | ||
=== | === Stable kABI for real-time kernel === | ||
The real-time kernel (<code>kernel-rt</code>) 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. | The real-time kernel (<code>kernel-rt</code>) 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 not supported in installer Web UI === | ||
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 https://agama-project.github.io/docs/user/reference/profile/storage]. RAID support in the installer Web UI is planned for a future release. | 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 https://agama-project.github.io/docs/user/reference/profile/storage]. RAID support in the installer Web UI is planned for a future release. | ||
=== | === Support for NTP configuration in early boot and the Agama installer === | ||
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 <code>rd.ntp=<server></code> 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 <code>ntp</code> section in the installer profile or via input fields in the user interface. Legacy AutoYaST <code>ntp-client</code> configurations are automatically converted into the native <code>ntp</code> configuration block on profile import. The configured NTP settings are written to the target system to persist after installation. | 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 <code>rd.ntp=<server></code> 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 <code>ntp</code> section in the installer profile or via input fields in the user interface. Legacy AutoYaST <code>ntp-client</code> configurations are automatically converted into the native <code>ntp</code> configuration block on profile import. The configured NTP settings are written to the target system to persist after installation. | ||
=== | === Kiwi KubeVirt containerdisk format === | ||
Kiwi now supports a new <code>containerdisk</code> format for building KubeVirt-compatible container images from OEM disk builds. | Kiwi now supports a new <code>containerdisk</code> format for building KubeVirt-compatible container images from OEM disk builds. | ||
| Line 679: | Line 679: | ||
Example format syntax: <code>format="oci:qcow2:docker://registry.example.com/kubevirt-disk:latest"</code> | Example format syntax: <code>format="oci:qcow2:docker://registry.example.com/kubevirt-disk:latest"</code> | ||
=== | === SSSD: support for running as unprivileged user === | ||
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. | 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. | ||
| Line 707: | Line 707: | ||
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. | 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. | ||
=== | === Multiple LSMs enabled by default === | ||
SELinux is now used as the primary LSM (Linux Security Module) as compared to AppArmor that was used previously. | SELinux is now used as the primary LSM (Linux Security Module) as compared to AppArmor that was used previously. | ||
| Line 718: | Line 718: | ||
* other virtual ones like bpf, ima, evm, capability | * other virtual ones like bpf, ima, evm, capability | ||
==== | ==== Yama ==== | ||
Yama is a global framework that collects system-wide DAC security protections that are not handled by the core kernel itself. Individual processes can disable Yama for themselves. The enablement of Yama disables the <code>ptrace</code> mechanism of processes by default, except in the following cases: | Yama is a global framework that collects system-wide DAC security protections that are not handled by the core kernel itself. Individual processes can disable Yama for themselves. The enablement of Yama disables the <code>ptrace</code> mechanism of processes by default, except in the following cases: | ||
| Line 734: | Line 734: | ||
To enable <code>ptrace</code> system-wide again after the next reboot, install the <code>aaa_base-yama-enable-ptrace</code> package. | To enable <code>ptrace</code> system-wide again after the next reboot, install the <code>aaa_base-yama-enable-ptrace</code> package. | ||
==== | ==== Landlock ==== | ||
Landlock is a local security framework where processes can voluntarily confine their own actions. It provides scoped access-control (sandboxing) limited to file system and socket actions. Refer to the <code>landlock</code> manual pages for more details. | Landlock is a local security framework where processes can voluntarily confine their own actions. It provides scoped access-control (sandboxing) limited to file system and socket actions. Refer to the <code>landlock</code> manual pages for more details. | ||
==== | ==== Lockdown ==== | ||
Lockdown is a kernel-based lockdown method. The kernel supports three lockdown states: | Lockdown is a kernel-based lockdown method. The kernel supports three lockdown states: | ||
| Line 748: | Line 748: | ||
The lockdown level can be set during boot. By default, the level is set to <code>none</code>, but for Secure Boot, <code>integrity</code> is the lowest default level. During runtime, the lockdown level can only be increased, and cannot be decreased. | The lockdown level can be set during boot. By default, the level is set to <code>none</code>, but for Secure Boot, <code>integrity</code> is the lowest default level. During runtime, the lockdown level can only be increased, and cannot be decreased. | ||
=== | === Consistent location for kernel and initramfs across architectures === | ||
Previously, location of kernel or initrams would differ based on architecture. | Previously, location of kernel or initrams would differ based on architecture. | ||
| Line 754: | Line 754: | ||
Now these are stored in the same location regardless of architecture: <code>boot/$arch/loader/</code> | Now these are stored in the same location regardless of architecture: <code>boot/$arch/loader/</code> | ||
=== | === Supported Java Versions === | ||
The following table lists Java implementations available in SUSE Linux Enterprise Server 16.1: | The following table lists Java implementations available in SUSE Linux Enterprise Server 16.1: | ||
| Line 768: | Line 768: | ||
|} | |} | ||
=== | === Python in SLES 16.1 === | ||
openSUSE Leap 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 <code>/usr/bin/python3</code> executable and a full stack of <code>python3-</code> packages (approximately 700 packages). | openSUSE Leap 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 <code>/usr/bin/python3</code> executable and a full stack of <code>python3-</code> packages (approximately 700 packages). | ||
| Line 776: | Line 776: | ||
The Python support strategy for openSUSE Leap 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). | The Python support strategy for openSUSE Leap 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). | ||
== | == x86-64-specific changes == | ||
Information in this section applies to the x86-64 architecture. | Information in this section applies to the x86-64 architecture. | ||
=== | === Clocksource watchdog disabled on HPE UV5 platforms === | ||
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 <code>tsc=nowatchdog</code> 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. | 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 <code>tsc=nowatchdog</code> 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. | ||
=== | === Support for Intel "Wildcat Lake-U" CPU platform === | ||
openSUSE Leap 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. | openSUSE Leap 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. | ||
== | == Arm-specific changes (AArch64) == | ||
Information in this section applies to openSUSE Leap on Arm 16.1. | Information in this section applies to openSUSE Leap on Arm 16.1. | ||
=== | === System-on-Chip driver enablement === | ||
Leap 16.1 includes driver enablement for the following System-on-Chip (SoC) chipsets: | Leap 16.1 includes driver enablement for the following System-on-Chip (SoC) chipsets: | ||
| Line 816: | Line 816: | ||
Check for SUSE ''YES!'' certified systems, which have undergone compatibility testing. | Check for SUSE ''YES!'' certified systems, which have undergone compatibility testing. | ||
=== | === Non-blocking console support === | ||
Non-blocking console (<code>nbcon</code>) support is enabled on the AArch64 architecture. The common AMBA PL011 serial console driver (<code>amba-pl011</code>) is converted to the new <code>nbcon</code> 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 <code>nmi_panic</code>). This ensures critical post-crash details are captured immediately without relying on legacy printing locks or threads. | Non-blocking console (<code>nbcon</code>) support is enabled on the AArch64 architecture. The common AMBA PL011 serial console driver (<code>amba-pl011</code>) is converted to the new <code>nbcon</code> 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 <code>nmi_panic</code>). This ensures critical post-crash details are captured immediately without relying on legacy printing locks or threads. | ||
== | == IBM Z-specific changes (s390x) == | ||
Information in this section applies to openSUSE Leap for IBM Z and LinuxONE 16.1. For more information, see [https://www.ibm.com/docs/en/linux-on-systems?topic=distributions-suse-linux-enterprise-server https://www.ibm.com/docs/en/linux-on-systems?topic=distributions-suse-linux-enterprise-server] | Information in this section applies to openSUSE Leap for IBM Z and LinuxONE 16.1. For more information, see [https://www.ibm.com/docs/en/linux-on-systems?topic=distributions-suse-linux-enterprise-server https://www.ibm.com/docs/en/linux-on-systems?topic=distributions-suse-linux-enterprise-server] | ||
=== | === New <code>zpckey</code> tool and changed interface in <code>libzpc</code> 2 === | ||
openSUSE Leap includes <code>libzpc</code> version 2 for IBM Z. | openSUSE Leap includes <code>libzpc</code> version 2 for IBM Z. | ||
| Line 832: | Line 832: | ||
Version 2 does not provide the <code>libzpc</code> C API as a shared library. Applications must use the OpenSSL provider module instead. The <code>libzpc-legacy</code> package provides the version 1 packages <code>libzpc1</code> and <code>libzpc-devel</code>. The package is deprecated and will be removed in a future release. | Version 2 does not provide the <code>libzpc</code> C API as a shared library. Applications must use the OpenSSL provider module instead. The <code>libzpc-legacy</code> package provides the version 1 packages <code>libzpc1</code> and <code>libzpc-devel</code>. The package is deprecated and will be removed in a future release. | ||
=== | === Secure Boot support for ECKD DASD disks on IBM Z === | ||
openSUSE Leap 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 (<code>zipl</code>) 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. | openSUSE Leap 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 (<code>zipl</code>) 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. | ||
=== | === Removed support for IBM 3480 and 3590 tape drives === | ||
Support for IBM 3480 and 3590 tape drives, including the <code>tape390_display</code> and <code>tape390_crypt</code> tools, has been removed. In <code>s390-tools</code>, support for 3480 and 3590 FICON tape devices as well as the related <code>tape390</code> 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 <code>tape.ko</code>, <code>tape_34xx.ko</code>, and <code>tape_3590.ko</code> kernel modules. | Support for IBM 3480 and 3590 tape drives, including the <code>tape390_display</code> and <code>tape390_crypt</code> tools, has been removed. In <code>s390-tools</code>, support for 3480 and 3590 FICON tape devices as well as the related <code>tape390</code> 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 <code>tape.ko</code>, <code>tape_34xx.ko</code>, and <code>tape_3590.ko</code> kernel modules. | ||
=== | === Installer support for pervasive encryption on IBM Z === | ||
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 <code>apqns</code> and <code>keyType</code> properties under the <code>pervasiveLuks2</code> encryption configuration. During installation, the encryption planner assigns the specified APQN objects and key types to the planned encrypted devices. | 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 <code>apqns</code> and <code>keyType</code> properties under the <code>pervasiveLuks2</code> encryption configuration. During installation, the encryption planner assigns the specified APQN objects and key types to the planned encrypted devices. | ||
=== | === IBM z17 hardware support in libraries and development tools === | ||
Several IBM libraries and development tools now support the IBM z17 hardware platform. The system libraries <code>libzdnn</code>, <code>libzpc</code>, and <code>libica</code> 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. | Several IBM libraries and development tools now support the IBM z17 hardware platform. The system libraries <code>libzdnn</code>, <code>libzpc</code>, and <code>libica</code> 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. | ||
=== | === Secure Initial Program Load (IPL) support === | ||
IPL has the following minimum system requirements, depending on the boot device to be IPLed: | IPL has the following minimum system requirements, depending on the boot device to be IPLed: | ||
| Line 858: | Line 858: | ||
If these requirements are not met, the system can be IPLed in non-secure mode only. | If these requirements are not met, the system can be IPLed in non-secure mode only. | ||
== | == POWER-specific changes (ppc64le) == | ||
Information in this section applies to openSUSE Leap on POWER 16.1. | Information in this section applies to openSUSE Leap on POWER 16.1. | ||
=== | === Boot fails when PReP partition and root filesystem use different storage devices === | ||
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. | 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. | ||
| Line 868: | Line 868: | ||
To avoid this issue, configure the PReP boot partition and the root file system on the same storage subsystem. | To avoid this issue, configure the PReP boot partition and the root file system on the same storage subsystem. | ||
=== | === Kdump capture fails on NVMe-oF targets === | ||
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. | 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. | ||
=== | === Login times out on HMC virtual terminal === | ||
If you install openSUSE Leap 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. | If you install openSUSE Leap 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. | ||
| Line 878: | Line 878: | ||
To work around this issue, disable the Plymouth graphical boot screen by appending the boot parameter <code>plymouth.enable=0</code> to the kernel command line. | To work around this issue, disable the Plymouth graphical boot screen by appending the boot parameter <code>plymouth.enable=0</code> to the kernel command line. | ||
=== | === Automated provisioning with cloud-init in virtual machine guest images === | ||
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. | 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. | ||
== | == Virtualization == | ||
* iSCSI boot support is disabled in OVMF images. | * iSCSI boot support is disabled in OVMF images. | ||
=== | === Virtual persistent memory (vPMEM) in virtual machine guests === | ||
openSUSE Leap 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. openSUSE Leap does not support physical Intel* Optane* Memory. | openSUSE Leap 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. openSUSE Leap does not support physical Intel* Optane* Memory. | ||
=== | === QEMU === | ||
QEMU has been updated to version 11.0.0. For changes, see [https://wiki.qemu.org/ChangeLog/11.0 https://wiki.qemu.org/ChangeLog/11.0]. For removed or deprecated features, see [https://qemu-project.gitlab.io/qemu/about/removed-features.html https://qemu-project.gitlab.io/qemu/about/removed-features.html] and [https://qemu-project.gitlab.io/qemu/about/deprecated.html https://qemu-project.gitlab.io/qemu/about/deprecated.html]. | QEMU has been updated to version 11.0.0. For changes, see [https://wiki.qemu.org/ChangeLog/11.0 https://wiki.qemu.org/ChangeLog/11.0]. For removed or deprecated features, see [https://qemu-project.gitlab.io/qemu/about/removed-features.html https://qemu-project.gitlab.io/qemu/about/removed-features.html] and [https://qemu-project.gitlab.io/qemu/about/deprecated.html https://qemu-project.gitlab.io/qemu/about/deprecated.html]. | ||
=== | === libvirt === | ||
<code>libvirt</code> 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 https://libvirt.org/news.html#v12-3-0-2026-05-02]. | <code>libvirt</code> 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 https://libvirt.org/news.html#v12-3-0-2026-05-02]. | ||
==== | ==== Virtual machine confinement enabled by default in libvirt ==== | ||
<code>libvirt</code> now enables confinement of virtual machines (VMs) by default using the system’s default security framework (SELinux in openSUSE Leap 16). This improves out-of-the-box VM isolation and security. Administrators can override this setting in <code>/etc/libvirt/qemu.conf</code>. | <code>libvirt</code> now enables confinement of virtual machines (VMs) by default using the system’s default security framework (SELinux in openSUSE Leap 16). This improves out-of-the-box VM isolation and security. Administrators can override this setting in <code>/etc/libvirt/qemu.conf</code>. | ||
=== | === VMware === | ||
==== | ==== open-vm-tools ==== | ||
<code>open-vm-tools</code> has been updated to version 13.1.0. For details, see [https://github.com/vmware/open-vm-tools/blob/stable-13.1.0/ReleaseNotes.md https://github.com/vmware/open-vm-tools/blob/stable-13.1.0/ReleaseNotes.md]. | <code>open-vm-tools</code> has been updated to version 13.1.0. For details, see [https://github.com/vmware/open-vm-tools/blob/stable-13.1.0/ReleaseNotes.md https://github.com/vmware/open-vm-tools/blob/stable-13.1.0/ReleaseNotes.md]. | ||
=== | === Confidential Computing === | ||
==== | ==== AMD SEV-SNP packages update ==== | ||
AMD SEV-SNP is supported in openSUSE Leap 16.1. The following AMD Secure Encrypted Virtualization (SEV-SNP) tools have been updated: | AMD SEV-SNP is supported in openSUSE Leap 16.1. The following AMD Secure Encrypted Virtualization (SEV-SNP) tools have been updated: | ||
| Line 918: | Line 918: | ||
* <code>snphost</code> has been updated to version 0.7.0. | * <code>snphost</code> has been updated to version 0.7.0. | ||
For details on AMD remote and local attestation, see [[# | For details on AMD remote and local attestation, see [[#Confidential Computing Remote and Local Attestation (technology preview)|“Confidential Computing Remote and Local Attestation (technology preview)”]]. | ||
==== | ==== Intel TDX Confidential Computing ==== | ||
Intel TDX is supported in openSUSE Leap 16.1. For details on Intel TDX remote and local attestation, see [[# | Intel TDX is supported in openSUSE Leap 16.1. For details on Intel TDX remote and local attestation, see [[#Confidential Computing Remote and Local Attestation (technology preview)|“Confidential Computing Remote and Local Attestation (technology preview)”]]. | ||
=== | === Other tools === | ||
The following virtualization utilities have been updated: | The following virtualization utilities have been updated: | ||
| Line 935: | Line 935: | ||
* <code>virt-manager</code> has been updated to version 5.1.0. Direct XML editing via <code>virsh</code> and remote viewing via VNC are recommended (see [https://github.com/virt-manager/virt-manager/releases/tag/v5.1.0 https://github.com/virt-manager/virt-manager/releases/tag/v5.1.0]). | * <code>virt-manager</code> has been updated to version 5.1.0. Direct XML editing via <code>virsh</code> and remote viewing via VNC are recommended (see [https://github.com/virt-manager/virt-manager/releases/tag/v5.1.0 https://github.com/virt-manager/virt-manager/releases/tag/v5.1.0]). | ||
==== | ==== <code>virt-bridge-setup</code> ==== | ||
<code>virt-bridge-setup</code> is a new script designed to simplify network bridge creation on a specified interface using <code>nmcli</code>. It replaces the automatic bridge creation previously managed by <code>yast2 virtualization</code>. | <code>virt-bridge-setup</code> is a new script designed to simplify network bridge creation on a specified interface using <code>nmcli</code>. It replaces the automatic bridge creation previously managed by <code>yast2 virtualization</code>. | ||
| Line 945: | Line 945: | ||
* The script must be run locally (not over a remote connection) immediately after installation and before applying any custom network configurations. | * The script must be run locally (not over a remote connection) immediately after installation and before applying any custom network configurations. | ||
==== | ==== <code>strace</code> updated to version 7.1 ==== | ||
<code>strace</code> has been updated to version 7.1. | <code>strace</code> has been updated to version 7.1. | ||
| Line 959: | Line 959: | ||
* This version adds support for Linux kernel 7.1 ioctl commands. | * This version adds support for Linux kernel 7.1 ioctl commands. | ||
== | == Removed and deprecated features and packages == | ||
This section lists features and packages that were removed from openSUSE Leap or will be removed in upcoming versions. | This section lists features and packages that were removed from openSUSE Leap or will be removed in upcoming versions. | ||
=== | === Removed features and packages === | ||
The following features and packages have been removed in this release. | The following features and packages have been removed in this release. | ||
| Line 982: | Line 982: | ||
* The UDP-Lite protocol (RFC 3828) has been disabled in the openSUSE Leap 16.1 kernel. This protocol has been dropped from the upstream Linux kernel. | * The UDP-Lite protocol (RFC 3828) has been disabled in the openSUSE Leap 16.1 kernel. This protocol has been dropped from the upstream Linux kernel. | ||
==== | ==== Support for SUSE Rancher Prime: OS Manager 2.x removed ==== | ||
This release removes SUSE Rancher Prime: OS Manager 2.x components and container images. To manage operating system deployments, use SUSE Rancher Prime: OS Manager 3.x. The coexistence of versions 2.x and 3.x in the previous release supported the migration path. Only SUSE Rancher Prime: OS Manager 3.x remains supported from this release onward. | This release removes SUSE Rancher Prime: OS Manager 2.x components and container images. To manage operating system deployments, use SUSE Rancher Prime: OS Manager 3.x. The coexistence of versions 2.x and 3.x in the previous release supported the migration path. Only SUSE Rancher Prime: OS Manager 3.x remains supported from this release onward. | ||
=== | === Deprecated features and packages === | ||
The following features and packages are deprecated and will be removed in a future version of openSUSE Leap. | The following features and packages are deprecated and will be removed in a future version of openSUSE Leap. | ||
* Legacy XFS v4 filesystems are deprecated. For details, see [[# | * Legacy XFS v4 filesystems are deprecated. For details, see [[#Deprecation of legacy XFS v4 filesystem format|“Deprecation of legacy XFS v4 filesystem format”]]. | ||
* The following SSSD features and options are deprecated in openSUSE Leap 16.1 and are planned for removal in openSUSE Leap 16.2: | * The following SSSD features and options are deprecated in openSUSE Leap 16.1 and are planned for removal in openSUSE Leap 16.2: | ||
** The enumeration feature for the AD or IPA provider | ** The enumeration feature for the AD or IPA provider | ||
| Line 1,007: | Line 1,007: | ||
* The <code>qib</code> driver has been deprecated in openSUSE Leap 16.1 and will be removed in openSUSE Leap 16.2. | * The <code>qib</code> driver has been deprecated in openSUSE Leap 16.1 and will be removed in openSUSE Leap 16.2. | ||
= | = 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://get.opensuse.org/ https://get.opensuse.org] 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 [mailto:sle_source_request@suse.com sle_source_request@suse.com]. SUSE may charge a reasonable fee to recover distribution costs. | 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://get.opensuse.org/ https://get.opensuse.org] 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 [mailto:sle_source_request@suse.com sle_source_request@suse.com]. SUSE may charge a reasonable fee to recover distribution costs. | ||
= | = Legal notices = | ||
Copyright © 2025-2026 openSUSE contributors and SUSE LLC. All rights reserved. | Copyright © 2025-2026 openSUSE contributors and SUSE LLC. All rights reserved. | ||