catastrophic failure after enabling systemd in wsl.conf

[Sadra-jl]

Version

Windows version: 10.0.25211.1010

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.15.68.1

Distro Version

No response

Other Software

No response

Repro Steps

installed pengwin from the windows store. enabled [boot] systemd=true in /etc/wsl.conf, shutdown wsl, and rerun wsl, after a few moments, I got the: "catastrophic failure Error code: Wsl/Service/CreateInstance/0x8000ffff "

note: systemd is working fine in arch Linux inside wsl with the same steps above.

Expected Behavior

expected to see the distro start successfully and work with systemd.

Actual Behavior

gets the error "catastrophic failure"
with Error code:" Wsl/Service/CreateInstance/0x8000ffff "

Diagnostic Logs

No response

[OneBlue]

/logs

[ghost]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

[bangbang93]

Same problem for me.
WslLogs-2022-10-13_23-30-15.zip

[Sadra-jl]

so sorry for the delay, I live in Iran, and, well government cut off our internet as they pleased.
anyway here is the log.
WslLogs-2022-10-13_19-56-20.zip

[OneBlue]

Thank you @Sadra-jl. Unfortunately I'm not seeing any WSL log entries in the file you shared. Did you reproduce the issue while the log collection was running ?

[josesa-xx]

I've used Windows 11 with Microsoft Store WSL preview (0.70.4.0) and tried to enable cgroupv2 by doing

WIN_WSLCONFIG=$(wslpath $(wslvar USERPROFILE))/.wslconfig
git config -f ${WIN_WSLCONFIG} wsl2.kernelCommandLine "cgroup_no_v1=all"
wsl.exe --shutdown

Problem shows when starting up.
WslLogs-2022-11-02_21-01-42.zip

systemd was already enabled and working.

[OneBlue]

Thank you @josesa-xx. Now I can see what's happening.

During boot, WSL tries to mount /sys/fs/cgroup/memory, but with cgroup_no_v1=all , this fail:

698	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	11-02-2022 21:01:51.746	7920	"text: 	""[    2.493568] WSL (1) ERROR: Mount:1761: mount((null), /sys/fs/cgroup/memory, cgroup, 0x20000e ""
vmId: 	{4a81dc2a-f949-4fa4-b16c-abad63c1acbd}"	"	"				3384	5		00000000-0000-0000-0000-000000000000			

Which is why WSL fails to start

[YiuTerran]

Same problem here. Any idea to restore settings?

[josesa-xx]

If you have the same problem as me it should be simple to edit the file in %USERPROFILE%\.wslconfig and remove the line about kernelCommandLine

[ilan-schemoul]

1.0.1.0 fixed the issue in my case (my exact case was putting kernelCommandLine=cgroup_no_v1=all with systemd enabled, see #6662 (comment))

[OneBlue]

Indeed this was fixed with 1.0.1. Closing