You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting this @xudyang1. The startup times with systemd depends on what units are enabled during boot, but the delay you're seeing doesn't sound extravagant to me. The best way to make wsl starts with systemd faster would be to looking at the units you're running via systemctl -t service and disable the ones you don't need
Windows Version
Microsoft Windows [Version 10.0.19045.2965]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
Linux version 5.15.90.1-microsoft-standard-WSL2
Distro Version
Ubuntu-20.04
Other Software
No response
Repro Steps
/etc/wsl.conf
file in default distro (Ubuntu 20.04) to enablesystemd
:wsl --shutdown
Expected Behavior
WSL2 startup time should be less than 4 seconds.
Actual Behavior
#9377 mentions disabling swap, but the startup time was still around 6~7 seconds with the following configuration:
#2941 says something related to systemd, so I ran
systemctl
, then noticedsystemd-remount-fs.service
andmultipathd.socket
were marked as red.From the
dmesg
reports, I also noticed the diffs at the very bottom, which took about 2 seconds:Some other fields marked red in both reports were:
PCI: Fatal: No config space access function found
kvm: no hardware support
FS-Cache: Duplicate cookie detected
Failed to connect to bus: No such file or directory
misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
They seemed to be harmless, so I assume they were not the causes.
Diagnostic Logs
systemd
:systemd
enabled:The text was updated successfully, but these errors were encountered: