-
Notifications
You must be signed in to change notification settings - Fork 867
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
VmmemCmFirstBoot freezes Framework Laptop #12541
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 script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here 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:
|
WslLogs-2025-02-03_08-27-26.zip The script asked me to reproduce the issue, which I cannot do because I would have to enable WSL, which freezes my machine. |
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running. Diagnostic information
|
The bot is able to extract and parse zip files but not read my comment. I‘m unable to reproduce the issue because I would need to enable VMX in EFI which would start the process VmmemCmFirstBoot after logging in. This freezes my machine INCLUDING the trace script. If you tell me how to disable that process I can generate a trace. |
After switching to the prerelease, the problem is not occuring anymore (for now):
|
I'm not sure what vmmmemCmFirstBoot is, but it's unrelated to WSL. I would suggest filing an issue via Feedback Hub so this can get routed to the right team, feedback hub will also collect the relevant tracing information. |
@Isotop7 I reported it to Microsoft on Feedback Hub. |
Windows Version
24H2 (26100.2894)
WSL Version
2.3.26.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Debian Bookworm
Other Software
No response
Repro Steps
Expected Behavior
After logging in, I would like to use Windows and also the WSL.
Actual Behavior
After logging in, several VmMem processes are forked, which consume a high cpu load. The process VmmemCmFirstBoot ultimately freezes the PC. No mouse or keyboard input are possible and I have to force reboot the system by holding down the power key.
When disabling WSL or Virtualization settings in the BIOS, the system starts without any problems.
Diagnostic Logs
The text was updated successfully, but these errors were encountered: