-
Notifications
You must be signed in to change notification settings - Fork 823
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
WSL slow startup: PCI VMBus probing: Using version 0x10003 #11009
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please 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. Thank you! Open similar issues:
Closed similar issues:
|
/logs |
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download 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 If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue. Thank you! |
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it. Thank you! |
All,
After following the technique from @sryio in issue #5548
I get a new error that is still taking a long time. Here is a subset of the
dmesg
output right after startup.Zooming in you can see that the major chunk of time for startup was here,
Googling around for
wsl PCI VMBus probing
did not shed much light... the closest where:but don't appear to be this issue...
Thoughts?
System Description:
WSL version: 2.0.9.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.3930
Device name astrocyte
Processor 13th Gen Intel(R) Core(TM) i9-13900H 2.60 GHz
Installed RAM 64.0 GB (63.7 GB usable)
Device ID 93CDF4AC-164A-42B5-B0B8-019666C58CEC
Product ID 00329-00000-00003-AA350
System type 64-bit operating system, x64-based processor
Pen and touch Touch support with 10 touch points
Edition Windows 10 Enterprise
Version 22H2
Installed on 12/6/2023
OS build 19045.3930
Experience Windows Feature Experience Pack 1000.19053.1000.0
Name NVIDIA GeForce RTX 4080 Laptop GPU
PNP Device ID PCI\VEN_10DE&DEV_27A0&SUBSYS_0BDB1028&REV_A1\4&32DCE9B4&0&0008
Adapter Type NVIDIA GeForce RTX 4080 Laptop GPU, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 4080 Laptop GPU
Adapter RAM (1,048,576) bytes
Installed Drivers C:\windows\System32\DriverStore\FileRepository\nvdmsig.inf_amd64_58416624598bf658\nvldumdx.dll,C:\windows\System32\DriverStore\FileRepository\nvdmsig.inf_amd64_58416624598bf658\nvldumdx.dll,C:\windows\System32\DriverStore\FileRepository\nvdmsig.inf_amd64_58416624598bf658\nvldumdx.dll,C:\windows\System32\DriverStore\FileRepository\nvdmsig.inf_amd64_58416624598bf658\nvldumdx.dll
Driver Version 31.0.15.4633
The text was updated successfully, but these errors were encountered: