enable default_boot_always_attempt for non-TL VMs (#2436) #2459
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR backports a temporary workaround that enables the default_boot_always_attempt flag for non-Trusted Launch isolated VMs. This is necessary to allow VMs to boot successfully after OS disk swaps in Azure when the VMGS is not swapped along with the OS disk.
Key changes:
- Adds conditional logic to enable
default_boot_always_attemptfor isolated VMs that don't have secure boot or TPM enabled - Includes clear documentation explaining the temporary nature and rationale for the workaround
Member
|
Do we need a 2411 version of this patch? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Always enable default boot always attempt for non-Trusted Launch VMs. This is roughly equivalent to not having secure boot or TPM enabled. This is necessary because the VMGS is not swapped with the OS disk for these VMs in Azure (and in any case on-prem), causing the VM to fail to boot after an OS swap.
Backport of #2436