Skip to content
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

Closed
1 of 2 tasks
Isotop7 opened this issue Feb 3, 2025 · 7 comments
Closed
1 of 2 tasks

VmmemCmFirstBoot freezes Framework Laptop #12541

Isotop7 opened this issue Feb 3, 2025 · 7 comments

Comments

@Isotop7
Copy link

Isotop7 commented Feb 3, 2025

Windows Version

24H2 (26100.2894)

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Debian Bookworm

Other Software

No response

Repro Steps

  • Upgrade to the latest Windows 11 release and wsl version
  • Install any distro
  • Reboot and login and wait for the deadlock

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.

Image

Diagnostic Logs

Image

Copy link

github-actions bot commented Feb 3, 2025

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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
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 and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@Isotop7
Copy link
Author

Isotop7 commented Feb 3, 2025

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.

Copy link

github-actions bot commented Feb 3, 2025

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
.wslconfig found
Detected appx version: 2.3.26.0
Found no WSL traces in the logs

@Isotop7
Copy link
Author

Isotop7 commented Feb 3, 2025

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.

@Isotop7
Copy link
Author

Isotop7 commented Feb 3, 2025

After switching to the prerelease, the problem is not occuring anymore (for now):

WSL-Version: 2.4.10.0
Kernelversion: 5.15.167.4-1
WSLg-Version: 1.0.65
MSRDC-Version: 1.2.5716
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.26100.1-240331-1435.ge-release
Windows-Version: 10.0.26100.2894

@benhillis
Copy link
Member

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.

@gadcam
Copy link

gadcam commented Mar 9, 2025

@Isotop7 I reported it to Microsoft on Feedback Hub.
If you want it to be fixed quickly you can upvote/share details there
https://aka.ms/AAuy732
Anyone having the same issue can do it, this way we will get it fixed quickly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants