OpenSUSE Leap 16.0 Release Notes: Difference between revisions

Line 76:

=== AppArmor not available by default on new installations ===

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''

Line 86:

Line 87:

== Steam ==

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''

Line 103:

Line 105:

=== Broken libvirt networking when using Docker ===

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''

Line 139:

Line 142:

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.

= SUSE Linux Enterprise Core =

== What's new? ==

=== Package and module changes in 16.0 ===

The full list of changed packages compared to 15 SP7 can be seen at this URL:

https://documentation.suse.com/package-lists/sle/16.0/package-changes_SLE-15-SP7-GA_SLE-16.0-GA.txt

The full list of changed modules compared to 15 SP7 can be seen at this URL:

https://documentation.suse.com/package-lists/sle/16.0/module-changes_SLE-15-SP7-GA_SLE-16.0-GA.txt

== 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.

The current version (16.0) will be fully maintained and supported until 31 Jul 2034.

If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support duration. You can buy an additional 12 to 36 months in twelve month increments. This means that you can receive support up to Dec 2037.

For more information, see the pages [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].

== Support statement for openSUSE Leap ==

To receive support, you need an appropriate subscription with SUSE. For more information, see https://forums.opensuse.org.

The following definitions apply:

;L1

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

;L2

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

;L3

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

For contracted customers and partners, openSUSE Leap is delivered with L3 support for all packages, except for the following:

* Technology Previews, see Section 3.4, "Technology previews"

* Sound, graphics, fonts and artwork

* Packages that require an additional customer contract, see Section 3.3.2, "Software requiring specific contracts"

* 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.

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:

* Section 3.16, "Virtualization"

* Section 3.17, "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>, <code>zypper</code>, or <code>YaST</code>.

Major packages and groups of packages affected by this are:

* PostgreSQL (all versions, including all subpackages)

=== Software under GNU AGPL ===

openSUSE Leap 16.0 (and the SUSE Linux Enterprise modules) includes the following software that is shipped ''only'' under a GNU AGPL software license:

* Ghostscript (including subpackages)

* <code>velociraptor</code> and <code>velociraptor-client</code>

* <code>zypp-boot-plugin</code>

openSUSE Leap 16.0 (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:

* MySpell dictionaries and LightProof

* ArgyllCMS

== Technology previews ==

Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations. Technology previews are included for your convenience to give you a chance to test new technologies within your environment. We would appreciate your feedback! If you test a technology preview, contact your SUSE representative and let them know about your experience and use cases. Your input is helpful for future development.

Technology previews come with the following limitations:

* Technology previews are still in development. Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.

* Technology previews are not supported.

* Technology previews may only be available for specific hardware architectures. Details and functionality of technology previews are subject to change. As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.

* Technology previews can be removed from a product at any time. This may be the case, for example, if SUSE discovers that a preview does not meet the customer or market needs, or does not comply with enterprise standards.

== <code>lklfuse</code> ==

As technology preview, <code>lklfuse</code> is available in openSUSE Leap 16.0.

<code>lklfuse</code> is intentionally built without Btrfs support. Btrfs filesystems can be multi-device (for example, RAID1) but <code>lklfuse</code> currently only supports a single device per mount.

== Changes affecting all architectures ==

* <code>rasdaemon</code> has been updated to version 8.3.0. This version supports machine checks related to CXL memory.

* We now provide Grafana Alloy which can integrate with SUSE Observability as well.

* <code>NetworkManager</code> is now the only network configuration stack in openSUSE Leap 16.0.

* We now provide a unified image that can be used to install either SLES or SLES for SAP

=== Userspace live patching ===

Currently, <code>libpulp</code> supports ULP (user space live patching) of <code>glibc</code> and <code>openssl</code> binaries on the following architectures:

* x86-64

* ppc64le

For more information see https://documentation.suse.com/sles/15-SP7/html/SLES-all/cha-ulp.html

=== Switch to <code>mountfd</code> API in <code>util-linux</code> ===

The <code>util-linux</code> mount command has switched from the old string-based method to the new kernel <code>mountfd</code> API. This change introduces new features but also comes with some minor incompatibilities.

There is a special case that cannot be handled by <code>mountfd</code> and needs to be handled by applications:

* <code>mountfd</code> discriminates between the physical mount layer and the virtual mount layer

* once the physical mount layer is read-only, read-write mount on the virtual layer is not possible

If the first mount is read-only, then the physical filesystem is mounted read-only, and later mounting of the same file system as read-write is not possible. To solve this problem, the first mount needs to be read-only on the virtual layer only, keeping the physical layer read-write. The userspace fix is simple. Instead of:

mount -oro

use

mount -oro=vfs

This will keep the physical layer read-write, but the virtual file system layer (and the userspace access) read-only.

=== Switch to predictable network names ===

The persistent network naming scheme used in Leap 15 became legacy with the switch to the systemd predictable network names. For complicated setups, we recommend using <code>systemd.link</code>.

For more information, see:

* https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

* https://www.freedesktop.org/software/systemd/man/latest/systemd.link.html

'''Note'''

In the future, when upgrading from SL Micro to Leap 16.1 (so-called "SLE merge"), some systems will have <code>net.ifnames=0</code> set on their kernel command line (this is the case for new installations of SL Micro 6.0 and 6.1). This boot option will prevent the system from switching to the predictable naming scheme and it will need to be removed.

</div>

=== systemd default configurations moved to <code>/usr</code> ===

Main configuration files have been moved from <code>/etc</code> to <code>/usr</code>. This ensures that main configuration files have lower precedence, allowing them to be overriden by package-supplied drop-in snippets.

Local configuration should be created by either modifying the default file in <code>/usr</code> (or a copy of it placed in <code>/etc</code> if the original file is shipped in <code>/usr</code>), or by creating drop-in snippets in the appropriate directory in (for example, <code>/etc/systemd/coredump.conf.d/</code>) - this is recommended.

Remove configurations in <code>/etc</code> to restore defaults.

=== Password access as root via SSH disabled ===

Previously, it was possible to SSH as root using password-based authentication. In Leap 16.0 only key-based authentication is allowed by default. Systems upgraded to 16.0 from a previous version will carry over the old behavior. New installations will enforce the new behavior.

Installing the package <code>openssh-server-config-rootlogin</code> restores the old behavior and allows password-based login for the root user.

=== Minimum hardware requirements ===

openSUSE Leap 16.0 requires hardware to meet requirements on these architectures:

* For AMD64 and Intel* 64 systems: Microarchitecture level x86-64-v2 or higher.

* For IBM* Power LE systems: POWER10 or higher (see note below).

* For Arm64* systems: Armv8.0-A or higher.

* For IBM* Z systems: z14 or higher.

'''Note'''

POWER9 systems may work with Leap 16.0 but are not supported by IBM, the hardware vendor.

</div>

=== SHA1 to be disabled or mark unapproved ===

Due to FIPS 140-3 certification requirements, the SHA1 cryptographic algorithm will be disabled or marked unapproved when running in FIPS mode.

=== Added <code>tuned</code> ===

The <code>tuned</code> package contains a daemon that tunes system settings dynamically.

=== Lightweight guard region support ===

This is a new feature in <code>madvise()</code> that installs a lightweight guard region into a specified address range.

See [https://manpages.opensuse.org/Leap-16.0/man-pages/madvise.2.en.html#MADV_GUARD_INSTALL madvise() man page] for more information.

=== Harmless error messages sometimes displayed when launching some applications ===

The following messages are sometimes displayed when launching specific applications:

# <code>gnome-desktop</code> some times failes to create transient scope:

#:<pre>> gnome-session-binary: GnomeDesktop-WARNING: Could not create transient scope for PID 7883: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 7883 does not exist.</pre>

# <code>systemd</code> sometimes fails to assign cgroup:

#:<pre>> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Couldn't move process 6708 to requested cgroup '/user.slice/user-0.slice/user@0.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope': No such process

> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed to add PIDs to scope's control group: No such process

> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed with result 'resources'.

> systemd: Failed to start Application launched by gnome-session-binary.</pre>

These messages are harmless and can be ignored.

=== NFS over TLS support ===

NFS over TLS is now supported for storage traffic.

=== <code>saptune</code> replaces <code>sapconf</code> ===

In Leap 16.0, <code>sapconf</code> is replaced with <code>saptune</code>. <code>saptune</code> will also be enabled with a base tuning, similar to <code>sapconf</code>. Base tuning only will be enabled if <code>saptune</code> was not configured before (no SAP Notes or Solutions selected).

=== Azure Entra ID authentication via <code>himmelblau</code> ===

The <code>himmelblau</code> package has been added. It provides interoperability with Microsoft Azure Entra ID and Intune. It supports Linux authentication to Microsoft Azure Entra ID via PAM and NSS modules.

For more information see https://github.com/himmelblau-idm/himmelblau.

=== Legacy BIOS support ===

Legacy BIOS is still supported in openSUSE Leap 16.0. However, some features are not available when using it (for example, full-disk encryption with TPM). Finally, support for legacy BIOS will be discontinued in the future. For that reason we recommend switching to UEFI at the nearest opportunity.

=== <code>/tmp</code> not persistent ===

In openSUSE Leap 16.0, <code>/tmp</code> is no longer persistent between reboots but uses <code>tmpfs</code> instead. See https://susedoc.github.io/doc-modular/main/html/SLE-comparison/index.html#sle16-tmp for more information.

=== Python update strategy ===

* <code>/usr/bin/python3</code> is currently set to use Python 3.13. In a future minor version update this is likely going to be changed to a newer Python version.

* openSUSE Leap 16.0 contains around 700 popular Python packages, which form a basic set of functionality for packages that depends on Python and for developing apps without needing to install Python modules from an external provider.

* We have been working on removing the dependencies of packages and tools on the <code>/usr/bin/python3</code> binary, which means that openSUSE Leap could use a newer version of the Python interpreter in the future. This new Python interpreter will coexist with the previous version that will then be maintained as legacy interpreter for a limited time.

=== Removal of 32-bit support ===

openSUSE Leap 16.0 only supports 64-bit binaries. Support for 32-bit binaries (or 31-bit binaries on IBM Z) has been removed.

This means that statically-linked 32-bit binaries (or 31-bit binaries on IBM Z) and container images cannot be run anymore. 32-bit syscalls are still enabled by default on arm64, and can be enabled on x86_64 via the kernel parameter <code>ia32_emulation</code>. On other architectures it’s disabled without any option to enable it.

=== Compiling kernel uses non-default compiler ===

Customers who need to build kernel modules or rebuild the kernel must use the same compiler version the kernel was built with. The kernel is built with <code>gcc</code> version 13, which is not the default compiler. Install the <code>gcc</code> version 13 compiler using the gcc13 package and invoke it with the command <code>gcc-13</code>. This specific compiler version is only supported for building kernel modules and the kernel.

=== Optimized libraries for newer hardware architectures ===

We have added support for the glibc-HWCAPS feature which loads optimized versions of libraries for specific newer CPUs automatically.

The build infrastructure for this feature is enabled for the following libraries:

* <code>blosc2</code>

* <code>boost</code>

* <code>brotli</code>

* <code>bzip2</code>

* <code>flac</code>

* <code>jsoncpp</code>

* <code>lame</code>

* <code>leveldb</code>

* <code>libdb-4_8</code>

* <code>libgcrypt</code>

* <code>libiscsi</code>

* <code>libjpeg-turbo</code>

* <code>libjxl</code>

* <code>libmng</code>

* <code>libnettle</code>

* <code>libpng16</code>

* <code>libvorbis</code>

* <code>libxmlb</code>

* <code>lz4</code>

* <code>lzo</code>

* <code>openjpeg2</code>

* <code>openssl-3</code>

* <code>python311</code>

* <code>python313</code>

* <code>sqlite3</code>

* <code>talloc</code>

* <code>tree-sitter</code>

* <code>wavpack</code>

* <code>xxhash</code>

* <code>xz</code>

* <code>zlib</code>

* <code>zopfli</code>

* <code>zstd</code>

=== No remote root login with password ===

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''

If you install the system using only a <code>root</code> password and do not provide an SSH key for the root user, <code>sshd</code> will not be enabled automatically after installation. You will not be able to log in remotely as root using the password.

</div>

By default, remote password-based <code>root</code> login is disabled. The installer enables the <code>sshd</code> service only when an SSH key for root is configured during setup. To allow remote <code>root</code> login, configure an SSH key for root during installation.

=== Default user group assignment changed ===

Previously, all user accounts belonged to a single <code>users</code> group.

Now instead of being added to the common <code>users</code> group, each new user now gets their own primary group matching their username. This is due to <code>USERGROUPS_ENAB</code> being enabled in <code>/usr/etc/login.defs</code>. This change affects all new installations and upgraded systems that did not change the default <code>/etc/login.defs</code>. This has several consequences:

* files created by new users are not group-readable by default

* configurations that used the primary <code>users</code> group as a condition do not work anymore

* configurations that used the primary or secondary <code>users</code> group as a condition need to have the <code>users</code> group manually added to these user accounts in order to continue to work, for example, to for <code>@users</code> in the sudoers file

* home directories inherited from a previous system need to standardize the GID of the files by running:

:<code>find "$HOME" -group users -exec chgrp myuser {} \;</code> or <code>chgrp -R myuser "$HOME"</code> if you did not use any GID other than <code>users</code>

=== SysV init.d scripts support ===

SysV init.d scripts have been [https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2/index.html#jsc-SLE-7690 deprecated since Leap 15 SP2].

In Leap 16.0, support of SysV init.d scripts has been removed.

== Changes affecting all architectures (RC1) ==

This section contains information specific to RC1. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.

=== <code>/etc/services</code> removal ===

The <code>/etc/services</code> file is just a dummy file that will be removed in the future. Software that appends to it without creating it should have its behavior changed.

== Changes affecting all architectures (Beta4) ==

This section contains information specific to Beta4. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.

=== Configuring network interfaces during installation ===

Currently, the installer does not allow for setting up network interfaces using the UI. However, in the meantime you can use dracut-like command-line options, for example:

ifname=<interface>:<MAC>

ip=<interface>:dhcp

Additionally, the <code>inst.copy_network</code> is not available in Beta4.

=== SAP workloads on Leap 16.0 ===

For running SAP workloads on openSUSE Leap 16.0, do the following:

# Unpack the SAP installer.

# Run the following commands to change policies:

#:<pre>semanage boolean -m --on selinuxuser_execmod

semanage boolean -m --on unconfined_service_transition_to_unconfined_user

semanage permissive -a snapper_grub_plugin_t

restorecon -R /</pre>

# Run the following commands to lable all files:

#:<pre>test -d ./snapshots && restorecon -R / -e /.snapshots

test -d ./snapshots || restorecon R /</pre>

# Install SAP workload or SAP HANA

# Label all files again:

#:<pre>test -d /.snapshots && restorecon -R / -e /.snapshots

test -d /.snapshots || restorecon -R /</pre>

=== FIPS 140-3 not working properly ===

FIPS 140-3 installation has not been fully validated and may cause unexpected software failure or crashes. Therefore, we discourage you from using it on Beta4.

== Changes affecting all architectures (Beta3) ==

This section contains information specific to Beta3. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.

=== Kernel crash in QEMU ===

openSUSE Leap 16.0 requires a CPU that supports a so-called "x86-64-v2" microarchitecture. Due to this, running a Leap image using QEMU currently results in a kernel crash.

As a workaround you can run QEMU with the <code>-cpu host</code> argument.

=== Missing <code>libnsl.so.1</code> library ===

The <code>libnsl.so.1</code> library has been deprecated in SLES 15 and finally removed in openSUSE Leap 16.0.

As a workaround for applications that cannot be installed without it (but presumaly do not use it for anything), we provide the <code>libnsl-stub1</code> package that includes ABI-compatible but otherwise function-less stub of the library file.

=== <code>firewalld</code> not usable with many interfaces ===

Due to an upstream bug, <code>firewalld</code> might take a long time or time out when adding many interfaces. The error occurs when <code>firewalld</code> is restarted after applying such a configuration. The following message appears in the system logs:

ERROR:dbus.proxies:Introspect error on :1.18:/org/fedoraproject/FirewallD1: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.

Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

See https://github.com/firewalld/firewalld/issues/1399 for more information.

== Changes affecting all architectures (Beta2) ==

This section contains information specific to Beta2. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.

=== Switch from YaST to Cockpit ===

openSUSE Leap 16.0 has switched from YaST to Cockpit for manual system administration. We have enhanced Cockpit with new modules with the intention to upstream them later. Despite being functional, bugs might appear and features might be missing.

'''New modules'''

* <code>cockpit-subscriptions</code>: register, de-register and view SUSE Linux Enterprise registrations. Does not work for unprivileged users yet.

* <code>cockpit-repositories</code>: add, remove, view repositories, change settings and refresh them. Does not work for unprivileged users yet.

* <code>cockpit-packages</code>: show installed packages, search available repositories, install and uninstall packages. Requires administrative access. Be aware that there are no safety measures implemented as far as system usability goes.

'''Enhanced modules'''

* <code>cockpit-packagekit</code>: update packages from available repositories. The module now allows to individually select packages to update.

'''Upstream modules'''

<code>cockpit</code>, <code>cockpit-bridge</code>, <code>cockpit-kdump</code>, <code>cockpit-machines</code>, <code>cockpit-networkmanager</code>, <code>cockpit-podman</code>, <code>cockpit-selinux</code>, <code>cockpit-storaged</code>, <code>cockpit-system</code>, <code>cockpit-ws</code>: these modules are updated to the recent stable base version 332 (or their respective).

'''Default selection'''

Installation of the pattern <code>cockpit</code> will pull in the following modules: <code>cockpit</code>, <code>cockpit-bridge</code>, <code>cockpit-networkmanager</code>, <code>cockpit-packagekit</code>, <code>cockpit-packages</code>, <code>cockpit-repos</code>, <code>cockpit-selinux</code>, <code>cockpit-storaged</code>, <code>cockpit-subscriptions</code>, <code>cockpit-system</code>, <code>cockpit-ws</code>.

=== <code>dovecot 2.4</code> configuration upgrade ===

In openSUSE Leap 16.0 <code>dovecot</code> has been upgraded to version 2.4. The configuration of this version is incompatible with the previous versions.

Configuration has to be updated manually. For more information see https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html.

== Changes affecting all architectures (Beta1) ==

This section contains information specific to Beta1. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.

=== Disk configuration UI during installation ===

Currently, choosing disk configurations other than "An existing disk" (installation to a single disk) suffer from poor usability. This is expected to change in a future update.

=== Non-functioning <code>zypper</code> after installation ===

There is currently a known issue that adds a non-functioning <code>zypper</code> repository which prevents <code>zypper</code> from working correctly.

To fix this issue, remove the repository in question and add the installation medium repository manually:

# Remove repository with <code>zypper rr</code>. To remove the first repository, for example, run: <code>zypper rr 1</code>.

# Add the installation medium as repository by running

#:<pre>zypper ar hd:/install?device=/dev/disk/by-label/agama-installer medium</pre>

#:(the <code>medium</code> at the end is a name you want to give the repository).

# Run <code>zypper refresh</code> to refresh the added repository.

=== systemd uses cgroup v2 by default ===

openSUSE Leap 16.0 uses cgroup v2 by default and v1 is unsupported. If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.

== x86-64-specific changes ==

Information in this section applies to the x86-64 architecture.

=== AMD EPYC Turin automonous frequency scaling ===

In Leap 16.0, the default Linux CPU frequency scaling driver for AMD EPYC Turin (and later processors) has shifted to the AMD P-State driver to enable autonomous frequency scaling.

With the AMD P-State driver, it enables the use of the Energy Performance Preference (EPP) for more granular control over performance versus power efficiency to adjust the CPU frequencies based on workload and hardware feedback dynamically.

== IBM Z-specific changes (s390x) ==

Information in this section applies to openSUSE Leap for IBM Z 16.0. For more information, see https://www.ibm.com/docs/en/linux-on-systems?topic=distributions-suse-linux-enterprise-server

=== Hardware ===

* Support has been added for IBM z17 in <code>kernel</code> providing machine name, kconfig options, new instructions, etc.

* Support has been added for IBM z17 in <code>gdb</code>, <code>valgrind</code>, <code>binutils</code>

* Support has been added for IBM z16 - reset DAT-Protection facility support

* Identify ConnectX devices through port rather than PCHID

* Processor Activity Instrumentation / Neural Network Processing Assist counters for new IBM Z hardware was added into kernel

* kprobes are now supported without <code>stop machine</code>

* Promiscuous Mode Exploitation for NETH Virtual Functions for IBM z17 and LinuxONE 5

* Vertical CPU Polarization support for IBM z17 and LinuxONE 5

* qclib has been updated to support IBM z17

* The Integrated Accelerator for AI has new operations, which are now supported by libzdnn low-level driver library

* Enhanced RAS and Call Home for zPCI

* The kernel image can move into vmalloc space, where random physical pages are used to map virtual pages (V!=R)

* Add new CPU-MF Counters for new IBM Z Hardware (libpfm)

* Deactivate CONFIG_QETH_OSX kernel config option

* Upgrade Mellanox (mlx5) driver to latest version

=== Performance ===

* LPAR level power consumption reporting is now available in kernel and s390-tools.

=== Security ===

==== In-kernel crypto support ====

With this service pack are additionally supported:

* MSA 10 XTS instructions for in-kernel crypto

* MSA 11 HMAC instructions for in-kernel crypto

* MSA 12 (SHA3) has been added and introduces new options to call CPACF SHA 3 functions

* MSA 11 HMAC instructions for in-kernel crypto

* MSA 10 XTS crypto PAES support for in-kernel crypto

==== OpenSSL features ====

This release brings these features and improvements:

* XTS instructions support in libcrypto/openSSL

* New MSA 11 HMAC instruction support in libcrypto/openSSL

* Added support for MSA 12 (SHA3), which also introduces new options to call CPACF SHA3 and SHKE functions

* Extended support of the openssl-pkcs11 provider such that it can be used by programs that issue forks

* Replace openssl-ibmpkcs11 with openssl-pkcs11

* Upgrade openssl-ibmca to the latest version

==== openCryptoki ====

* The new version of <code>libica</code> and <code>libzpc</code> is included.

* The openCryptoki CCA Token is now available on x86_64 and ppc64le architectures.

==== p11-kit =====

* Add support for IBM specific attributes and mechanisms to the PKCS11 client-server implementation of p11-kit.

==== pkey ====

* The kernel pkey module can now generate keys AES-XTS keys (MSA 10) and HMAC key (MSA 11) from clear keys.

* The module can also generate keys represented by identifiers of secure execution retrievable keys.

* The pkey also supports EP11 API ordinal 6 for secure guests.

==== zcrypt =====

* The zcrypt extends error recovery to deal with device scans of unavailable devices.

=== Virtualization ===

* KVM guests can exploit z17 & LinuxONE 5 CPU features

* KVM can display available host key hashes for Secure Execution (Query Host-key hash UVC)

* KVM can benefit from genprotimg rewritten in Rust to re-use existing rust libraries (s390-tools feature)

* KVM benefits from genprotimg validation of SE image running on particular host(s) (s390-tools feature)

* KVM benefits from using pvimg info command to display encrypted & unencrypted SE image information (s390-tools)

* KVM can use unencrypted SE images for creating generic images (s390-tools feature)

* KVM passthrough is available for guests i.e. retrievable secrets in Secure Execution guests

* KVM can use unencrypted SE images for creating generic images (s390-tools feature)

* KVM implements counters for nested guest shadow events

* KVM implements virsh hypervisor-cpu-models (libvirt)

* KVM provides enhanced and dynamic CPU topology for KVM guests (qemu)

* KVM and libvirt full boot order enables users to attempt booting from multiple targets

* KVM provides Atomic Memop for Key-Checked Compare-and-swap

* KVM enhances CCW address translation architectural compliance

* KVM improves memory reclaiming for z15 Secure Execution guests and above (libvirt)

=== Miscellaneous ===

* <code>plymouth</code> was replaced by <code>blog</code> on s390x, as <code>plymouth</code> couldn't work without graphical display.

* The <code>Eigen</code> library is the backend used by <code>Tensorflow</code> for computations executed on the CPU. Several GCC adjustments have been implemented to speed up Eigen with IBM z14 support and above.

* Allow <code>httpd</code> customers to protect their web server identity using HSMs (via CryptoExpress adapters).

==== Enhancements in <code>s390-tools</code> ====

The latest s390-tool update brings these noticeable changes:

* Additional channel measurements - kernel & <code>s390-tools</code>

* A new tool cpacinfo shall provide information on CPACF including the supported MSA levels, instructions, subfunctions per instruction. https://www.ibm.com/docs/en/linux-on-systems?topic=hw-cpacf

==== <code>parmfile</code> now points to ISO ====

Previously, <code>parmfile</code> would point to a directory of unpacked files.

Now it needs to point to a loop-mounted ISO via FTP. For example:

root=live:ftp://$SERVER_URL/install/agama-online.iso

agama.install_url=ftp://$SERVER_URL/install/agama

For more information see https://agama-project.github.io/docs/user/boot_options.

==== Disk selection UI problems during installation ====

If you want to enable a disk, click on ''Storage'' in the left panel, then ''Install new system on'' and choose "storage techs". Then you can choose a type of disk. This can be avoided if you have defined your <code>parmfile</code> as described in Section 3.13.5.2, "<code>parmfile</code> now points to ISO".

If you choose DASD, you should see disks based on your <code>parmfile</code> and <code>cio_ignore</code> configuration. Then choose a disk and activate it by clicking ''Perform an action'' and then ''Activate''. This can take a moment. If it is not visible, then you need to click on Storage or refresh the page.

In the ''zFCP'' section, after activating a disk a gray line will appear. This is just a visual bug, the disk will activate correctly.

==== Installation failure on zVM ====

Due to a change from <code>linuxrc</code> to <code>dracut</code>, the <code>parmfile</code> needs to define not only installation source but also a network and disks.

The <code>parmfile</code> needs to be filled with a <code>dracut-like</code> options, for example:

root=live:ftp://$SERVER_URL/install/online.iso

ip=$IP_address::$IP_gateway:24:SLE16-Beta4:$NETWORK_DEVICE:none

rd.zdev=qeth,0.0.0800:0.0.0801:0.0.0802,layer2=1,portno=0

cio_ignore=all,!condev,!0.0.0160 nameserver=$NAMEserverIP

live.password=linux rd.zdev=dasd,0.0.0160

== POWER-specific changes (ppc64le) ==

Information in this section applies to openSUSE Leap for POWER 16.0.

=== KVM guests in LPAR ===

The ability to run KVM Guests in an LPAR is a new feature in PowerVM Firmware 1060.10 release and supported in openSUSE Leap 16.0. This enables users to run KVM guests in a PowerVM LPAR bringing industry standard Linux KVM virtualization stack to IBM PowerVM, which easily integrates with existing Linux virtualization ecosystem. This enables a lot of interesting usecases which were earlier difficult to realize in a PowerVM LPAR.

KVM in a PowerVM LPAR is a new type of LPAR (logical partition) that allows the openSUSE Leap 16.0 kernel to host KVM guests inside an LPAR on PowerVM. A KVM enabled LPAR allows standard Linux KVM tools (for example, <code>virsh</code>) to create and manage lightweight Linux Virtual Machines (VM). A KVM Linux LPAR uses dedicated cores which enables Linux to have full control of when Linux VMs are scheduled to run, just like KVM on other platforms.

=== Login times out on HMC virtual terminal ===

If you install openSUSE Leap for POWER with the GNOME desktop on LPAR and try to login via the HMC virtual terminal, the login may time out while entering your credentials.

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

== Arm-specific changes (AArch64) ==

=== System-on-Chip driver enablement ===

Leap 16.0 includes driver enablement for the following System-on-Chip (SoC) chipsets:

* Ampere* X-Gene*, eMAG*, Altra*, Altra Max, AmpereOne*

* AWS* Graviton, Graviton2, Graviton3

* Broadcom* BCM2837/BCM2710, BCM2711

* Fujitsu* A64FX

* Huawei* Kunpeng* 916, Kunpeng 920

* Marvell* ThunderX*, ThunderX2*; OCTEON TX*; Armada* 7040, Armada 8040

* NVIDIA* Grace; Tegra* X1, Tegra X2, Xavier*, Orin; BlueField*, BlueField-2, BlueField-3

* NXP* i.MX 8M, 8M Mini; Layerscape* LS1012A, LS1027A/LS1017A, LS1028A/LS1018A, LS1043A, LS1046A, LS1088A, LS2080A/LS2040A, LS2088A, LX2160A

* Rockchip RK3399

* Socionext* SynQuacer* SC2A11

* Xilinx* Zynq* UltraScale*+ MPSoC

'''Note'''

Driver enablement is done as far as available and requested. Refer to the following sections for any known limitations.

</div>

Some systems might need additional drivers for external chips, such as a Power Management Integrated Chip (PMIC), which may differ between systems with the same SoC chipset.

For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR) or the Embedded Base Boot Requirements (EBBR), that is, the Unified Extensible Firmware Interface (UEFI) either implementing the Advanced Configuration and Power Interface (ACPI) or providing a Flat Device Tree (FDT) table. If both are implemented, the kernel will default to the Device Tree; the kernel command line argument <code>acpi=force</code> can override this default behavior.

Check for SUSE ''YES!'' certified systems, which have undergone compatibility testing.

== Virtualization ==

* iSCSI boot support is disabled in OVMF images.

=== QEMU ===

QEMU has been updated to version 10.0.2, full list of changes are available at https://wiki.qemu.org/ChangeLog/10.0

Highlights include:

* Removed features: https://qemu-project.gitlab.io/qemu/about/removed-features.html

* Deprecated features: https://qemu-project.gitlab.io/qemu/about/deprecated.html

=== libvirt ===

<code>libvirt</code> has been updated to version 11.4.0, this includes many incremental improvements and bug fixes, see https://libvirt.org/news.html#v11-4-0-2025-06-02.

<code>libvirt</code> provides now a modular daemons.

=== VMware ===

==== <code>open-vm-tools</code> ====

<code>open-vm-tools</code> has been updated to version 13.0.0 that addresses a few critical problems and bug fixes. See https://github.com/vmware/open-vm-tools/blob/stable-13.0.0/ReleaseNotes.md.

=== Confidential Computing ===

==== <code>sevctl</code> ====

The <code>sevctl</code> package has been updated to version 0.6.0.

==== <code>snpguest</code> ====

The <code>snpguest</code> package has been updated to version 0.9.1. Full list of changes is available at: https://github.com/virtee/snpguest/compare/v0.7.1…v0.9.1

==== <code>snphost</code> ====

The <code>snphost</code> package version 0.6.0 has been added.

==== Intel TDX Confidential Computing ====

In openSUSE Leap 16.0 the kernel now incorporates the latest upstream Intel Trust Domain Extensions (TDX) patches. This significant update prepares the virtualization toolstack for Intel TDX confidential computing capabilities.

These patches are important for enabling the kernel to support creating and managing trust domains, which is a step towards enabling confidential computing environments on Intel TDX-enabled hardware.

'''Note'''

The full Intel TDX confidential computing experience also requires integrating QEMU and libvirt components, which will be part of a future update.

</div>

==== Enhanced VM Security with AMD SEV-SNP ====

AMD SEV-SNP (Secure Encrypted Virtualization-Secure Nested Paging) is a hardware security feature in AMD EPYC processors that provides a highly secure and confidential environment for virtual machines (VMs). It offers strong memory confidentiality through per-VM encryption keys and AES encryption, and crucially, robust memory integrity protection to prevent tampering from the hypervisor or other threats. It also provides enhanced isolation and remote attestation capabilities, making it ideal for protecting sensitive data and workloads in untrusted environments like cloud computing. This release fully integrates AMD SEV-SNP for KVM-based virtual machines. This means integrated support in our kernel, along with updated QEMU, Libvirt, and OVMF Firmware. To use AMD SEV-SNP, you’ll need, AMD EPYC™ 3rd Gen Processors (Milan) or newer and SEV-SNP enabled in your system’s BIOS/UEFI.

=== Others ===

==== <code>numatop</code> ====

<code>numatop</code> is available in version 2.5, adding support for Intel GNR and SRF platforms.

==== <code>numactl</code> ====

<code>numactl</code> is shipped in version 2.0.19. Full changes at: https://github.com/numactl/numactl/releases/tag/v2.0.19

==== <code>libguestfs</code> ====

<code>libguestfs</code> has been updated to version 1.55.13.

==== <code>virt-v2v</code> ====

Update to version 2.7.16. While there are no dedicated release notes, you can review the code changes in Github: https://github.com/libguestfs/virt-v2v/tree/v2.7.16

* Implement --parallel=N for parallel disk copies

* Update Translations

* Various fixes

==== <code>virtiofsd</code> ====

The <code>virtiofsd</code> has been updated to 1.12.0.

==== <code>virt-manager</code> ====

<code>virt-manager</code> is now shipped in version 5.0.0. Its preferable to setup VNC for remote viewing and do all the XML editing using the <code>virsh</code> command. Full list of changes is available at https://github.com/virt-manager/virt-manager/releases/tag/v5.0.0

==== virt-bridge-setup ====

virt-bridge-setup is a script designed to simplify network bridge creation on a specified interface using nmcli. It was developed as a replacement for the automatic "yast2 virtualization" bridge creation and is particularly useful for setting up virtualization environments.

Important considerations:

* It supports IPv4 only.

* This is a simple script not intended for complex network scenarios (vlan, bonding, etc…); manual bridge setup is recommended for intricate configurations.

* The script should be run locally (not remotely) immediately after installation and before any custom network configurations.

== 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.

=== Removed features and packages ===

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

* Xorg server has been removed. Only Wayland is supported for graphical display. X11 applications compatibility is provided via XWayland.

* <code>sapconf</code> has been removed. See Section 3.6.7, "<code>saptune</code> replaces <code>sapconf</code>" for more info.

* YaST has been removed. See Section 3.10.1, "Switch from YaST to Cockpit" for more info.

* WSL1 is not supported anymore

* The Xen hypervisor was removed in favor of KVM. You no longer run SLE 16 as Xen host or as paravirtualized guest (PV). Running SLE 16 as fully virtualized Xen guest (HVM) or using using hardware virtualization features (PVH) is still possible.

* <code>nscd</code> has been removed

* The snIPL package is deprecated as HMC is providing most capabilities. There is also available a command line client to interact with the HMC Web Services API: the zhmccli https://github.com/zhmcclient.

* Removed <code>rc<service></code> controls of systemd services

* Removed the <code>KBD_DISABLE_CAPS_LOCK</code> feature from <code>/etc/sysconfig/keyboard</code>

* <code>netiucv</code> and <code>lcs</code> drivers

* <code>ansible-9</code> and <code>ansible-core-2.16</code>

* <code>criu</code>

* Section 3.6.17, "SysV init.d scripts support"

* <code>compat-libpthread-nonshared</code>

* <code>crun</code> has been removed. Use <code>runc</code> instead.

== Deprecated features and packages ==

The following features and packages are deprecated and will be removed in a future version of openSUSE Leap.

* The 2MB OVMF image will be deprecated and removed in openSUSE Leap 16.1.

=== nmap deprecation notice ===

The nmap project has moved to a new source license that makes future releases of nmap incompatible with our product.

In Leap 16.0, we are shipping the latest version of nmap released under the old license. In an upcoming release we will switch to an alternative tool.

= 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 on Medium 2. For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Send requests by e-mail to sle_source_request@suse.com. SUSE may charge a reasonable fee to recover distribution costs.

= Legal notices =

Permission is granted to copy, distribute, and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) Version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.

This document includes content adapted from the SUSE Linux Enterprise release notes, contributed by the SUSE Documentation Team. Portions of the content are maintained by the openSUSE community.

For SUSE trademarks, see https://www.suse.com/company/legal/. For openSUSE trademarks, see https://en.opensuse.org/openSUSE:Trademark_guidelines. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™, etc.) denote trademarks of SUSE, openSUSE, and their affiliates. Asterisks (*) denote third-party trademarks.

While every effort has been made to ensure accuracy, the openSUSE contributors, SUSE Documentation Team, and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.

@@ Line 76: / Line 76: @@
 === AppArmor not available by default on new installations ===
 <div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''
@@ Line 86: / Line 87: @@
 == Steam ==
 <div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''
@@ Line 103: / Line 105: @@
 === Broken libvirt networking when using Docker ===
 <div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''
@@ Line 139: / Line 142: @@
 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.
+= SUSE Linux Enterprise Core =
+== What's new? ==
+=== Package and module changes in 16.0 ===
+The full list of changed packages compared to 15 SP7 can be seen at this URL:
+https://documentation.suse.com/package-lists/sle/16.0/package-changes_SLE-15-SP7-GA_SLE-16.0-GA.txt
+The full list of changed modules compared to 15 SP7 can be seen at this URL:
+https://documentation.suse.com/package-lists/sle/16.0/module-changes_SLE-15-SP7-GA_SLE-16.0-GA.txt
+== 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.
+The current version (16.0) will be fully maintained and supported until 31 Jul 2034.
+If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support duration. You can buy an additional 12 to 36 months in twelve month increments. This means that you can receive support up to Dec 2037.
+For more information, see the pages [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].
+== Support statement for openSUSE Leap ==
+To receive support, you need an appropriate subscription with SUSE. For more information, see https://forums.opensuse.org.
+The following definitions apply:
+;L1
+:Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering, and basic troubleshooting using the documentation.
+;L2
+:Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate the problem area, and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
+;L3
+:Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.
+For contracted customers and partners, openSUSE Leap is delivered with L3 support for all packages, except for the following:
+* Technology Previews, see Section 3.4, "Technology previews"
+* Sound, graphics, fonts and artwork
+* Packages that require an additional customer contract, see Section 3.3.2, "Software requiring specific contracts"
+* 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.
+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:
+* Section 3.16, "Virtualization"
+* Section 3.17, "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>, <code>zypper</code>, or <code>YaST</code>.
+Major packages and groups of packages affected by this are:
+* PostgreSQL (all versions, including all subpackages)
+=== Software under GNU AGPL ===
+openSUSE Leap 16.0 (and the SUSE Linux Enterprise modules) includes the following software that is shipped ''only'' under a GNU AGPL software license:
+* Ghostscript (including subpackages)
+* <code>velociraptor</code> and <code>velociraptor-client</code>
+* <code>zypp-boot-plugin</code>
+openSUSE Leap 16.0 (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:
+* MySpell dictionaries and LightProof
+* ArgyllCMS
+== Technology previews ==
+Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations. Technology previews are included for your convenience to give you a chance to test new technologies within your environment. We would appreciate your feedback! If you test a technology preview, contact your SUSE representative and let them know about your experience and use cases. Your input is helpful for future development.
+Technology previews come with the following limitations:
+* Technology previews are still in development. Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.
+* Technology previews are not supported.
+* Technology previews may only be available for specific hardware architectures. Details and functionality of technology previews are subject to change. As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.
+* Technology previews can be removed from a product at any time. This may be the case, for example, if SUSE discovers that a preview does not meet the customer or market needs, or does not comply with enterprise standards.
+== <code>lklfuse</code> ==
+As technology preview, <code>lklfuse</code> is available in openSUSE Leap 16.0.
+<code>lklfuse</code> is intentionally built without Btrfs support. Btrfs filesystems can be multi-device (for example, RAID1) but <code>lklfuse</code> currently only supports a single device per mount.
+== Changes affecting all architectures ==
+* <code>rasdaemon</code> has been updated to version 8.3.0. This version supports machine checks related to CXL memory.
+* We now provide Grafana Alloy which can integrate with SUSE Observability as well.
+* <code>NetworkManager</code> is now the only network configuration stack in openSUSE Leap 16.0.
+* We now provide a unified image that can be used to install either SLES or SLES for SAP
+=== Userspace live patching ===
+Currently, <code>libpulp</code> supports ULP (user space live patching) of <code>glibc</code> and <code>openssl</code> binaries on the following architectures:
+* x86-64
+* ppc64le
+For more information see https://documentation.suse.com/sles/15-SP7/html/SLES-all/cha-ulp.html
+=== Switch to <code>mountfd</code> API in <code>util-linux</code> ===
+The <code>util-linux</code> mount command has switched from the old string-based method to the new kernel <code>mountfd</code> API. This change introduces new features but also comes with some minor incompatibilities.
+There is a special case that cannot be handled by <code>mountfd</code> and needs to be handled by applications:
+* <code>mountfd</code> discriminates between the physical mount layer and the virtual mount layer
+* once the physical mount layer is read-only, read-write mount on the virtual layer is not possible
+If the first mount is read-only, then the physical filesystem is mounted read-only, and later mounting of the same file system as read-write is not possible. To solve this problem, the first mount needs to be read-only on the virtual layer only, keeping the physical layer read-write. The userspace fix is simple. Instead of:
+ mount -oro
+use
+ mount -oro=vfs
+This will keep the physical layer read-write, but the virtual file system layer (and the userspace access) read-only.
+=== Switch to predictable network names ===
+The persistent network naming scheme used in Leap 15 became legacy with the switch to the systemd predictable network names. For complicated setups, we recommend using <code>systemd.link</code>.
+For more information, see:
+* https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
+* https://www.freedesktop.org/software/systemd/man/latest/systemd.link.html
+<div style="background:#C0C0C0;border:1px solid #666666;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
+'''Note'''
+In the future, when upgrading from SL Micro to Leap 16.1 (so-called "SLE merge"), some systems will have <code>net.ifnames=0</code> set on their kernel command line (this is the case for new installations of SL Micro 6.0 and 6.1). This boot option will prevent the system from switching to the predictable naming scheme and it will need to be removed.
+</div>
+=== systemd default configurations moved to <code>/usr</code> ===
+Main configuration files have been moved from <code>/etc</code> to <code>/usr</code>. This ensures that main configuration files have lower precedence, allowing them to be overriden by package-supplied drop-in snippets.
+Local configuration should be created by either modifying the default file in <code>/usr</code> (or a copy of it placed in <code>/etc</code> if the original file is shipped in <code>/usr</code>), or by creating drop-in snippets in the appropriate directory in (for example, <code>/etc/systemd/coredump.conf.d/</code>) - this is recommended.
+Remove configurations in <code>/etc</code> to restore defaults.
+=== Password access as root via SSH disabled ===
+Previously, it was possible to SSH as root using password-based authentication. In Leap 16.0 only key-based authentication is allowed by default. Systems upgraded to 16.0 from a previous version will carry over the old behavior. New installations will enforce the new behavior.
+Installing the package <code>openssh-server-config-rootlogin</code> restores the old behavior and allows password-based login for the root user.
+=== Minimum hardware requirements ===
+openSUSE Leap 16.0 requires hardware to meet requirements on these architectures:
+* For AMD64 and Intel* 64 systems: Microarchitecture level x86-64-v2 or higher.
+* For IBM* Power LE systems: POWER10 or higher (see note below).
+* For Arm64* systems: Armv8.0-A or higher.
+* For IBM* Z systems: z14 or higher.
+<div style="background:#C0C0C0;border:1px solid #666666;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
+'''Note'''
+POWER9 systems may work with Leap 16.0 but are not supported by IBM, the hardware vendor.
+</div>
+=== SHA1 to be disabled or mark unapproved ===
+Due to FIPS 140-3 certification requirements, the SHA1 cryptographic algorithm will be disabled or marked unapproved when running in FIPS mode.
+=== Added <code>tuned</code> ===
+The <code>tuned</code> package contains a daemon that tunes system settings dynamically.
+=== Lightweight guard region support ===
+This is a new feature in <code>madvise()</code> that installs a lightweight guard region into a specified address range.
+See [https://manpages.opensuse.org/Leap-16.0/man-pages/madvise.2.en.html#MADV_GUARD_INSTALL madvise() man page] for more information.
+=== Harmless error messages sometimes displayed when launching some applications ===
+The following messages are sometimes displayed when launching specific applications:
+# <code>gnome-desktop</code> some times failes to create transient scope:
+#:<pre>> gnome-session-binary: GnomeDesktop-WARNING: Could not create transient scope for PID 7883: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 7883 does not exist.</pre>
+# <code>systemd</code> sometimes fails to assign cgroup:
+#:<pre>> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Couldn't move process 6708 to requested cgroup '/user.slice/user-0.slice/user@0.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope': No such process
+> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed to add PIDs to scope's control group: No such process
+> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed with result 'resources'.
+> systemd: Failed to start Application launched by gnome-session-binary.</pre>
+These messages are harmless and can be ignored.
+=== NFS over TLS support ===
+NFS over TLS is now supported for storage traffic.
+=== <code>saptune</code> replaces <code>sapconf</code> ===
+In Leap 16.0, <code>sapconf</code> is replaced with <code>saptune</code>. <code>saptune</code> will also be enabled with a base tuning, similar to <code>sapconf</code>. Base tuning only will be enabled if <code>saptune</code> was not configured before (no SAP Notes or Solutions selected).
+=== Azure Entra ID authentication via <code>himmelblau</code> ===
+The <code>himmelblau</code> package has been added. It provides interoperability with Microsoft Azure Entra ID and Intune. It supports Linux authentication to Microsoft Azure Entra ID via PAM and NSS modules.
+For more information see https://github.com/himmelblau-idm/himmelblau.
+=== Legacy BIOS support ===
+Legacy BIOS is still supported in openSUSE Leap 16.0. However, some features are not available when using it (for example, full-disk encryption with TPM). Finally, support for legacy BIOS will be discontinued in the future. For that reason we recommend switching to UEFI at the nearest opportunity.
+=== <code>/tmp</code> not persistent ===
+In openSUSE Leap 16.0, <code>/tmp</code> is no longer persistent between reboots but uses <code>tmpfs</code> instead. See https://susedoc.github.io/doc-modular/main/html/SLE-comparison/index.html#sle16-tmp for more information.
+=== Python update strategy ===
+* <code>/usr/bin/python3</code> is currently set to use Python 3.13. In a future minor version update this is likely going to be changed to a newer Python version.
+* openSUSE Leap 16.0 contains around 700 popular Python packages, which form a basic set of functionality for packages that depends on Python and for developing apps without needing to install Python modules from an external provider.
+* We have been working on removing the dependencies of packages and tools on the <code>/usr/bin/python3</code> binary, which means that openSUSE Leap could use a newer version of the Python interpreter in the future. This new Python interpreter will coexist with the previous version that will then be maintained as legacy interpreter for a limited time.
+=== Removal of 32-bit support ===
+openSUSE Leap 16.0 only supports 64-bit binaries. Support for 32-bit binaries (or 31-bit binaries on IBM Z) has been removed.
+This means that statically-linked 32-bit binaries (or 31-bit binaries on IBM Z) and container images cannot be run anymore. 32-bit syscalls are still enabled by default on arm64, and can be enabled on x86_64 via the kernel parameter <code>ia32_emulation</code>. On other architectures it’s disabled without any option to enable it.
+=== Compiling kernel uses non-default compiler ===
+Customers who need to build kernel modules or rebuild the kernel must use the same compiler version the kernel was built with. The kernel is built with <code>gcc</code> version 13, which is not the default compiler. Install the <code>gcc</code> version 13 compiler using the gcc13 package and invoke it with the command <code>gcc-13</code>. This specific compiler version is only supported for building kernel modules and the kernel.
+=== Optimized libraries for newer hardware architectures ===
+We have added support for the glibc-HWCAPS feature which loads optimized versions of libraries for specific newer CPUs automatically.
+The build infrastructure for this feature is enabled for the following libraries:
+* <code>blosc2</code>
+* <code>boost</code>
+* <code>brotli</code>
+* <code>bzip2</code>
+* <code>flac</code>
+* <code>jsoncpp</code>
+* <code>lame</code>
+* <code>leveldb</code>
+* <code>libdb-4_8</code>
+* <code>libgcrypt</code>
+* <code>libiscsi</code>
+* <code>libjpeg-turbo</code>
+* <code>libjxl</code>
+* <code>libmng</code>
+* <code>libnettle</code>
+* <code>libpng16</code>
+* <code>libvorbis</code>
+* <code>libxmlb</code>
+* <code>lz4</code>
+* <code>lzo</code>
+* <code>openjpeg2</code>
+* <code>openssl-3</code>
+* <code>python311</code>
+* <code>python313</code>
+* <code>sqlite3</code>
+* <code>talloc</code>
+* <code>tree-sitter</code>
+* <code>wavpack</code>
+* <code>xxhash</code>
+* <code>xz</code>
+* <code>zlib</code>
+* <code>zopfli</code>
+* <code>zstd</code>
+=== No remote root login with password ===
+<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''
+If you install the system using only a <code>root</code> password and do not provide an SSH key for the root user, <code>sshd</code> will not be enabled automatically after installation. You will not be able to log in remotely as root using the password.
+</div>
+By default, remote password-based <code>root</code> login is disabled. The installer enables the <code>sshd</code> service only when an SSH key for root is configured during setup. To allow remote <code>root</code> login, configure an SSH key for root during installation.
+=== Default user group assignment changed ===
+Previously, all user accounts belonged to a single <code>users</code> group.
+Now instead of being added to the common <code>users</code> group, each new user now gets their own primary group matching their username. This is due to <code>USERGROUPS_ENAB</code> being enabled in <code>/usr/etc/login.defs</code>. This change affects all new installations and upgraded systems that did not change the default <code>/etc/login.defs</code>. This has several consequences:
+* files created by new users are not group-readable by default
+* configurations that used the primary <code>users</code> group as a condition do not work anymore
+* configurations that used the primary or secondary <code>users</code> group as a condition need to have the <code>users</code> group manually added to these user accounts in order to continue to work, for example, to for <code>@users</code> in the sudoers file
+* home directories inherited from a previous system need to standardize the GID of the files by running:
+:<code>find "$HOME" -group users -exec chgrp myuser {} \;</code> or <code>chgrp -R myuser "$HOME"</code> if you did not use any GID other than <code>users</code>
+=== SysV init.d scripts support ===
+SysV init.d scripts have been [https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2/index.html#jsc-SLE-7690 deprecated since Leap 15 SP2].
+In Leap 16.0, support of SysV init.d scripts has been removed.
+== Changes affecting all architectures (RC1) ==
+This section contains information specific to RC1. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.
+=== <code>/etc/services</code> removal ===
+The <code>/etc/services</code> file is just a dummy file that will be removed in the future. Software that appends to it without creating it should have its behavior changed.
+== Changes affecting all architectures (Beta4) ==
+This section contains information specific to Beta4. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.
+=== Configuring network interfaces during installation ===
+Currently, the installer does not allow for setting up network interfaces using the UI. However, in the meantime you can use dracut-like command-line options, for example:
+ ifname=<interface>:<MAC>
+ ip=<interface>:dhcp
+Additionally, the <code>inst.copy_network</code> is not available in Beta4.
+=== SAP workloads on Leap 16.0 ===
+For running SAP workloads on openSUSE Leap 16.0, do the following:
+# Unpack the SAP installer.
+# Run the following commands to change policies:
+#:<pre>semanage boolean -m --on selinuxuser_execmod
+semanage boolean -m --on unconfined_service_transition_to_unconfined_user
+semanage permissive -a snapper_grub_plugin_t
+restorecon -R /</pre>
+# Run the following commands to lable all files:
+#:<pre>test -d ./snapshots && restorecon -R / -e /.snapshots
+test -d ./snapshots || restorecon R /</pre>
+# Install SAP workload or SAP HANA
+# Label all files again:
+#:<pre>test -d /.snapshots && restorecon -R / -e /.snapshots
+test -d /.snapshots || restorecon -R /</pre>
+=== FIPS 140-3 not working properly ===
+FIPS 140-3 installation has not been fully validated and may cause unexpected software failure or crashes. Therefore, we discourage you from using it on Beta4.
+== Changes affecting all architectures (Beta3) ==
+This section contains information specific to Beta3. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.
+=== Kernel crash in QEMU ===
+openSUSE Leap 16.0 requires a CPU that supports a so-called "x86-64-v2" microarchitecture. Due to this, running a Leap image using QEMU currently results in a kernel crash.
+As a workaround you can run QEMU with the <code>-cpu host</code> argument.
+=== Missing <code>libnsl.so.1</code> library ===
+The <code>libnsl.so.1</code> library has been deprecated in SLES 15 and finally removed in openSUSE Leap 16.0.
+As a workaround for applications that cannot be installed without it (but presumaly do not use it for anything), we provide the <code>libnsl-stub1</code> package that includes ABI-compatible but otherwise function-less stub of the library file.
+=== <code>firewalld</code> not usable with many interfaces ===
+Due to an upstream bug, <code>firewalld</code> might take a long time or time out when adding many interfaces. The error occurs when <code>firewalld</code> is restarted after applying such a configuration. The following message appears in the system logs:
+ ERROR:dbus.proxies:Introspect error on :1.18:/org/fedoraproject/FirewallD1: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
+ Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
+See https://github.com/firewalld/firewalld/issues/1399 for more information.
+== Changes affecting all architectures (Beta2) ==
+This section contains information specific to Beta2. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.
+=== Switch from YaST to Cockpit ===
+openSUSE Leap 16.0 has switched from YaST to Cockpit for manual system administration. We have enhanced Cockpit with new modules with the intention to upstream them later. Despite being functional, bugs might appear and features might be missing.
+'''New modules'''
+* <code>cockpit-subscriptions</code>: register, de-register and view SUSE Linux Enterprise registrations. Does not work for unprivileged users yet.
+* <code>cockpit-repositories</code>: add, remove, view repositories, change settings and refresh them. Does not work for unprivileged users yet.
+* <code>cockpit-packages</code>: show installed packages, search available repositories, install and uninstall packages. Requires administrative access. Be aware that there are no safety measures implemented as far as system usability goes.
+'''Enhanced modules'''
+* <code>cockpit-packagekit</code>: update packages from available repositories. The module now allows to individually select packages to update.
+'''Upstream modules'''
+<code>cockpit</code>, <code>cockpit-bridge</code>, <code>cockpit-kdump</code>, <code>cockpit-machines</code>, <code>cockpit-networkmanager</code>, <code>cockpit-podman</code>, <code>cockpit-selinux</code>, <code>cockpit-storaged</code>, <code>cockpit-system</code>, <code>cockpit-ws</code>: these modules are updated to the recent stable base version 332 (or their respective).
+'''Default selection'''
+Installation of the pattern <code>cockpit</code> will pull in the following modules: <code>cockpit</code>, <code>cockpit-bridge</code>, <code>cockpit-networkmanager</code>, <code>cockpit-packagekit</code>, <code>cockpit-packages</code>, <code>cockpit-repos</code>, <code>cockpit-selinux</code>, <code>cockpit-storaged</code>, <code>cockpit-subscriptions</code>, <code>cockpit-system</code>, <code>cockpit-ws</code>.
+=== <code>dovecot 2.4</code> configuration upgrade ===
+In openSUSE Leap 16.0 <code>dovecot</code> has been upgraded to version 2.4. The configuration of this version is incompatible with the previous versions.
+Configuration has to be updated manually. For more information see https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html.
+== Changes affecting all architectures (Beta1) ==
+This section contains information specific to Beta1. We are working on fixing the problems mentioned here. The content of this section will be removed for the final released product.
+=== Disk configuration UI during installation ===
+Currently, choosing disk configurations other than "An existing disk" (installation to a single disk) suffer from poor usability. This is expected to change in a future update.
+=== Non-functioning <code>zypper</code> after installation ===
+There is currently a known issue that adds a non-functioning <code>zypper</code> repository which prevents <code>zypper</code> from working correctly.
+To fix this issue, remove the repository in question and add the installation medium repository manually:
+# Remove repository with <code>zypper rr</code>. To remove the first repository, for example, run: <code>zypper rr 1</code>.
+# Add the installation medium as repository by running
+#:<pre>zypper ar hd:/install?device=/dev/disk/by-label/agama-installer medium</pre>
+#:(the <code>medium</code> at the end is a name you want to give the repository).
+# Run <code>zypper refresh</code> to refresh the added repository.
+=== systemd uses cgroup v2 by default ===
+openSUSE Leap 16.0 uses cgroup v2 by default and v1 is unsupported. If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.
+== x86-64-specific changes ==
+Information in this section applies to the x86-64 architecture.
+=== AMD EPYC Turin automonous frequency scaling ===
+In Leap 16.0, the default Linux CPU frequency scaling driver for AMD EPYC Turin (and later processors) has shifted to the AMD P-State driver to enable autonomous frequency scaling.
+With the AMD P-State driver, it enables the use of the Energy Performance Preference (EPP) for more granular control over performance versus power efficiency to adjust the CPU frequencies based on workload and hardware feedback dynamically.
+== IBM Z-specific changes (s390x) ==
+Information in this section applies to openSUSE Leap for IBM Z 16.0. For more information, see https://www.ibm.com/docs/en/linux-on-systems?topic=distributions-suse-linux-enterprise-server
+=== Hardware ===
+* Support has been added for IBM z17 in <code>kernel</code> providing machine name, kconfig options, new instructions, etc.
+* Support has been added for IBM z17 in <code>gdb</code>, <code>valgrind</code>, <code>binutils</code>
+* Support has been added for IBM z16 - reset DAT-Protection facility support
+* Identify ConnectX devices through port rather than PCHID
+* Processor Activity Instrumentation / Neural Network Processing Assist counters for new IBM Z hardware was added into kernel
+* kprobes are now supported without <code>stop machine</code>
+* Promiscuous Mode Exploitation for NETH Virtual Functions for IBM z17 and LinuxONE 5
+* Vertical CPU Polarization support for IBM z17 and LinuxONE 5
+* qclib has been updated to support IBM z17
+* The Integrated Accelerator for AI has new operations, which are now supported by libzdnn low-level driver library
+* Enhanced RAS and Call Home for zPCI
+* The kernel image can move into vmalloc space, where random physical pages are used to map virtual pages (V!=R)
+* Add new CPU-MF Counters for new IBM Z Hardware (libpfm)
+* Deactivate CONFIG_QETH_OSX kernel config option
+* Upgrade Mellanox (mlx5) driver to latest version
+=== Performance ===
+* LPAR level power consumption reporting is now available in kernel and s390-tools.
+=== Security ===
+==== In-kernel crypto support ====
+With this service pack are additionally supported:
+* MSA 10 XTS instructions for in-kernel crypto
+* MSA 11 HMAC instructions for in-kernel crypto
+* MSA 12 (SHA3) has been added and introduces new options to call CPACF SHA 3 functions
+* MSA 11 HMAC instructions for in-kernel crypto
+* MSA 10 XTS crypto PAES support for in-kernel crypto
+==== OpenSSL features ====
+This release brings these features and improvements:
+* XTS instructions support in libcrypto/openSSL
+* New MSA 11 HMAC instruction support in libcrypto/openSSL
+* Added support for MSA 12 (SHA3), which also introduces new options to call CPACF SHA3 and SHKE functions
+* Extended support of the openssl-pkcs11 provider such that it can be used by programs that issue forks
+* Replace openssl-ibmpkcs11 with openssl-pkcs11
+* Upgrade openssl-ibmca to the latest version
+==== openCryptoki ====
+* The new version of <code>libica</code> and <code>libzpc</code> is included.
+* The openCryptoki CCA Token is now available on x86_64 and ppc64le architectures.
+==== p11-kit =====
+* Add support for IBM specific attributes and mechanisms to the PKCS11 client-server implementation of p11-kit.
+==== pkey ====
+* The kernel pkey module can now generate keys AES-XTS keys (MSA 10) and HMAC key (MSA 11) from clear keys.
+* The module can also generate keys represented by identifiers of secure execution retrievable keys.
+* The pkey also supports EP11 API ordinal 6 for secure guests.
+==== zcrypt =====
+* The zcrypt extends error recovery to deal with device scans of unavailable devices.
+=== Virtualization ===
+* KVM guests can exploit z17 & LinuxONE 5 CPU features
+* KVM can display available host key hashes for Secure Execution (Query Host-key hash UVC)
+* KVM can benefit from genprotimg rewritten in Rust to re-use existing rust libraries (s390-tools feature)
+* KVM benefits from genprotimg validation of SE image running on particular host(s) (s390-tools feature)
+* KVM benefits from using pvimg info command to display encrypted & unencrypted SE image information (s390-tools)
+* KVM can use unencrypted SE images for creating generic images (s390-tools feature)
+* KVM passthrough is available for guests i.e. retrievable secrets in Secure Execution guests
+* KVM can use unencrypted SE images for creating generic images (s390-tools feature)
+* KVM implements counters for nested guest shadow events
+* KVM implements virsh hypervisor-cpu-models (libvirt)
+* KVM provides enhanced and dynamic CPU topology for KVM guests (qemu)
+* KVM and libvirt full boot order enables users to attempt booting from multiple targets
+* KVM provides Atomic Memop for Key-Checked Compare-and-swap
+* KVM enhances CCW address translation architectural compliance
+* KVM improves memory reclaiming for z15 Secure Execution guests and above (libvirt)
+=== Miscellaneous ===
+* <code>plymouth</code> was replaced by <code>blog</code> on s390x, as <code>plymouth</code> couldn't work without graphical display.
+* The <code>Eigen</code> library is the backend used by <code>Tensorflow</code> for computations executed on the CPU. Several GCC adjustments have been implemented to speed up Eigen with IBM z14 support and above.
+* Allow <code>httpd</code> customers to protect their web server identity using HSMs (via CryptoExpress adapters).
+==== Enhancements in <code>s390-tools</code> ====
+The latest s390-tool update brings these noticeable changes:
+* Additional channel measurements - kernel & <code>s390-tools</code>
+* A new tool cpacinfo shall provide information on CPACF including the supported MSA levels, instructions, subfunctions per instruction. https://www.ibm.com/docs/en/linux-on-systems?topic=hw-cpacf
+==== <code>parmfile</code> now points to ISO ====
+Previously, <code>parmfile</code> would point to a directory of unpacked files.
+Now it needs to point to a loop-mounted ISO via FTP. For example:
+ root=live:ftp://$SERVER_URL/install/agama-online.iso
+ agama.install_url=ftp://$SERVER_URL/install/agama
+For more information see https://agama-project.github.io/docs/user/boot_options.
+==== Disk selection UI problems during installation ====
+If you want to enable a disk, click on ''Storage'' in the left panel, then ''Install new system on'' and choose "storage techs". Then you can choose a type of disk. This can be avoided if you have defined your <code>parmfile</code> as described in Section 3.13.5.2, "<code>parmfile</code> now points to ISO".
+If you choose DASD, you should see disks based on your <code>parmfile</code> and <code>cio_ignore</code> configuration. Then choose a disk and activate it by clicking ''Perform an action'' and then ''Activate''. This can take a moment. If it is not visible, then you need to click on Storage or refresh the page.
+In the ''zFCP'' section, after activating a disk a gray line will appear. This is just a visual bug, the disk will activate correctly.
+==== Installation failure on zVM ====
+Due to a change from <code>linuxrc</code> to <code>dracut</code>, the <code>parmfile</code> needs to define not only installation source but also a network and disks.
+The <code>parmfile</code> needs to be filled with a <code>dracut-like</code> options, for example:
+ root=live:ftp://$SERVER_URL/install/online.iso
+ ip=$IP_address::$IP_gateway:24:SLE16-Beta4:$NETWORK_DEVICE:none
+ rd.zdev=qeth,0.0.0800:0.0.0801:0.0.0802,layer2=1,portno=0
+ cio_ignore=all,!condev,!0.0.0160 nameserver=$NAMEserverIP
+ live.password=linux rd.zdev=dasd,0.0.0160
+== POWER-specific changes (ppc64le) ==
+Information in this section applies to openSUSE Leap for POWER 16.0.
+=== KVM guests in LPAR ===
+The ability to run KVM Guests in an LPAR is a new feature in PowerVM Firmware 1060.10 release and supported in openSUSE Leap 16.0. This enables users to run KVM guests in a PowerVM LPAR bringing industry standard Linux KVM virtualization stack to IBM PowerVM, which easily integrates with existing Linux virtualization ecosystem. This enables a lot of interesting usecases which were earlier difficult to realize in a PowerVM LPAR.
+KVM in a PowerVM LPAR is a new type of LPAR (logical partition) that allows the openSUSE Leap 16.0 kernel to host KVM guests inside an LPAR on PowerVM. A KVM enabled LPAR allows standard Linux KVM tools (for example, <code>virsh</code>) to create and manage lightweight Linux Virtual Machines (VM). A KVM Linux LPAR uses dedicated cores which enables Linux to have full control of when Linux VMs are scheduled to run, just like KVM on other platforms.
+=== Login times out on HMC virtual terminal ===
+If you install openSUSE Leap for POWER with the GNOME desktop on LPAR and try to login via the HMC virtual terminal, the login may time out while entering your credentials.
+To work around this issue, disable the Plymouth graphical boot screen by appending the boot parameter <code>plymouth.enable=0</code> to the kernel command line.
+== Arm-specific changes (AArch64) ==
+=== System-on-Chip driver enablement ===
+Leap 16.0 includes driver enablement for the following System-on-Chip (SoC) chipsets:
+* Ampere* X-Gene*, eMAG*, Altra*, Altra Max, AmpereOne*
+* AWS* Graviton, Graviton2, Graviton3
+* Broadcom* BCM2837/BCM2710, BCM2711
+* Fujitsu* A64FX
+* Huawei* Kunpeng* 916, Kunpeng 920
+* Marvell* ThunderX*, ThunderX2*; OCTEON TX*; Armada* 7040, Armada 8040
+* NVIDIA* Grace; Tegra* X1, Tegra X2, Xavier*, Orin; BlueField*, BlueField-2, BlueField-3
+* NXP* i.MX 8M, 8M Mini; Layerscape* LS1012A, LS1027A/LS1017A, LS1028A/LS1018A, LS1043A, LS1046A, LS1088A, LS2080A/LS2040A, LS2088A, LX2160A
+* Rockchip RK3399
+* Socionext* SynQuacer* SC2A11
+* Xilinx* Zynq* UltraScale*+ MPSoC
+<div style="background:#C0C0C0;border:1px solid #666666;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
+'''Note'''
+Driver enablement is done as far as available and requested. Refer to the following sections for any known limitations.
+</div>
+Some systems might need additional drivers for external chips, such as a Power Management Integrated Chip (PMIC), which may differ between systems with the same SoC chipset.
+For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR) or the Embedded Base Boot Requirements (EBBR), that is, the Unified Extensible Firmware Interface (UEFI) either implementing the Advanced Configuration and Power Interface (ACPI) or providing a Flat Device Tree (FDT) table. If both are implemented, the kernel will default to the Device Tree; the kernel command line argument <code>acpi=force</code> can override this default behavior.
+Check for SUSE ''YES!'' certified systems, which have undergone compatibility testing.
+== Virtualization ==
+* iSCSI boot support is disabled in OVMF images.
+=== QEMU ===
+QEMU has been updated to version 10.0.2, full list of changes are available at https://wiki.qemu.org/ChangeLog/10.0
+Highlights include:
+* Removed features: https://qemu-project.gitlab.io/qemu/about/removed-features.html
+* Deprecated features: https://qemu-project.gitlab.io/qemu/about/deprecated.html
+=== libvirt ===
+<code>libvirt</code> has been updated to version 11.4.0, this includes many incremental improvements and bug fixes, see https://libvirt.org/news.html#v11-4-0-2025-06-02.
+<code>libvirt</code> provides now a modular daemons.
+=== VMware ===
+==== <code>open-vm-tools</code> ====
+<code>open-vm-tools</code> has been updated to version 13.0.0 that addresses a few critical problems and bug fixes. See https://github.com/vmware/open-vm-tools/blob/stable-13.0.0/ReleaseNotes.md.
+=== Confidential Computing ===
+==== <code>sevctl</code> ====
+The <code>sevctl</code> package has been updated to version 0.6.0.
+==== <code>snpguest</code> ====
+The <code>snpguest</code> package has been updated to version 0.9.1. Full list of changes is available at: https://github.com/virtee/snpguest/compare/v0.7.1…v0.9.1
+==== <code>snphost</code> ====
+The <code>snphost</code> package version 0.6.0 has been added.
+==== Intel TDX Confidential Computing ====
+In openSUSE Leap 16.0 the kernel now incorporates the latest upstream Intel Trust Domain Extensions (TDX) patches. This significant update prepares the virtualization toolstack for Intel TDX confidential computing capabilities.
+These patches are important for enabling the kernel to support creating and managing trust domains, which is a step towards enabling confidential computing environments on Intel TDX-enabled hardware.
+<div style="background:#C0C0C0;border:1px solid #666666;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
+'''Note'''
+The full Intel TDX confidential computing experience also requires integrating QEMU and libvirt components, which will be part of a future update.
+</div>
+==== Enhanced VM Security with AMD SEV-SNP ====
+AMD SEV-SNP (Secure Encrypted Virtualization-Secure Nested Paging) is a hardware security feature in AMD EPYC processors that provides a highly secure and confidential environment for virtual machines (VMs). It offers strong memory confidentiality through per-VM encryption keys and AES encryption, and crucially, robust memory integrity protection to prevent tampering from the hypervisor or other threats. It also provides enhanced isolation and remote attestation capabilities, making it ideal for protecting sensitive data and workloads in untrusted environments like cloud computing. This release fully integrates AMD SEV-SNP for KVM-based virtual machines. This means integrated support in our kernel, along with updated QEMU, Libvirt, and OVMF Firmware. To use AMD SEV-SNP, you’ll need, AMD EPYC™ 3rd Gen Processors (Milan) or newer and SEV-SNP enabled in your system’s BIOS/UEFI.
+=== Others ===
+==== <code>numatop</code> ====
+<code>numatop</code> is available in version 2.5, adding support for Intel GNR and SRF platforms.
+==== <code>numactl</code> ====
+<code>numactl</code> is shipped in version 2.0.19. Full changes at: https://github.com/numactl/numactl/releases/tag/v2.0.19
+==== <code>libguestfs</code> ====
+<code>libguestfs</code> has been updated to version 1.55.13.
+==== <code>virt-v2v</code> ====
+Update to version 2.7.16. While there are no dedicated release notes, you can review the code changes in Github: https://github.com/libguestfs/virt-v2v/tree/v2.7.16
+* Implement --parallel=N for parallel disk copies
+* Update Translations
+* Various fixes
+==== <code>virtiofsd</code> ====
+The <code>virtiofsd</code> has been updated to 1.12.0.
+==== <code>virt-manager</code> ====
+<code>virt-manager</code> is now shipped in version 5.0.0. Its preferable to setup VNC for remote viewing and do all the XML editing using the <code>virsh</code> command. Full list of changes is available at https://github.com/virt-manager/virt-manager/releases/tag/v5.0.0
+==== virt-bridge-setup ====
+virt-bridge-setup is a script designed to simplify network bridge creation on a specified interface using nmcli. It was developed as a replacement for the automatic "yast2 virtualization" bridge creation and is particularly useful for setting up virtualization environments.
+Important considerations:
+* It supports IPv4 only.
+* This is a simple script not intended for complex network scenarios (vlan, bonding, etc…); manual bridge setup is recommended for intricate configurations.
+* The script should be run locally (not remotely) immediately after installation and before any custom network configurations.
+== 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.
+=== Removed features and packages ===
+The following features and packages have been removed in this release.
+* Xorg server has been removed. Only Wayland is supported for graphical display. X11 applications compatibility is provided via XWayland.
+* <code>sapconf</code> has been removed. See Section 3.6.7, "<code>saptune</code> replaces <code>sapconf</code>" for more info.
+* YaST has been removed. See Section 3.10.1, "Switch from YaST to Cockpit" for more info.
+* WSL1 is not supported anymore
+* The Xen hypervisor was removed in favor of KVM. You no longer run SLE 16 as Xen host or as paravirtualized guest (PV). Running SLE 16 as fully virtualized Xen guest (HVM) or using using hardware virtualization features (PVH) is still possible.
+* <code>nscd</code> has been removed
+* The snIPL package is deprecated as HMC is providing most capabilities. There is also available a command line client to interact with the HMC Web Services API: the zhmccli https://github.com/zhmcclient.
+* Removed <code>rc<service></code> controls of systemd services
+* Removed the <code>KBD_DISABLE_CAPS_LOCK</code> feature from <code>/etc/sysconfig/keyboard</code>
+* <code>netiucv</code> and <code>lcs</code> drivers
+* <code>ansible-9</code> and <code>ansible-core-2.16</code>
+* <code>criu</code>
+* Section 3.6.17, "SysV init.d scripts support"
+* <code>compat-libpthread-nonshared</code>
+* <code>crun</code> has been removed. Use <code>runc</code> instead.
+== Deprecated features and packages ==
+The following features and packages are deprecated and will be removed in a future version of openSUSE Leap.
+* The 2MB OVMF image will be deprecated and removed in openSUSE Leap 16.1.
+=== nmap deprecation notice ===
+The nmap project has moved to a new source license that makes future releases of nmap incompatible with our product.
+In Leap 16.0, we are shipping the latest version of nmap released under the old license. In an upcoming release we will switch to an alternative tool.
+= 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 on Medium 2. For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Send requests by e-mail to sle_source_request@suse.com. SUSE may charge a reasonable fee to recover distribution costs.
+= Legal notices =
+Copyright © 2025-2025 openSUSE contributors and SUSE LLC. All rights reserved.
+Permission is granted to copy, distribute, and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) Version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.
+This document includes content adapted from the SUSE Linux Enterprise release notes, contributed by the SUSE Documentation Team. Portions of the content are maintained by the openSUSE community.
+For SUSE trademarks, see https://www.suse.com/company/legal/. For openSUSE trademarks, see https://en.opensuse.org/openSUSE:Trademark_guidelines. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™, etc.) denote trademarks of SUSE, openSUSE, and their affiliates. Asterisks (*) denote third-party trademarks.
+While every effort has been made to ensure accuracy, the openSUSE contributors, SUSE Documentation Team, and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.