Conversation
* implement scoutd vsock bootsrap and fatal panic reporting * make scoutd panic reporting allocator free
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR promotes the latest scoutd guest communication work from
devtomain.It brings the initial vsock transport foundation onto
main, including separate control and log channels, the first framed control messages, early boot control channel setup, and fatal panic reporting over vsock before guest power off.This keeps
mainaligned with the current scoutd boot pipeline and establishes the long term host guest communication path before networking, MMDS, and workload launch are added.