![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 25%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
Hey Nick,
I know it looks like it should work—the kernel string is even in the newest support-matrix row—but, unfortunately, openSUSE Leap 15.6 isn’t on the “officially supported” list for the ASR Mobility Service. The package you grabbed (Microsoft-ASR_UA_9.65…_SLES15-64…tar.gz) is built and driver-signed for SUSE Linux Enterprise Server 15 SP6, not for the community Leap build. During install the script:
- Reads
/etc/os-release, seesID="opensuse-leap"andVERSION_ID="15.6"→ resolves “SP0”.
Tries to load the filter driver (involflt.ko) that’s signed with the SLES key.
The kernel refuses to load it, so the installer bails out with exit code 208 (“filter driver can’t start”)—exactly what you’re seeing. ([azvise.com](https://azvise.com/2020/12/18/azure-asr-kernel-modules-fail-to-load-while-installing-the-mobility-service-vmware/?utm_source=chatgpt.com"ASR Kernel modules fail to load while installing the Mobility Service ..."))
What Microsoft supports today
| Distro | Status in support matrix | Mobility-agent build | Notes |
|---|---|---|---|
| SLES 12 SP1-SP5 | ✅ | 9.64+ | |
| SLES 12 SP1-SP5 | ✅ | 9.64+ | |
| SLES 15 SP1-SP6 | ✅ (6.4.0-150600.* kernels listed) | 9.64+ | |
| openSUSE Leap 15.x | ❌ Not listed | — | No driver signing key; not tested |
Microsoft confirmed the same last year when someone asked about SP6: only the Enterprise edition counts for support; community builds aren’t planned yet. ([learn.microsoft.com](https://learn.microsoft.com/en-us/answers/questions/1820216/linux-suse-15-sp6-compatibility-with-asr-mobility"Linux SuSE 15 SP6 compatibility with ASR mobility agent - Microsoft Q&A"))
Your options
- Switch the VM to SLES 15 SP6 (or an earlier SP that you’re licensed for). With the same 6.4.x kernel the agent installs cleanly.
Stay on openSUSE and wait – you’d need to track the ASR release notes and hope Leap gets added (there’s no ETA, and tickets filed with support usually come back with “unsupported”).
Hacky workaround (not supported, do at your own risk)
Install the matching kernel-default-devel package plus make, gcc, etc.
Temporarily edit `/etc/os-release` so the installer thinks it’s `SLES_SAP` with `SP=6`.
Re-run `./install` and manually sign the resulting `involflt.ko` with your own key + `mokutil`.
Revert `/etc/os-release`. This gets past 208 for some people, but you’re on your own if something breaks later.
Bottom line
Right now the safest path is to replicate a SLES guest, not openSUSE. If Leap support is a must-have, raise a support request so the product group can track the demand, but plan on SLES for production DR.
Hope that clears up the mystery—and saves you a few more re-installs! Let me know if you need the SLES media links or the exact zypper commands to pull the kernel-devel headers.
Best Regards,
Jerald Felix