Furthermore, additional issues with speed, specifically I/O, were also problematic. This was mostly due to restrictions placed on some system calls, most importantly those revolving around networking. Sudo cat /proc/sys/fs/binfmt_misc/WSLInteropĮverything should work fine also with systemd again.Kali Linux has had support for WSL for some time, but its usefulness has been somewhat limited. rw-r-r- 1 root root 0 Mar 24 11:35 status rw-r-r- 1 root root 0 Mar 24 11:35 WSLInterop If you see sudo ls -Fal /proc/sys/fs/binfmt_miscĭr-xr-xr-x 1 root root 0 Mar 24 11:11. If you get an error on restarting, you might need to install binformat support first: sudo apt update Restart systemd services sudo systemctl restart systemd-binfmt restart binformat related systemd services With contents: :WSLInterop:M::MZ::/init:PFĢ.
In wsl create the file sudo vi /usr/lib/binfmt.d/nf I did some more digging and following binformat config fixed it for me: If that works when you run it manually but fails when you run that kex command, then there may be something else going in with kex that breaks on your system. It should dump a list of running processes with a few details for each. Maybe try running tasklist manually? First by running tasklist.exe, then with /mnt/c/Windows/system32/tasklist.exe. You could check for that by looking for a line that starts with kernel= in a file placed under %USERPROFILE%.wslconfig (maybe with cat $(wslpath $(wslvar USERPROFILE))/.wslconfig, if you happen to have wslpath and wslvar installed in your WSL distro), but in truth the output of uname -a on my system is essentially identical to yours, so that's unlikely to be the issue. Another way binary interoperability might be disabled is if you configured WSL to use a custom kernel that was built without it. Looking at this, try running cat /proc/sys/fs/binfmt_misc/WSLInterop. It might mean that you (or something you ran) decided to reconfigure your WSL setup to disable the ability to run win32 executables from within a WSL distro. That cannot execute binary file error is peculiar. For example, wsl.exe -v will show you various the version numbers of various relevant bits. Run wsl.exe to actually run the windows tool to manage WSL. You have a tool installed on your linux distro called " wsl", so when you run wsl in a linux shell, that's what runs.
0 kommentar(er)
