-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hibernate breaks WSL Hyper-V Adapter #11388
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
Here are the logs: I have podman desktop installed but this issue occurs on any WSL2 distro and occurred before I installed podman desktop. The reason I created this report even though #4992 exists is because none of the work arounds that aren't restarting my computer work to resolve the issue. |
Diagnostic information
|
Hi. Can you please collect networking logs by following the instructions below? |
I am uploading via the email. I needed to exclude the trace files to be able to send it. Let me know if you need those and how I could upload them more securely. |
Windows Version
10.0.19045.4170
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-2
Distro Version
No response
Other Software
No response
Repro Steps
From a clean wsl2 install following these steps:
Clean WSL2 install
Uninstall wsl and related stuff 1. In powershell (as admin) #list all installed distroswsl -l -v #destroy distroswsl --unregister Ubuntu wsl --unregister Debian #and so onRe-install and configure wsl to use systemD
1. Installing wsl - In powershell (as admin)
#install wsl
wsl --install
Open Turn Windows Features on or off
Tick Hyper-V, Containers, Windows Hypervisor Platform
Then reboot and wait for the Ubuntu installation to complete and ask for username (it might takes some time).
Assumptions:
System is behind a corporate proxy and a vpn.
Run WSL2 configure it with your ca-cert, proxy env variables, disable generateResolvConf in wsl.conf, unlink /etc/resolv.conf and create a new resolv.conf with proper dns server for your network.
Run curl https://example.com and you should get back a proper response.
Hibernate your machine (sleep also works) and then wake it up, try to run the curl command again and notice that https://example.com will fail to resolve. (this also happens if you close your wsl2 session and hibernate then reenter your session).
Resolve the issue by restarting your machine (resetting WSL2 via shutdown and restarting the services does not resolve the issue).
Expected Behavior
Upon waking computer WSL2 networking works as it did before hibernation/sleep.
Actual Behavior
WSL2 networking breaks after waking from hibernation/sleep. WSL Hyper-V network adapter breaks.
Diagnostic Logs
Event viewer has this error when trying to recreate the WSL hyper-v network adapter after hibernation:
The text was updated successfully, but these errors were encountered: