This message was deleted.

Hello there. What version of the operator are you using? The SL Micro 6.0 based channels are compatible with operator >= v.1.6.x For example I tried to apply the following and it works on my side:

apiVersion: <http://elemental.cattle.io/v1beta1|elemental.cattle.io/v1beta1>
kind: ManagedOSVersionChannel
metadata:
  name: elemental-channel
  namespace: fleet-default
spec:
  options:
    image: <http://registry.suse.com/rancher/elemental-channel/sl-micro:6.0-base|registry.suse.com/rancher/elemental-channel/sl-micro:6.0-base>
  type: custom

You can try to dig further by inspecting the logs of the channel syncer pod. This is a pod in the

fleet-default

namespace with the same name of the ManagedOSVersionChannel. This pod is responsible to unpack the channel image and generate the respective

ManagedOSVersions

I'm using the 2.0 plugin and elemental-operator:1.6.4

Hi there, this is known issue with SL Micro 6.0 images: https://elemental.docs.rancher.com/release-notes#kernel-panic-on-hypervisors You can set the CPU type to be

x86-64-v2

at very least, or use CPU host passthrough for better compatibility

That fixed it, Thanks!