image: fix deadlock on boot by using AWS linux kernel #2115
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.
Context
Constellation nodes on AWS SEV-SNP frequently get stuck during boot.
They are usually automatically cleaned up and replaced by AWS after a period of 5-10 minutes.
After a lot of testing, our Kernel was deemed to be the problem.
Proposed change(s)
Related issue
Additional info
This does not seem to fix all problems related to booting SEV-SNP VMs, but it seems to make things a lot more stable.
We'll need a build process for the Kernel.
The standard AWS Linux Kernel (currently
6.1.34-59.116
) does not support dm-verity and has dependencies on packages which aren't actually required.We have a prebuilt Kernel with the required modules, but in the future we should automate the process of building this Kernel.
Checklist