Last Update: 2018-03-08

Table of Contents

5 themes for SLE 15
Technical Details
Planned Releases
Release Notes
Known Issues
Report Issues
Mailing list
Frequently Asked Questions
Why are there 3 ISOs available?
Error message when trying to download isos
Beta Test Subscription and Registration Code
Updating from SLE 15 Beta X to SLE 15 Beta X+N
Updating from SLE 12 or SLE 11 to SLE 15 Beta X
How to check the beta version of an installed system?
Will SUSE Linux Enterprise Server support a specific Intel microarchitecture ?
Private channel for sensitive data
Contact Beta Manager


Welcome to the dedicated web page for the beta of SUSE Linux Enterprise Server (SLES®), SUSE Linux Enterprise Desktop (SLED®) and SUSE Linux Enterprise High Availability (SLEHA). They are all part of the SUSE Linux Enterprise products family, share a common code base and have the same planned release, from Beta to First Customer Shipment.

SUSE Linux Enterprise 15 Beta will be our new major release designed for IT Transformation! SLE 15 is developed with both “Traditional Infrastructure” and “Software-Defined Infrastructure” in mind, thus significant and major changes from the previous SUSE Linux Enterprise 12 are made to address both world in a more elegant and simpler way.

5 key objectives for SLE 15

  • Address traditional & containerized infrastructure and provide a common code base for traditional and agile data center.
  • Install all SUSE Linux Enterprise 15 products starting from a single medium.
  • Hassle-free use of modules & extensions and easily search, install, and use packages across the SUSE universe.
  • Multiple architectures and deployment scenarios available on: X86_64, Power LE, System z, ARM64, for physical, virtual, host and guest, and cloud.
  • Compliance & Secure Development, Be compliant to regulations, built using a secure development model.

Technical details:

Major changes from previous SLE versions:

  • Linux Kernel 4.12
  • GCC7 as system compiler
    • Will stay the same during SLE15 lifetime
    • Yearly updates will be provided on top
  • OpenSSL
    • 1.1.x as default
    • 1.0.x available in the Legacy Module for a grace period
  • Scripting Languages
    • Ruby 2.5
      • Pre-releases, final version available in December 2017
    • PHP7
    • Perl 5.26
    • Python 3.6
      • Python 2 will be in the Legacy Module for a grace period
  • GNOME 3.26
  • High Availability
    • Hawk2 – UI improvements
    • DRDB multi-node three-way replication
    • cluster-raid 10 (as Technical Preview)
  • New Applications
    • 389-DS will replace openLDAP
      • openLDAP libraries still available
    • Chrony will replace ntpd
      • ntpd will be in the Legacy Module for a grace period
    • Firewalld will replace SUSEFirewall2
    • Wayland will be by default for SUSE Linux Enterprise Desktop (thus only for x86-64)
  • Other Changes
    • SALT in Basesystem Module
    • TLS 1.3
    • Improved Package Search across Modules
    • Nvdimm improvements
    • OpenJDK 9
  • …and much more…
  • Check out our DRAFT Release Notes for more information.


Planned Releases

Scheduled releases:

  • Beta 1October 7, 2017
  • Beta 2November 9, 2017
  • Beta 3November 22, 2017
  • Beta 4December 7, 2017
  • Beta 5January 23, 2018
  • Beta 6February 1, 2018
  • Beta 7February 15, 2018
  • RC 1March 1, 2018
  • RC 2March 22, 2018
  • RC 3April 12, 2018



Please note that we reserve the right to change or adapt this schedule depending on various factors. Rest assured that we will communicate if there is any change of plan.



architectures: aarch64, ppc64le, s390x and x86_64.



Note: The following Documentations are drafts.

And will remain as such through out the SLE Beta Program. Documentations for Beta Products do not yet have the quality, accuracy and content of our official documentations. However we will update these documentations on the fly during the SLE Beta Program.


Release Notes

Fixed bugs in RC1 (selection): 

  • Existing swap partition is handled as ordinary filesystem [Bug 1080926]
  • Many YaST components were updated and received a lot of enhancements and fixes.
  • Added packages (across all modules):

a52dec, alacarte, apache-pdfbox, boost, bzr, cal10n, c-ares, cargo, check, createrepo_c, cscope, delayacct-utils, dmraid, FastCGI, fftw3_3_3_6-gnu-openmpi2-hpc, flatpak-builder, glade, glew, gnustep-base, gstreamer-plugins-ugly, hdf5_1_10_1-gnu-openmpi2-hpc, installation-images-SLES_SAP, installation-images-SLES, kiwi-boot-descriptions, libcap1, libGLw, liboping, libpst, libqt5-qt3d, libqt5-qtquickcontrols2, libqt5-qtsensors, libqt5-qtwayland, libqt5xdg, libyui-qt-graph, meanwhile, meld, monitoring-plugins, mpiP_3_4_1-gnu-openmpi2-hpc, netcdf_4_4_1_1-gnu-mvapich2-hpc, netcdf_4_4_1_1-gnu-openmpi2-hpc, netcdf-fortran_4_4_4-gnu-openmpi2-hpc, openmpi_2_1_2-gnu-hpc, openmpi_2_1_2-gnu-hpc-testsuite, openmpi2, petsc_3_8_3-gnu-mpich-hpc, petsc_3_8_3-gnu-mvapich2-hpc, petsc_3_8_3-gnu-openmpi2-hpc, petsc, pixz, prctl, procinfo, purple-import-empathy, pv, python-kiwi, rust, scalapack_2_0_2-gnu-openmpi2-hpc, shim, stunnel, tidyp, u-boot, unar, vala, yast2-rmt.

Migration from SLE 12 to SLE 15:

  • Offline migration:
    By using SLE-15-Installer and SLE-15-Packages isos manually. Boot on the SLE-15-Installer, then select and follow the “Upgrade” wizard. Make sure you add the SLE-15-Packages DVD as the source for the SLE 15 Modules.
  • Online migration:
    By using a SLE 15 Beta Registration Code on a SLE 12 instance and booting on the SLE-15-Installer. Then select and follow the “Upgrade” wizard. Make sure your network setting is done so the SLE-15-Installer will be able to contact our SCC or your SMT/SUSE Manager as source for the SLE 15 Modules.


Here are the complete rpm changelogs between Beta for all packages in all modules on all architectures:


Known Issues

    • bootloader installed into extended partition while it was instructed to install into root partition [Bug 1080924]
    • a subvolume is not created for home if /home is not a separate partition and root partition is using btrfs. This might cause data loss if rollback is used [bsc#1084261]
    • Kernel reports error “BUG: Bad page state in process xx” [BSC#1082743] -> We plan a maintenance update of the kernel for this.
    • SLE12 AutoYast profile need to be adapted: you need to specify which product is installed in the software section:
      <products config:type="list">
          <product>SLES15</product> (or SLED15)
  • SLES:
    • XEN: the first time you try to connect to the domain with virt-manager there is a connection error, re-launch it will fix the problem [bsc#1076932]
  • SLED/WE:
    • No default pattern is selected when installing Workstation extension on SLES [bsc#1083611]
    • Evolution (and webkit2gtk applications) crashes when used on wayland with unaccelerated drivers (mostly VT related) [bsc#1079512]
  • HA/HA-GEO:
    • crmsh has been ported to python3, please report any trouble using it
  • SDK:
    • doesn’t exist anymore, devel packages are being integrated in the various modules;
    • If you need development applications you should add the “Development Module”.


Warning: Beta Registration Code

Registration is not working with your regular SLE key, special Beta Registration Code is required. Thus, you don’t have access to the SLE online channels/repositories and Modules without a Beta Registration Code.
Please refer to the FAQ for more on how to request a Beta Registration Code.


Report Issues

Mailing List is our dedicated Mailing List to discuss SUSE Linux Enterprise Beta products. It is used by the SUSE Release Team to announce new beta images and technical information, as well as for general or technical questions, feedback, or defect reports related to SUSE Linux Enterprise Beta products from our beta testers base.Only subscribers can post to our mailing lists. To subscribe, please go to

Only subscribers can post to our mailing lists. To subscribe, please go to

Please refer to our Mailing Lists Guideline for more information.



Here are the links to the SLE Bugzilla product that you will use for reporting the defects of the following products:

Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla

Frequently Asked Questions
– Why are there 3 ISOs available?

We offer 3 DVD ISOs, for instance we have:

  • SLE-15-Installer-DVD-x86_64-BetaX-DVD1.iso = DVD1 contains the binaries
  • SLE-15-Installer-DVD-x86_64-BetaX-DVD2.iso = DVD2 the sources
  • SLE-15-Installer-DVD-x86_64-BetaX-DVD3.iso = DVD3 the debuginfo packages

For installation purposes you just need DVD 1 for your architecture. Please verify the sha256sum of the ISO using the SHA256SUMS file, which can also be found on the download page.


Note: Final Product and Debuginfo

We are providing the DVD3 (debuginfo packages) as DVD media for the SLE Beta Program, but the final product will not! However it will only be accessible as an Online Channel.


– Error message when trying to download isos

Well, sorry for the inconvenience, please report your issue to
One quick workaround would be to remove and cookies from you browser and try again.


– Beta Subscription and Registration Code



Regular product subscription and registration code will not work with the beta products!

The Beta Registration Code is the key to unlock the Beta Subscription in our SUSE Customer Center.
The Beta Subscription consist of giving access to our SLE 15 Beta Online Channels.

We will not provide a beta product subscription or beta product registration code by default for the SLE 15 Beta Program. You might request one via, please specify if you want a registration code for SLES, SLED, SLEHA
or for all of them.

Without a beta registration code for SLES 15 Beta, you won’t be able to access the online SLE 15 Modules.


– Updating from SLE 15 Beta X to SLE 15 Beta X+N

Even if it’s completely feasible and working, we do not recommend to update from “SLE 15 Beta X” to “SLE 15 Beta X+N” for your thorough beta testing.

Because this scenario is specific to beta and can not be compared to any SLE production update scenario. During the beta phase of our products, we need the flexibility of doing important changes to packages (libraries, configuration
files, features, etc), like upgrading or downgrading to different versions.
Thus changes between SLE Beta might look very different from regular updates we make in official SLE Service Pack releases.

We highly recommend to test the following scenarios, whenever a new Beta version is released:

  • Fresh install of SLE 15 Beta X+N,
  • Migration from SLE 12 SPX-N to SLE 15 Beta X+N.


– Migrating from SLE 12 or SLE 11 to SLE 15 Beta X

Since SLE 15 Beta 6, we have made the necessary changes to our SCC Online Channels setup for SLE 15 to allow beta testing the migration to SLE15. Please note that only the migration from SLE 12 to SLE 15 Beta is supported at the moment. More information on the migration from SLE 11 to SLE 15 Beta will come later on.


– How to check the beta version of an installed system?
# grep betaversion /etc/products.d/*
/etc/products.d/baseproduct: <betaversion>Beta4<betaversion>
/etc/products.d/ <betaversion>Beta4</betaversion>
/etc/products.d/ <betaversion>Beta4</betaversion>
/etc/products.d/ <betaversion>Beta4</betaversion>
/etc/products.d/ <betaversion>Beta4</betaversion>
/etc/products.d/ <betaversion>Beta4</betaversion>
/etc/products.d/ <betaversion>Beta4</betaversion>


– Will SUSE Linux Enterprise Server support a specific Intel microarchitecture?

Please read the SUSE Linux Enterprise Server–Support for Intel Server Platforms document.


– Private channel for sensitive data

In case you are a SUSE’s partners or customers and would like to share some sensitive data with us for multiple reasons (data for bug reports, feedbacks, etc).
Please contact us at, and we will review your case and help you have a private channel with us.


– Contact Beta Manager

For questions related to the beta test infrastructure, for example download issues or problems with reporting bugs or the mailing list, please write to