-
Notifications
You must be signed in to change notification settings - Fork 814
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
Cannot use GPU support in Windows 10 preview build 21354 #6773
Comments
Installed 21354 yesterday. Any idea when the next version, with the gpu fix, will drop? |
This fix should be available the next Windows Insiders preview build. |
@craigloewen-msft I appreciate you guys are working hard and I shouldn't expect rock-hard stability in this line of Windows development but it being the only way of using CUDA under WSL in any meaningful way, is there a chance that a team member does a
before a release to ensure that works? Assuming it is an oversight and not some fundamental incompatibility every time. This is the third time this has happened in the past few months, and judging by the amount of people who comment on and star these issues I know I am not alone. It doesn't help that my computer restarts itself overnight leaving me with a non-functioning system (I know I can turn that off). Anyway, thanks for all the work you do and I look forward to the fix for this. |
+1 Actually, would be nice to have some way to not living on the bleeding edge to get WSL or Cuda on Windows. Would consider paying for our use case :) |
Indeed, is there any information wrt. when it will no longer require insider build for CUDA in WSL? |
Exactly one of my questions. My other question is: when will the next version, with the gpu fix, drop? I figure that with requiring Insider for WSL CUDA, MS "acquires developer buy-in." So to speak. My last Linux box died a while ago - I should really get around to replacing it. Had high hopes for WSL[2]. |
Two days i spent trying to get it working because i specifically moved to the dev channel for this feature. I'd pay for windows 10 pro for workstation to get this feature. Why don't you enable DDA in windows 10 pro for workstation while this gets ironed out. |
Besides the GPU issue, I found that I suddenly cannot ssh into WSL2 from Windows using my usual
Simply restart the sshd service won't fix it. Somehow I have to change the port number in my |
Agreed! We actually do run GPU tests in WSL that are part of our regular process to ensure that we are not breaking anything GPU related when we make any changes to WSL. These last breakages have exposed some gaps in our testing and we are working on fixing them as we definitely don't want to break you either :) . Additionally, GPU compute will be part of the next major Windows release. |
@craigloewen-msft Cuda in WLS2 5.4.72 with WIP 21354.1 worked normally, while abnormally in WLS2 5.4.91 updated at today. I had attempted to turn off and then turn on WLS2, or |
Hi,@craigloewen-msft |
https://archive.org/details/Windows-10-Build-21286 < I'm desperate so reinstalling the last build. |
Does this mean it is not fixed? |
|
This issue has been fixed in the latest preview build 21359, please upgrade your systems and you'll have vGPU access again! I am working on getting the changelog there updated to reflect that vGPU is fixed. Thank you all for your patience! |
I think it can be somehow related to this:
Is it possible that this version mismatch causes my error? |
Actually, I have a separate issue:
|
Actually, I have this issue too |
I'm really fresh here, but I think this:
is strange |
Turns out here is a way to bypass the version check: NVIDIA/nvidia-container-toolkit#148
|
Hi, Thanks, It's great and timely. |
Oh Man, I brought a second hand PC yesterday just to run the old build and get ML going again. All I had to do was wait 24hrs. Thanks for getting it going again though. It will be faster on my main machine and it shows that there is commitment to the cause. |
Agreed! Great to have it working again, thanks everyone! |
It worked for me too. However, now getting the error: "only 0 Devices available, 1 requested. Exiting." Any idea how this can be resolved? $ sudo docker run --gpus all --env NVIDIA_DISABLE_REQUIRE=1 nvcr.io/nvidia/k8s/cuda-sample:nbody nbody -gpu -benchmark NOTE: The CUDA Samples are not meant for performance measurements. Results may vary when GPU Boost is enabled. Error: only 0 Devices available, 1 requested. Exiting. |
The issue still persists for me. nvidia-smi.exe works just fine, but the linux command returns
|
Same here -- but cuda is running without any issues. This might just be an issue with nvidia-smi at this point. |
Could be an NVML thing. |
Upgraded to 21359 - both nvidia-smi and deviceQuery failed with the same errors as before. What Nvidia driver version do I have? 465.89. Check to see if that's the latest (https://www.nvidia.com/Download/index.aspx?lang=en-us). No, there's a 466.11 Install that. Didn't help. Same errors again for nvidia-smi and deviceQuery.
For good measure reboot. Didn't help. As a practical concern, it looks to me like CUDA programming inside WSL2 is a lost cause. I don't have a lot of cycles for WSL. I'm spending too much time testing out MS's latest code (and writing messages like this). Mostly my concern now is how to uninstall Windows Insider Program - except when I looked at that before it didn't seem all that obvious. You can't back up. It seemed the message was: wait until Insider and release versions are synced up then exit. Or something to that effect. |
Oh right - this is now a closed topic. That;'s great. Closed so far as MS is concerned that is. |
Yeah, i think that's the case. Sometimes nvidia-smi requires a bit of a work around. It was fixed with 465.42, but 470.14 probably still needs it |
Yes, Microsoft has no interest in your NVIDIA problems which are completely unrelated to the original issue under which you are commenting. The issue is closed because it was corrected in the latest build. |
Thanks Anton - that's very useful. |
I've closed this issue out as the original issue breaking GPU support that this issue is tracking is now fixed. If you're still experiencing GPU related problems please open another issue. From the discussion above it seems like this is NVIDIA related, we're also taking a look internally at what could be causing this issue but do not have repros on the few machines we have tried it on. As a kind reminder, this repository abides by the Microsoft Code of Conduct and we encourage users to be polite and respectful to others on this forum. Thanks all! |
Seems like this change is not migrated to 21364 build. So please be on 21359 build only. |
this bug is not fixed on Windows 21376co_release.210503-1432 |
I actuallu have version 21354, how can I update to version 21359? |
Hello to everyone. Premising that I’m using “Microsoft Windows 11 [Version 10.0.22000.1219]”,I have installed Ubuntu 22.04 on top of it and then I’ve upgraded Ubuntu 22.04 to 22.10 and I’ve upgraded the driver for my RTX 2080 ti on the host os. After this,I have installed CUDA inside the WSL2 / Ubuntu following this mini tutorial : Get the latest feature updates to NVIDIA's proprietary compute stack. These are the commands that I have issued :
at this point I did :
because without installing this package,it won’t find the utility nvidia-smi. But this is the error that I’ve got next :
what should I do now ? The driver installed on the host os is version : 31.0.15.2686 |
Notes from the dev team
Hey everyone we're filing this issue on ourselves to track the fact that GPU Compute support is unavailable in preview build 21354. We have identified the fix for this already and it should likely be out in the next Insiders build. Thanks for your patience here (again 😅) as we resolve this issue!
Environment
Steps to reproduce
Trying to use any Linux application that leverages the GPU on Windows will not work.
Expected behavior
I should be able to use Linux applications that leverage the GPU.
Actual behavior
Any access to the vGPU in WSL will fail.
The text was updated successfully, but these errors were encountered: