Skip to content

Specify HyperVGeneration = 'v1' #189

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

Merged
merged 1 commit into from
Apr 23, 2025
Merged

Conversation

mbiver
Copy link
Contributor

@mbiver mbiver commented Mar 25, 2025

If you do not specify HyperVGeneration = 'v1' in the $GalleryParams, you'll receive the error message Validation failed: Error with Hyper-V Version validation (cross-generation for multiple Hyper-V Versions is not supported). The provided SIG:
| /subscriptions/REDACTED/resourceGroups/myWinImgBuilderRG/providers/Microsoft.Compute/galleries/myImageGallery/images/winSvrImages, has a different Hyper-V Generation: V2,
| than source image: V1.

If you do not specify HyperVGeneration = 'v1' in the $GalleryParams, you'll receive the error message  
Validation failed: Error with Hyper-V Version validation (cross-generation for multiple Hyper-V Versions is not supported). The provided SIG:
     | /subscriptions/REDACTED/resourceGroups/myWinImgBuilderRG/providers/Microsoft.Compute/galleries/myImageGallery/images/winSvrImages, has a different Hyper-V Generation: V2,
     | than source image: V1.
Copy link
Contributor

@mbiver : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 9e62b20:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/windows/image-builder-powershell.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Mar 25, 2025

@kof-f

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Mar 25, 2025
Copy link

github-actions bot commented Apr 8, 2025

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Apr 8, 2025
Copy link
Contributor

@mbiver : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-dirichards
Copy link
Contributor

@kof-f - Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge? Thanks.

@github-actions github-actions bot removed the inactive This PR is inactive for more than 14 days label Apr 9, 2025
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Apr 23, 2025
@v-dirichards
Copy link
Contributor

@kof-f

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@kof-f
Copy link
Contributor

kof-f commented Apr 23, 2025

#sign-off

@v-dirichards v-dirichards merged commit 77211f6 into MicrosoftDocs:main Apr 23, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants