search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.37k stars 817 forks source link

WSL2 failed to run, no response from virtual machine or container #7351

Closed wangfys closed 3 years ago

wangfys commented 3 years ago

Windows Build Number

Microsoft Windows [Version 10.0.19043.1151]

WSL Version

Kernel Version

5.10.16

Distro Version

No response

Other Software

__

Repro Steps

Just run 'wsl' command in PowerShell or create a new tab of Ubuntu in PowerShell.

Expected Behavior

The WSL2 should run normally.

Actual Behavior

It says "没有收到虚拟机或容器的回应，操作超时 [已退出进程，代码为4294967295]". The translation of the Chinese should be 'No response from virtual machine or container, operation timed out [Process exited, the code is 4294967295]'

Diagnostic Logs

Currently, I'm using a Surface Pro X running Windows 10 on ARM and the PowerShell version is PowerShell 7.2.0-preview.9

This issue doesn't appear on another computer running normal Windows 10.

I have searched whether there are similar issues. There are three related issues but their solutions are all workarounds. The real problem hasn't been found.

7012 shows exactly the same behavior, but the solution he/she found is that install Ubuntu-18.04 in the MS store and then his 20.04 works fine.

7332 shows a similar behavior, the solution he/she found is to uninstall Windows Update KB5005033. I tried but failed.

7339 shows a similar behavior, the solution he/she found is to export the distro, unregister it and then import it again.

Basically, I guess that there is something wrong with a Windows Update. It results in that the system can't find the original WSL distro correctly. Install another distro or export+unregister+import accidentally fixes this problem.

wangfys commented 3 years ago

I tried to install Ubuntu-18.04 in the MS store. It successfully runs but my original Ubuntu is still in trouble.

So the newly installed Ubuntu-18.04 is WSL1 so it works fine. When I tried to convert it into WSL2, it says 'No response from virtual machine or container, operation timed out' again. And my Ubuntu in WSL2 failed to run

image

licanhua commented 3 years ago

"The operation timed out because a response was not received from the virtual machine or container." The actual error is: HCS_E_CONNECTION_TIMEOUT 0x80370109

CoskunSunali commented 3 years ago

I am receiving the same error on Windows 11 Pro 22000.168 (kernel version 5.10.43)

P.S. It occasionally works, mostly doesn't.

Coskun@CS MINGW64 ~
$ ubuntu
The operation timed out because a response was not received from the virtual machine or container.
Segmentation fault
OneBlue commented 3 years ago

/logs

ghost commented 3 years ago

Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it.

Thank you!

wangfys commented 3 years ago

I have used Feedback Hub to upload the logs. Here is the link: https://aka.ms/AAdr1sz

florentchauveau commented 3 years ago

I have the same issue with Windows 11 Insider build 10.0.22454.1000.

Surface Pro X (SQ2)

The operation timed out because a response was not received from the virtual machine or container.

maxboone commented 3 years ago

I have the same issue with Windows 11 Insider build 10.0.22454.1000.

Surface Pro X (SQ2)

The operation timed out because a response was not received from the virtual machine or container.

Same issue, steps that didn't help:

I think I'm just going to do a re-install tbh, it seems like something is really up with the network interface between the Hyper-V guest services & wsl client side.

That said, I don't have the vmsmp service (even after above steps) which I saw in another issue - could that be related - as I don't have vEthernet switches either in my Device Manager (hidden devices & set devmgr_show_nonpresent_devices=1 turned on)

As this kinda feels like a networking issue I thought this to be relevant possibly.

benhillis commented 3 years ago

/dupe #5194

ghost commented 3 years ago

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

readloud commented 1 year ago

wsl --shutdown

Arias1101 commented 1 year ago

wsl --shutdown works for me, thanks !

readloud commented 1 year ago

👌

khadeshyam commented 1 year ago

wsl: Failed to launch the localhost relay process. Error: The operation timed out because a response was not received from the virtual machine or container. The operation timed out because a response was not received from the virtual machine or container.

Error code: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT

[process exited with code 4294967295 (0xffffffff)] You can now close this terminal with Ctrl+D, or press Enter to restart.

khadeshyam commented 1 year ago

Screenshot (105) I am getting this error can someone help

dhruvmsheth commented 4 months ago

finally fixed it. nothing in the comments above helped me. I navigated to the .wslconfig files placed in /Users/<username>/ and opened .wslconfig file with a text editor and removed a line which redirected the kernel to a non-existent directory. Make sure the config file only says [wsl2]