Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

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

from wsl.

/emailed-logs

from wsl.

Found '/emailed-logs', adding tag 'emailed-logs'

from wsl.

Thank you @Canic.

I'm not seeing anything abnormal in the logs. can you try to:

• Start WSL
• In another shell, run wsl --debug-shell as administrator
• Take a screenshot of top in that shell

And share the output here ? I'd be interested to see which process consumes the CPU.

from wsl.

I did it now, but top doesn't shows anything with high cpu usage:

Any other ideas what i could do that we found out whats going on?

from wsl.

Interesting. It looks like the CPU is being consumed by wslservice.exe, and not the actual VM. Let's try something: does removing:

networkingMode=mirrored

And then running wsl --shutdown solve the issue ?

from wsl.

Hey @OneBlue ,

Your suggestion regarding networkingMode has been quite helpful and is assisting me in identifying the problem.

The issue lies in using a Yubikey as an SSH GPG Key. To transfer the key from my Windows machine to the WSL2 distro, I am using a transfer Pageant.

When I save this file (wsl2-ssh-pageant.exe) directly on the distro (for instance, ~/.ssh/wsl2-ssh-pageant.exe) and initiate it from .bashrc, the problem arises after connecting to an SSH server with ForwardAgent yes enabled.

However, when I save wsl2-ssh-pageant.exe directly on the Windows machine (for example, "/mnt/d/wsl2-ssh-pageant.exe"), the problem disappears.

from wsl.