implement scoutd vsock bootsrap and fatal panic reporting#16
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
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 adds the first real vsock transport foundation for scoutd. The guest now establishes separate control and log channels to the host during early boot, sends an initial hello on the control channel, and keeps control traffic separate from raw log output from the start.
It also moves vsock bootstrap earlier in the init path so the control channel exists before the rest of guest setup continues. That lets the panic path send a final fatal report and stack trace to the host over vsock before powering the microVM off, instead of relying on stderr as a fallback observability path.
Overall, this change establishes the long term host guest communication model for scoutd and gives the guest a deterministic failure reporting path before networking, MMDS, and workload launch are layered on top. closes #4