Repository navigation
doc: index the OpenVMM commits past the upstream roadmap's mapped tip - #474
Merged
Merged
Conversation
The upstream roadmap presented 2728f33ea as the OpenVMM fork tip, but NVX pins 7bf0ee28b, 139 commits later on the same first-parent chain. Record the mapped tip and the pin, extend the branch DAG, and group the unassigned commits by topic so their PR assignment can follow. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The documented pin, commit counts, ranges, and topic boundaries are consistent with the referenced history.
0 open findings
What changed in this PR
Documents the OpenVMM commits between the existing roadmap mapping and NVX’s current pinned revision.
Changes:
- Clarifies the mapped tip and current NVX pin.
- Extends the branch DAG through positions 167–305.
- Groups 139 unassigned commits by topic.
| File | Description |
|---|---|
doc/openvmm-upstream-roadmap.md |
Adds scope and topic indexing for post-mapping OpenVMM commits. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Pedro Henrique Penna (ppenna)
deleted the
doc-sync/openvmm-roadmap-pin
branch
October 10, 2026 15:13
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.
Summary
doc/openvmm-upstream-roadmap.mdpresented2728f33eaas the OpenVMM fork tip. NVX now pins7bf0ee28b826374a2d386067df0456b81bcae818, 139 commits later on the same first-parent chain, so the roadmap silently omitted every commit since 2026-10-01, including the time ABI v1, CPU profiles, generation-bound snapshots, IPv6 and port/protocol egress rules, and aggregate virtio-fs shares. This PR records which tip the mapping covers, adds the pin, and indexes the unmapped commits by topic.Conservative choice: assigning 139 commits to upstream PRs and classes (U/P/N/F) is a planning judgment, not a fact I can verify from source, so the new section lists them by topic and explicitly marks them not yet assigned. The existing PR graph, summary, and per-commit mapping are unchanged.
Changes
2728f33ea" → "Mapped fork tip:2728f33ea, position 166"; the mapping covers 001-166git -C openvmm rev-list --count --first-parent e1cdbd916..2728f33ea= 166, no merges7bf0ee28b, 139 commits past the mapped tip on the same chaingit rev-parse HEAD:openvmm;git -C openvmm merge-base --is-ancestor 2728f33ea HEADsucceeds;rev-list --count 2728f33ea..HEAD= 139;rev-list --merges --count= 0git -C openvmm log --reverse --first-parent 2728f33ea..HEAD, numbered from 167; topics from each commit's subject/body (e.g.3072d7a91body: "Remove the second slot", hence 284-285 "which position 302 removes")git show --name-onlyfor those commits withgit diff --name-onlyover PR10c1be51ed4^..b3070731e, PR11eea6dff56^..f6a4471fc, PR172ce524409^..56a2cdd15OpenVMM SHA (pinned submodule, source of truth):
7bf0ee28b826374a2d386067df0456b81bcae818. NVX base:origin/devat218ad09fd54965013edd028818ec078b7a6fcc8a.Follow-ups
microsoft/openvmmmain; it is dated 2026-10-01 (1fd455b19) and was not re-checked here.scripts/setup/README.mdis documentation outsidedoc/. Relocating it needsscripts/test_tool_versions.py(reads it by path) and thetool-versions.confcomment to change, plus links indoc/ci.mdanddoc/setup.md, which open PRs test-microvm: pause and resume a microVM through OpenVMM state control #405 and Adopt bind-once microVM image slots #406 touch, so it was left in place.unittest_results.txtis tracked at the repository root and looks like an accidentally committed test log (not a documentation change; not touched).Other docs checked without finding drift:
README.md,doc/build.md,doc/distribution.md,doc/project-structure.md(vsgit ls-files),doc/design/goals.md,configuration-boundary.md,snapshot-sharing-and-host-storage.md,copilot-adversarial-testing.md,doc/guests/*. Files changed by open PRs #405, #406, and #417 were left alone.Validation
python -m unittest scripts.test_nvx_tools.CliTests scripts.test_performance.PerformanceTests: Ran 110 tests, OK (skipped=1).doc/design.mdlinks every chapter indoc/design/: OK.git diff --check: clean.python scripts\nvx.py verify: passes.doc/.