Repository navigation
Add cc PC backend, browser VNC, RAM framebuffer and PE linking APIs - #37
Merged
Merged
Conversation
This was referenced Sep 13, 2026
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
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.
Add reusable infrastructure for running and displaying a caller-supplied VM: an in-process cc Linux/amd64 KVM backend, browser VNC, a RAM framebuffer protocol, and portable PE construction APIs.
-servefrontend accepts a VM returned by a caller's Starlark recipe.NT 3.1 image construction, guest display/miniport sources, ABI declarations, registry setup, launch recipes and whole-guest smokes are in tinyrangex #67. This PR supplies the reusable pieces that those recipes consume; it does not provide an NT 3.1 image builder or boot recipe.
Validation in trex: focused cc/KVM, RAM framebuffer, PE linker/resource, RFB/WebSocket and JavaScript tests, including race checks. Consumer integration in TinyRangeX: stock-Renvo driver ABI smoke, fresh NT 3.1 Notepad/Security and Write smokes, and Firefox launch/typing. These establish one working consumer of the APIs, not general guest compatibility.
Current backend limits: Linux/amd64 KVM, one CPU and IDE disk, BIOS modes 03h/12h, relative PS/2 input. Guest driver sources and NT-specific operational guidance have been moved into TinyRangeX.
Dependency: cc #210, pinned at
b42f4a0, for x86 KVM state and execution control. Merge cc #210, then this PR, then tinyrangex #67. No Renvo PR is required.CI fixes: grant the Go job access to KVM so native backend tests execute; remove the redundant single-exit loop in cc. Full local Go tests, vet, build and all 153 Starlark tests pass.