Skip to content

doc: index the OpenVMM commits past the upstream roadmap's mapped tip - #474

Merged
Pedro Henrique Penna (ppenna) merged 1 commit into
devfrom
doc-sync/openvmm-roadmap-pin
Oct 10, 2026
Merged

Pedro Henrique Penna (ppenna) merged 1 commit into
devfrom
doc-sync/openvmm-roadmap-pin

Conversation

@ppenna

Copy link
Copy Markdown
Contributor

Summary

doc/openvmm-upstream-roadmap.md presented 2728f33ea as the OpenVMM fork tip. NVX now pins 7bf0ee28b826374a2d386067df0456b81bcae818, 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

Statement Evidence
Scope: "OpenVMM fork tip: 2728f33ea" → "Mapped fork tip: 2728f33ea, position 166"; the mapping covers 001-166 git -C openvmm rev-list --count --first-parent e1cdbd916..2728f33ea = 166, no merges
Scope: add NVX's pinned revision 7bf0ee28b, 139 commits past the mapped tip on the same chain git rev-parse HEAD:openvmm; git -C openvmm merge-base --is-ancestor 2728f33ea HEAD succeeds; rev-list --count 2728f33ea..HEAD = 139; rev-list --merges --count = 0
Branch DAG ends at the NVX pin via unassigned positions 167-305 Same commands
New "Commits after the mapped tip" table: 13 topic groups with positions, inclusive ranges, and counts (sum 139) git -C openvmm log --reverse --first-parent 2728f33ea..HEAD, numbered from 167; topics from each commit's subject/body (e.g. 3072d7a91 body: "Remove the second slot", hence 284-285 "which position 302 removes")
Positions 255-259 (legacy microVM clock removal) change files that PR10 and PR17 also change; position 261 (manifest v6 only) changes files that PR11 and PR17 also change File-set intersection of git show --name-only for those commits with git diff --name-only over PR10 c1be51ed4^..b3070731e, PR11 eea6dff56^..f6a4471fc, PR17 2ce524409^..56a2cdd15

OpenVMM SHA (pinned submodule, source of truth): 7bf0ee28b826374a2d386067df0456b81bcae818. NVX base: origin/dev at 218ad09fd54965013edd028818ec078b7a6fcc8a.

Follow-ups

  • Classify positions 167-305 (U/P/N/F) and assign them to PRs, revisiting PR10, PR11, and PR17 where the later commits rewrite their code (legacy clock paths, snapshot manifest versions 2-5).
  • Refresh the "Upstream status" section against current microsoft/openvmm main; it is dated 2026-10-01 (1fd455b19) and was not re-checked here.
  • scripts/setup/README.md is documentation outside doc/. Relocating it needs scripts/test_tool_versions.py (reads it by path) and the tool-versions.conf comment to change, plus links in doc/ci.md and doc/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.txt is 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 (vs git 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).
  • Throwaway checker outside the repo: every relative link and anchor in the changed file and in files linking to it resolves; one H1; balanced code fences; doc/design.md links every chapter in doc/design/: OK.
  • git diff --check: clean. python scripts\nvx.py verify: passes.
  • Documentation-only: the single changed path is under doc/.

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>
Copilot AI balanced review requested due to automatic review settings October 10, 2026 15:09
@ppenna Pedro Henrique Penna (ppenna) added the documentation Improvements or additions to documentation label Oct 10, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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.

@ppenna
Pedro Henrique Penna (ppenna) merged commit a9816d4 into dev Oct 10, 2026
28 checks passed
@ppenna
Pedro Henrique Penna (ppenna) deleted the doc-sync/openvmm-roadmap-pin branch October 10, 2026 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants