Last Update: 2024-08-21

Table of Contents

Introduction

Welcome to the dedicated web page for the beta of SUSE Linux Enterprise Micro (SLE Micro). SLE Micro leverages the enterprise-hardened technology components of SUSE Linux Enterprise and merges that with what developers want from a modern, secure, immutable OS platform. As a result, you get an ultra-reliable infrastructure platform that is also simple to use and comes out-of-the-box with best-in-class compliance.

Using SUSE Linux Enterprise Micro, you can build and scale differentiating systems across a wide range of industries including aerospace, telecom, automotive, defense, healthcare, hospitality, and manufacturing. SUSE Linux Enterprise Micro 6.1 is available on the AMD64 and Intel* 64 (x86_64), Arm* 64, IBM* POWER (ppc64le) and IBM* z System or LinuxONE (s390x) hardware architectures. For more information, please refer Release Notes.

Notable Changes

  • PED-8466 - SLE Micro 6.1 adds general support for the IBM Power platform (ppc64le) to the product. It requires at least IBM Power9. IBM Power8 is not supported. The support for IBM Power is currently still in progress and not yet finalized.
  • PED-8686 - Added soft-reboot support
  • SMO-353 - Include vhostmd for SAP Virtualization
  • PED-8599 - Secure offline updates from USB thumb drives
  • PED-8234 - chrony-pool-empty for SLE Micro
  • PED-8497 - pf-bb-config available on SLE Micro

 

Download

SLE Micro 6.1 is available on the following architectures: aarch64, ppc64le, s390x and x86_64.

aarch64

ppc64le

s390x

x86_64

Only bootable images of SLE Micro are available for all architectures. Here is the description of each and every image:

  • Please note these are non-bootable DVD images with all packages from repo
    • SL-Micro.aarch64-6.1-Base-SelfInstall-Beta2.install.iso
    • SL-Micro.aarch64-6.1-Default-SelfInstall-Beta2.install.iso
    • SL-Micro.ppc64le-6.1-Base-4096-SelfInstall-Beta2.install.iso
    • SL-Micro.ppc64le-6.1-Base-512-SelfInstall-Beta2.install.iso
    • SL-Micro.ppc64le-6.1-Default-4096-SelfInstall-Beta2.install.iso
    • SL-Micro.ppc64le-6.1-Default-512-SelfInstall-Beta2.install.iso
    • SL-Micro.x86_64-6.1-Base-RT-SelfInstall-Beta2.install.iso
    • SL-Micro.x86_64-6.1-Base-SelfInstall-Beta2.install.iso
    • SL-Micro.x86_64-6.1-Default-SelfInstall-Beta2.install.iso
    • SL-Micro-Extras-6.1-aarch64-Beta2.iso
    • SL-Micro-Extras-6.1-aarch64-Beta2-Source.iso
    • SL-Micro-Extras-6.1-ppc64le-Beta2.iso
    • SL-Micro-Extras-6.1-ppc64le-Beta2-Source.iso
    • SL-Micro-Extras-6.1-s390x-Beta2.iso
    • SL-Micro-Extras-6.1-s390x-Beta2-Source.iso
    • SL-Micro-Extras-6.1-x86_64-Beta2.iso
    • SL-Micro-Extras-6.1-x86_64-Beta2-Source.iso
    • SL-Micro-Packages-6.1-aarch64-Beta2.iso
    • SL-Micro-Packages-6.1-aarch64-Beta2-Source.iso
    • SL-Micro-Packages-6.1-ppc64le-Beta2.iso
    • SL-Micro-Packages-6.1-ppc64le-Beta2-Source.iso
    • SL-Micro-Packages-6.1-s390x-Beta2.iso
    • SL-Micro-Packages-6.1-s390x-Beta2-Source.iso
    • SL-Micro-Packages-6.1-x86_64-Beta2.iso
    • SL-Micro-Packages-6.1-x86_64-Beta2-Source.iso
  • Default images below are ready-to-deploy raw disk images, including podman as container engine and KVM as virtualization stack for x86_64 machines and RaspBerry Pi. During initial boot, Ignition or Combustion configuration must be provided in order to perform basic configuration (e.g. set root password).
    • SL-Micro.aarch64-6.1-Base-Beta2.raw.xz
    • SL-Micro.aarch64-6.1-Base-qcow-Beta2.qcow2
    • SL-Micro.aarch64-6.1-Default-Beta2.raw.xz
    • SL-Micro.aarch64-6.1-Default-qcow-Beta2.qcow2
    • SL-Micro.ppc64le-6.1-Base-4096-Beta2.raw.xz
    • SL-Micro.ppc64le-6.1-Base-512-Beta2.raw.xz
    • SL-Micro.ppc64le-6.1-Default-4096-Beta2.raw.xz
    • SL-Micro.ppc64le-6.1-Default-512-Beta2.raw.xz
    • SL-Micro.x86_64-6.1-Base-Beta2.raw.xz
    • SL-Micro.x86_64-6.1-Base-encrypted-Beta2.raw.xz
    • SL-Micro.x86_64-6.1-Base-qcow-Beta2.qcow2
    • SL-Micro.x86_64-6.1-Base-RT-Beta2.raw.xz
    • SL-Micro.x86_64-6.1-Base-RT-encrypted-Beta2.raw.xz
    • SL-Micro.x86_64-6.1-Base-VMware-Beta2.vmdk
    • SL-Micro.x86_64-6.1-Default-Beta2.raw.xz
    • SL-Micro.x86_64-6.1-Default-encrypted-Beta2.raw.xz
    • SL-Micro.x86_64-6.1-Default-qcow-Beta2.qcow2
    • SL-Micro.x86_64-6.1-Default-VMware-Beta2.vmdk
  • Default images of SLE Micro, including podman as container engine and KVM as virtualization stack, for various types of hypervisor and storage on IBM system z.
    • SL-Micro.s390x-6.1-Base-dasd-Beta2.raw.xz
    • SL-Micro.s390x-6.1-Base-fba-Beta2.raw.xz
    • SL-Micro.s390x-6.1-Base-qcow-Beta2.qcow2
    • SL-Micro.s390x-6.1-Default-dasd-Beta2.raw.xz
    • SL-Micro.s390x-6.1-Default-fba-Beta2.raw.xz
    • SL-Micro.s390x-6.1-Default-qcow-Beta2.qcow2

 

Documentation

Note: The following Documents are drafts.

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

All documentation are available at https://susedoc.github.io/#modular-micro:

 

Known Issues

Functional

  • bsc#1229146 - openQA test fails in journal_check: basic.target: Job cockpit-ws-user.service/stop deleted to break ordering cycle starting with basic.target/stop
  • bsc#1215377 - plugin /usr/sbin/sedispatch terminated unexpectedly
  • bsc#1215378 - libvirtd[982]: error from service: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running

Kernel

  • bsc#1229138 - P2 - kdump can't be setup on sl micro on s390x architecture - confirmed issue
  • bsc#1229207 - High crashkernel memory requirements for kdump on SL Micro encrypted image
  • bsc#1229025 - SLERT-15SP6: /proc/sys/kernel/printk does not exist

Filesystems

Containers

  • bsc#1215377 - plugin /usr/sbin/sedispatch terminated unexpectedly
  • bsc#1229231 - systemd units ordering cycles
  • bsc#1215378 - libvirtd[982]: error from service: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running

Migration

  • bsc#1229132 - SELinux: pam_wtmpdb module is not allowed to open wtmp database if called by /bin/login
  • bsc#1223259 - sedispatch[1192]: Connection Error (Failed to connect to socket /run/dbus/system_bus_socket: Connection refused): AVC Will be dropped
  • bsc#1215377 - plugin /usr/sbin/sedispatch terminated unexpectedly

Security

  • bsc#1218181 - [SLEM][6.0][Build7.1][x86_64][encrypted] systemd-cryptsetup reports error "Device luks is still in use" at every vm reboot

Virtualization

  • bsc#1229131 - [SLEM][6.1][Build9.15] Some guests fail to install due to "Could not run /usr/bin/swtpm_setup"
  • bsc#1218181 - [SLEM][6.0][Build7.1][x86_64][encrypted] systemd-cryptsetup reports error "Device luks is still in use" at every vm reboot
  • bsc#1210429 - reduce timeout when no ignition/combustion config is provided //For now, we have to wait for almost 10 - 15 mins to boot up ppc64le qemu images successfully due to this bug

Feedback

Whenever you find a bug or have a question while using SUSE Linux Enterprise Micro, we highly recommend that you use our mailing list first, then if it really make sense you should open a bug report.

Private Channel

In case you would like to share some sensitive data with us (data for bug reports, feedbacks, etc), please contact us at beta-programs@suse.com, and we will review your case and provide a private channel with us.

Public Mailing List

micro-beta@lists.suse.com is our dedicated Public 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 community. Only subscribers can post to our mailing lists. To subscribe, please go to http://lists.suse.com/mailman/listinfo/micro-beta. Only subscribers can post to our mailing lists. To subscribe, please go to http://lists.suse.com/mailman/listinfo/micro-beta. Please refer to our Mailing Lists Guideline for more information.  

Frequently Asked Questions

- Beta Subscription and Registration Code
Warning: Beta Registration Code

Registration is not working with your regular SLE Micro 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. 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 Micro Beta Online Channels. We will not provide a beta product subscription or beta product registration code by default for the SLE Micro Beta Program. You might request one via beta-programs@suse.com, please specify if you want a registration code for which architectures.  

- Migrating from SLE Micro 6.0 to SLE Micro 6.1 Beta

Update from SLE Micro 6.0 to 6.1 is now supported. Unlike with SLES, which offers several methods, with SLE Micro there is only one method available, via transactional-update.

- Updating from SLE Micro 6.1 Beta to the next SLE Micro 6.1 Beta

Even if it's completely feasible and working, we do not recommend updating from "SLE Micro 6.1 Beta X" to "SLE Micro 6.1 Beta X+N" for your thorough beta testing. Why? Because this scenario is specific to beta and can not be compared to any SLE Micro 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 Micro Beta might look very different from regular updates we make in official SLE Micro releases. We highly recommend to test the following scenarios, whenever a new Beta version is released:  

- Updating from SLE Micro 6.1 Beta to SLE Micro 6.1 GM
Warning: Migration from Beta to Gold Master

Migrating from SLE Micro 6.1 Beta to SLE Micro 6.1 Gold Master (the final and official version) is NOT SUPPORTED. If you want to put the final version of our product in production, you need to do a fresh installation or a migration from an existing supported version. We will not support the migration from a beta product to a final release of the product. As a reminder, our SUSE Beta EULA states that you should not put SUSE Beta Products in production.    

- Contact Beta Manager

Do you have a question or an issue to report on our Beta Program? Want to get in touch with our Product Managers or Engineering team? Or simply share a feedback? Please do not hesitate to contact us via beta-programs@suse.com!