Skip to content

Conversation

@benhillis
Copy link
Member

This resolves an issue where a new root VHD stopped PMEM boot from working. This is because in the HCS stack there is a default max size that is applied when pmemController.MaximumCount != 0 and this max size was not large enough for the new VHD.

@benhillis benhillis requested a review from a team as a code owner January 7, 2026 23:21
Copilot AI review requested due to automatic review settings January 7, 2026 23:21
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a boot failure when using PMEM VHDs by preventing the HCS stack from applying a restrictive default max size. The issue occurred because setting pmemController.MaximumCount to a non-zero value triggered HCS to apply a default size limit that was too small for the new root VHD.

Key changes:

  • Refactored PMEM controller initialization to use a separate nextDeviceId variable instead of MaximumCount for device ID tracking
  • Re-enabled the previously skipped PmemVhds test that validates PMEM boot functionality

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/windows/wslaservice/exe/WSLAVirtualMachine.cpp Refactored PMEM controller to avoid setting MaximumCount, preventing HCS from applying default size limits
test/windows/WSLATests.cpp Re-enabled PmemVhds test now that the underlying boot issue is resolved

@benhillis benhillis enabled auto-merge (squash) January 8, 2026 19:07
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

Successfully merging this pull request may close these issues.

2 participants