feat: Update kernel matrix with Cloud Hypervisor #55
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.
This is fairly simple to do now that the modules are mounted in separately.
Here I have restructured the
kernel
directory to build both firecracker and cloud-hypervisor images. Whichever you are using, the CAPMVM root image will be the same as there is no connection anymore.The readme has been updated to describe the sequence and how images relate to each other.
Tested against the CH pr in flintlock with this hammertime spec: