Skip to content

Conversation

praveen-pk
Copy link
Contributor

To configure custom VM features during VM creation, the create and initialize steps have been broken up in mshv-ioctls, starting with:

1afa433 mshv-ioctls: Don't initialize partition after creation

So, any uses of v0.5.0 and newer versions of mshv-ioctls should explicitly initialize the vm after creation.

To configure custom VM features during VM creation, the create and
initialize steps have been broken up in mshv-ioctls, starting with:

1afa433 mshv-ioctls: Don't initialize partition after creation

So, any uses of v0.5.0 and newer versions of mshv-ioctls should explicitly
initialize the vm after creation.

Signed-off-by: Praveen K Paladugu <[email protected]>
@praveen-pk praveen-pk requested a review from a team as a code owner October 1, 2025 21:41
@Copilot Copilot AI review requested due to automatic review settings October 1, 2025 21:41
Copy link
Contributor

@Copilot 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

Explicitly add a VM initialization step after creation to comply with the updated mshv-ioctls API (>= v0.5.0), which now separates creation and initialization.

  • Adds an explicit vmfd.initialize() call after VM creation.
  • Maps any initialization failure to an existing CreateVMFailed error variant.

Copy link

github-actions bot commented Oct 1, 2025

smalis-msft
smalis-msft previously approved these changes Oct 3, 2025
Co-authored-by: Copilot <[email protected]>
Signed-off-by: Praveen K Paladugu <[email protected]>
@praveen-pk praveen-pk merged commit e3a5fcf into microsoft:main Oct 6, 2025
29 checks passed
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