Skip to content

openvmm: pin microVM v6.1, rebased onto upstream main - #1567

Merged
Pedro Henrique Penna (ppenna) merged 2 commits into
devfrom
agents/rebase-openvmm-chain-v6.1
Nov 13, 2026
Merged

Pedro Henrique Penna (ppenna) merged 2 commits into
devfrom
agents/rebase-openvmm-chain-v6.1

Conversation

@ppenna

@ppenna Pedro Henrique Penna (ppenna) commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

What and why

Status: The release has landed in OpenVMM: feature/microvm/dev is now the pin, 73cf40357, and feature/microvm/release/v6.0 holds the previous line at 5ca20ee08. OpenVMM CI passes the six jobs that NVX requires on the pin (run 43410228612), and NVX CI of this head passes (run 43413731642). This PR merges through the merge queue once a maintainer approves it; see Landing order.

Pins openvmm to microVM v6.1: the microVM chain of feature/microvm/dev rebased onto the latest upstream OpenVMM main as a minor release. Upstream merged seven of the chain's commits, so the rebase drops them; 16 commits conflicted with upstream and were resolved in place, and eight fixups at the tip adapt the chain to upstream changes that no conflict exposed, two of them to failures of upstream's ttrpc interface test that OpenVMM CI found. Most of the work comes from microsoft/openvmm#4553, upstream's SaveVM and RestoreVM for the management RPC, which records a snapshot ID in the snapshot manifest's field 18, so the gitlink commit also has nvx-rs's reader of a template's manifest accept that field. The second commit maps the rebased chain in the OpenVMM upstream roadmap.

OpenVMM source

What changed in OpenVMM

Seven drops. Upstream merged these, all but the first after review changes, so the rebase takes upstream's versions and adapts the later commits to them:

v6.0 position Commit Upstream
002 707747c16 flowey: distinguish native Windows and WSL nextest paths microsoft/openvmm#4595, 5d3ab02f0, an identical patch
008 299a04d4f pal: query Unix socket peer credentials microsoft/openvmm#4591, 42d4fe619, with tests
009 a0e70d99e pal: resolve the process token user SID microsoft/openvmm#4604, 6937acefb, in pal::windows::security itself rather than a user_sid module
014 5ed5f7a22 serial_socket: keep Windows named-pipe listeners reconnectable microsoft/openvmm#4609, f5ef11b8a, which keeps the write handling that a Retain console on a named pipe needs
051-053 6cea1ae18, 4ccef3c27, b585c7300 loader: buffer reuse, MP 1.4 table builder, firmware-less Linux direct boot microsoft/openvmm#4554, e4728b7f4, as loader::linux::mptable_boot with a zerocopy table builder and an I/O APIC numbered after the processors, loading through load_kernel_and_initrd_x64, which needs no buffer reuse

With them, PR04 has landed whole, and PR03, PR06, and PR14 keep one commit each.

16 conflicts, resolved in place. Eleven are with microsoft/openvmm#4553, which adds SaveVM and RestoreVM, records a snapshot ID in the manifest's field 18, and changes the snapshot publication that PR11 replaces:

  • The manifest keeps upstream's snapshot_id after the chain's fields; a microVM capture leaves it zero, the manifest's "no ID".
  • SaveVM and the command line's save publish through the chain's staged publication, which copies the memory backing file into a staged directory that a no-replace rename publishes, instead of upstream's in-place write and hard link. Upstream's check_snapshot_destination stays, before SaveVM pauses the VM.
  • RestoreVM restores a standard VM, in place from memory.bin, as upstream's does, and refuses a microVM, which restores from its authoritative manifest through CreateVM; the command line keeps its private copy-on-write restore. MemoryConfig.backing_file_path (field 10) is now upstream's optional field, which a standard VM gives SaveVM and a microVM its RAM file.
  • The service, the worker launch, petri, and the guides take upstream's SaveVM state, restore parameters, and advice beside the chain's.

The other five: microsoft/openvmm#4591 (the credentials module beside the chain's fd_table), microsoft/openvmm#5018, microsoft/openvmm#4147, and microsoft/openvmm#4554 (supports_acpi_power_button from the load mode, the microVM's load mode before IGVM, the direct-boot guide), microsoft/openvmm#4609 (its named-pipe tests replace the dropped commit's), microsoft/openvmm#5057 (the fork's CI gates take the runner of upstream's new pool tuples; cargo xflowey regen reproduces the merge), and microsoft/openvmm#4554 again, at position 183, whose routing of every IOAPIC input moves onto upstream's zerocopy builder. Position 121's generated workflows replayed without a conflict but displaced the SIVM IGVM steps of microsoft/openvmm#4940, so the rebase regenerated them with cargo xflowey regen. The roadmap's Conflicts of the v6.1 rebase lists each resolution.

Eight fixups at the tip, each to fold into the commits that it names at the next reorganization:

Position Fixup Upstream Fold into
262 55adb5c93 serial_socket, openvmm_entry: resolve user SIDs at upstream's path microsoft/openvmm#4604 103, 110
263 b9a8f7f6e openvmm_core: load microVMs through upstream's MP-table boot module microsoft/openvmm#4554 055, 176
264 7b98adc6d openvmm_entry, openvmm_helpers: read upstream's snapshots through OpenedSnapshot microsoft/openvmm#4553 031
265 5460c8e05 openvmm_entry, openvmm_helpers: record no snapshot ID in microVM captures microsoft/openvmm#4553 069, 119
266 649aeacf0 ttrpc: give the guest exit test's service upstream's SaveVM state microsoft/openvmm#4553 118
267 4a1d9b07a Guide, openvmm_entry: describe upstream's snapshots with the chain's publication microsoft/openvmm#4553 028, 032, 069
268 63688dd58 vmm_tests: save the ttrpc interface test's VM with a VMBus NIC microsoft/openvmm#4553 044
269 73cf40357 openvmm_helpers: drop an independent snapshot copy's page cache microsoft/openvmm#4553 028

Position 268 answers the first OpenVMM CI run of the release, run 43393543822 on 4a1d9b07a, whose four required VMM test jobs failed only ttrpc::test_ttrpc_interface: upstream's #4553 version of that test saves and restores the VM of its iteration 1, which has the test's only virtio-frontend NIC, and the chain's virtio-net (position 044, PR13) saves only a NIC bound to a static identity and feature contract, which the management RPC does not configure, so SaveVM answered save state not supported. Upstream's test already leaves the virtio consoles, which cannot be saved, out of that iteration; position 268 gives it the VMBus NIC of the other iterations and moves the virtio-frontend NIC to iteration 2, which does not save.

Position 269 answers the second, run 43398301692 on 63688dd58, whose MSHV VMM test job failed the same test after SaveVM succeeded: within a millisecond of the VM that RestoreVM restored in place from memory.bin starting, VP 1 took a memory access exit while an interrupt was being delivered, on guest RAM at 0x2644fe0, which OpenVMM's emulator refuses (an interrupt caused the memory access exit), and the guest stopped. Its other VMM test jobs passed the test, and upstream main passes it on MSHV (run 43340266748), where SaveVM hard-links the memory backing file into the snapshot; the chain's staged publication (position 028, PR11) copies it instead, writing only its chunks that are not all zero, and the copy's pages stay in the page cache. On nvx-mshv-test (Azure Linux 3, kernel 6.18.34.mshv3), cargo xflowey vmm-tests-run reproduces the failure at 63688dd58 in both repetitions with the snapshot on ext4, and the test passes with the snapshot on tmpfs, with a hard-linked memory.bin, or with the copy's page cache dropped after the copy is flushed; it still fails when the copy writes every chunk. Which part of MSHV's mapping of those pages makes the difference is not established, so the fix follows the observed behavior: position 269 has copy_exact drop each independent copy's page cache on Linux with posix_fadvise(POSIX_FADV_DONTNEED) once the copy is flushed, logging a warning if that fails. That covers memory.bin and a paired scratch image, at capture and in a private-copy restore. NVX's templates publish memory.bin by hard link and pair no scratch, and the benchmarks' captures give OpenVMM neither a memory backing file nor a paired-scratch tier, so neither makes such a copy; test-microvm's paired-scratch captures and private-copy restores do.

The other 34 upstream commits merge with the chain without conflicts.

What changed in NVX

  • Gitlink commit (0a86d8265): moves openvmm from 5ca20ee08 to 73cf40357. OpenVMM's manifests now carry field 18, which mesh writes even when the ID is zero, and nvx-rs's template manifest reader refuses fields that it does not know, so it accepts field 18 and checks only that it holds 16 bytes: a microVM capture leaves it zero, and a template depends on nothing in it. A manifest without it, of an earlier OpenVMM, still reads. The other vectors, excerpts, contract versions, and CPU profiles that nvx-rs copies from OpenVMM match the pin.
  • Roadmap commit (79e93568a): maps the rebased chain in doc/openvmm-upstream-roadmap.md. Positions from 003 on fall by the commits dropped before them (one through v6.0 position 007, three through 013, four through 050, seven from 054 on), so the commits after the mapped tip and the mapping now name each commit's v6.0 position. The mapped tip is position 124, 7f31de535, and the pin is position 269, 145 commits past it. It records the drops, the conflicts and fixups, the open upstream pull requests as of 2026-11-13 (vmm_core: make level-triggered legacy IRQs explicit openvmm#4611 and virt_whp, petri: enable native PCIe NVMe boot on WHP openvmm#4615 closed, seven of the ten open ones drafts), and corrects a stale position, 219 for 211, in the retired PR09 entry.

Validation

OpenVMM

With Rust 1.97.1, the toolchain of OpenVMM's CI:

  • Per-commit, on x86_64 Linux (Azure Linux 3) and x86_64 Windows 11, at the 27 commits that a conflict or a fixup changed or that change the pipelines (the 16 resolved, the eight fixups, and positions 002, 121, and 179): rustfmt +1.97.1 --check --edition 2024 on each changed .rs file and cargo xtask fmt --pass lints pass at all 27, and cargo xtask fmt --pass verify-flowey passes at positions 002, 120, 121, and 179. cargo check --locked --workspace --all-targets (on Windows without vtpm_util, whose vendored OpenSSL needs a native Perl, and guest_test_uefi and opentmk_executor, which upstream's Clippy job checks for their UEFI targets alone) passes at positions 002, 006, 027, 028, and 266-269. From position 032 to 265 it fails only with the breaks that fixups 262-266 repair, classified error by error on both hosts: upstream's RestoreVM calls the read_snapshot that position 031 replaced (until 264), the microVM loader calls the dropped loader::linux::microvm (until 263), the microVM capture and the benchmark lack snapshot_id (until 265), the guest exit test's service lacks upstream's SaveVM state (until 266), and, on Windows, the peer identities and control console call the dropped user_sid module (until 262).
  • At position 267: cargo xtask fmt passes all of its passes; cargo clippy --workspace --all-targets -- -D warnings passes on Linux (with --all-features, without guest_test_uefi and opentmk_executor) and on Windows (also without vtpm_util); cargo nextest run of the 20 packages that the conflicts and fixups change or build on passes 1321 of 1321 tests on Linux, and on Windows 1206 of 1207 tests across 19 binaries, the exception being sparse_mmap tests::test_shared_file_offsets_and_handle_lifetime, which fails on that host on upstream main 7d90c4104 too. At position 268, which changes only a VMM test, cargo clippy -p vmm_tests --all-targets -- -D warnings passes on Windows. At position 269, cargo xtask fmt passes all of its passes on Windows, cargo clippy -p openvmm_helpers --all-targets -- -D warnings passes on Linux and Windows, and cargo test -p openvmm_helpers passes 146 of 146 tests on Linux (nvx-kvm-test and nvx-mshv-test) and 138 of 138 on Windows.
  • VMM tests: cargo xflowey vmm-tests-run --filter "test(microvm)" passes 6 of 6 on WHP (Windows 11) at position 267. On nvx-mshv-test, cargo xflowey vmm-tests-run --filter "test(test_ttrpc_interface)" --repetitions 2, with TMPDIR on ext4, fails at 63688dd58 as OpenVMM CI did and passes both repetitions at 73cf40357. vmm-tests-run cannot build that test's Linux artifacts on Windows.
  • OpenVMM CI: run 43393543822, started by the release branch's push at 4a1d9b07a, passed the unit tests on x64 Linux and Windows, and its four required VMM test jobs each failed only ttrpc::test_ttrpc_interface, with save state not supported (KVM 108 of 109, MSHV 104 of 105, Windows Intel 281 of 282, Windows AMD 280 of 281), which position 268 fixes. Run 43398301692 on 63688dd58 passed the unit tests on x64 Linux and Windows and the KVM, Windows Intel, and Windows AMD VMM test jobs, ttrpc::test_ttrpc_interface included, and failed it in the MSHV VMM test job after RestoreVM, which position 269 fixes. Run 43410228612 on the pin, 73cf40357, passes all six jobs that NVX requires, the MSHV VMM test job with ttrpc::test_ttrpc_interface included. Two jobs that NVX does not require fail. run vmm-tests [x64-windows-amd-snp] fails 19 Hyper-V OpenHCL SNP tests; it fails 17-19 of them, a different set each time, on upstream main at the base (run 43340266748) and on both earlier runs of this release. run vmm-tests [x64-windows-intel-tdx] fails four Hyper-V OpenHCL TDX tests (two in tpm138, one in tpm, one in memstat): each guest boots, but its pipette never connects to the host (Operation timed out (os error 110)) until the test times out. That job passed on 63688dd58, on the same runner, at 09:26 UTC, and since then the pin changes only Linux code, which the job's Windows binaries do not compile and OpenHCL, which does not use openvmm_helpers, does not contain. A rerun on the pin failed three of the same tests in the same way, and a rerun of 63688dd58's TDX job, which had passed there, now fails 30 Hyper-V OpenHCL tests on that runner, PCAT ones among them, with the same pipette timeouts: the runner changed, not the pin. Its vmm-perf jobs, which NVX does not require either, pass.

NVX

  • python scripts\nvx.py verify, python scripts\openvmm_pin.py check-roadmap (269 positions, 278 references), python scripts\openvmm_pin.py check-branch --target origin/dev (two verified commits), python scripts\check_markdown_links.py, and git diff --check pass.
  • python scripts\local_gates.py --base origin/dev --run --keep-going: at this head, test-changes, markdown-links, test-layout, openvmm-vectors (4 passed), openvmm-cpu-profiles (1 passed), and nvx-cli (2198 and 84 Python tests, OK, 88 and 11 skipped, with NVX_RS set and Git's usr\bin on PATH) pass. At the first build of this branch, b1d982332, which has the same nvx-rs, nvx-rs-format, nvx-rs-lint, nvx-rs-test (2,724 passed, 38 ignored), nvx-rs-bundling (18 passed), nvx-rs-doc, nvx-rs-msrv, nvx-rs-adapter-protocol (50 passed), and nvx-rs-adapter-host (145 passed, 95 ignored) pass. openvmm-ci is left to CI. NVX CI of the previous head, 253502cdd (run 43404057041), which has the same nvx-rs and pinned 63688dd58, passed 33 jobs and skipped 8, and failed only OpenVMM CI of the pinned revision, on the MSHV job above, and the Required status check that needs it.
  • test-microvm: python3 scripts/nvx.py test-microvm --backend BACKEND, with OpenVMM built at the pin, passes 57 of 57 scenario runs at this head on KVM (nvx-kvm-test) and MSHV (nvx-mshv-test), both Azure Linux 3 virtual machines working on ext4, among them the paired-scratch captures and private-copy restores whose copies position 269 changes. On WHP (Windows 11, locally), it passed 57 of 57 at b1d982332, with OpenVMM built at 4a1d9b07a, whose Windows build has the pin's code: position 268 changes only a VMM test, and position 269 only Linux code. On each Linux host, nvx-rs download first installed release v0.1.0-dev.8bb7d532a10d, and python3 scripts/nvx.py build-openvmm then replaced its OpenVMM, as the changed SHA-256 and build/openvmm.provenance.json, which names 73cf40357, show; other sessions' scenarios ran on those hosts at the same time.
  • NVX CI of this head, run 43413731642, passes: 35 jobs succeed, OpenVMM CI of the pinned revision among them, and the 8 that this pull request's run skips (publication, performance recording, the merge-group cancellation, and the debug-kernel microVM tests) are skipped.
  • Not run locally: the AArch64, macOS, TDX, and SEV-SNP configurations, which only OpenVMM CI covers; see OpenVMM above.

Tests modified

python scripts\check_test_changes.py --base origin/dev lists five changes to existing tests, all for manifest field 18:

  • ManifestSpec (nvx-rs/src/host/template/tests.rs) gains snapshot_id, ManifestSpec::template sets it to 16 zero bytes, and encode_with writes it as field 18 after field 15, as OpenVMM's mesh encoding does, so every manifest test reads a manifest of the pinned OpenVMM.
  • fields_that_the_format_does_not_have_are_refused no longer expects field 18 to be refused, since the format now has it, and checks 19 and 20, which upstream reserves, instead.
  • truncated_manifests_are_refused skips the one prefix of the template's encoding that is a whole manifest, the one without field 18, which an earlier OpenVMM wrote and which reads.

The new only_the_length_of_the_snapshot_id_is_checked covers a manifest without the field and one with a nonzero ID, both of which read like the template, and refuses IDs of 0, 15, and 17 bytes.

Equivalence

  • Patches: git range-diff ba105dd7f..5ca20ee08 7d90c4104..73cf40357 pairs 261 of the 269 commits in order: 220 have identical patches, 16 differ by their resolutions, and 25 differ only in context. The seven dropped commits have no counterpart, and the eight fixups are new. No commit is reordered.
  • Tree: the pin's tree differs from a three-way textual merge of upstream's 44 commits into 5ca20ee08 (git merge-tree --write-tree 5ca20ee08 7d90c4104), which conflicts in 21 files, in 43 files: those 21, the four workflows that the rebase regenerated, five files of the dropped commits, nine more that the fixups change, and four that the resolutions of positions 027, 183, and 221 change beside their conflicts.

Landing order

  1. Done: OpenVMM CI passes NVX's six required jobs on the pin, 73cf40357 (run 43410228612).
  2. Done: feature/microvm/release/v6.0 was fast-forwarded from cf6c03977 to 5ca20ee08, without force, so every revision of the old line that NVX pinned stays on a branch.
  3. Done: feature/microvm/dev moved from 5ca20ee08 to the pin, 73cf40357, with a lease on 5ca20ee08, because .gitmodules tracks that branch: python scripts/openvmm_release.py land --remote origin --old-head 5ca20ee081c255bed107e58b6dc5b5b769b6101d --new-head 73cf403574a8907ee94dab0ab9d648152b832b05 --prev-release feature/microvm/release/v6.0 --push, after check-openvmm-ci of the pin passed again. git ls-remote shows feature/microvm/dev and feature/microvm/release/v6.1 at 73cf40357 and feature/microvm/release/v6.0 at 5ca20ee08. [DO NOT REVIEW] microvm: enable governed ARM64 cold boot on WHP openvmm#5045 now needs a rebase onto it.
  4. Pending: this PR merges through the merge queue once a maintainer approves it.

NVX head: 79e93568a9f8eafb2b88de372bf3b67ed1bbf22f, on dev at 8bb7d532a10.

@ppenna Pedro Henrique Penna (ppenna) added the tests-modified Changes existing tests, test data, or test wiring label Nov 13, 2026
Copilot AI balanced review requested due to automatic review settings November 13, 2026 09:46
@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

This pull request changes existing tests

It modifies or removes 5 existing test asset(s), listed below. Review each with care: a change to a test can hide a regression that the test caught. See doc/contribute.md#changes-to-existing-tests.

Test code

Change What Before After
modified helper struct ManifestSpec in host::template::tests nvx-rs/src/host/template/tests.rs:572 nvx-rs/src/host/template/tests.rs:572
modified helper fn template in host::template::tests, impl ManifestSpec`` nvx-rs/src/host/template/tests.rs:618 nvx-rs/src/host/template/tests.rs:620
modified helper fn encode_with in host::template::tests, impl ManifestSpec`` nvx-rs/src/host/template/tests.rs:914 nvx-rs/src/host/template/tests.rs:917
modified test fn fields_that_the_format_does_not_have_are_refused in host::template::manifest::tests nvx-rs/src/host/template/manifest/tests.rs:326 nvx-rs/src/host/template/manifest/tests.rs:326
modified test fn truncated_manifests_are_refused in host::template::manifest::tests nvx-rs/src/host/template/manifest/tests.rs:428 nvx-rs/src/host/template/manifest/tests.rs:447

Relocated unchanged: 0; added: 1. Compared the merge base 8bb7d532a10d with 79e93568a9f8.

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.

🔵 Needs a closer look

The 268-commit OpenVMM rebase requires maintainer-led backend validation because the PR reports an unresolved MSHV RestoreVM failure, exact-pin CI remains in progress, and supplied diffs omit the rebased source.

No open issues 🎉

What changed in this PR

This PR rebases NVX’s OpenVMM pin onto microVM v6.1. The reviewed changes adapt NVX’s manifest reader to upstream’s new snapshot ID field while preserving compatibility with older manifests.

Changes:

  • Accept manifest field 18 when it contains a 16-byte snapshot ID, without using its value.
  • Update fixtures and tests to cover absent, nonzero, and malformed IDs, plus truncation handling.
  • Document snapshot ID validation for template and restore manifests.
File Description
nvx-rs/​src/​host/​template/​tests.rs Adds optional snapshot IDs to shared manifest fixtures and encoding.
nvx-rs/​src/​host/​template/​manifest/​tests.rs Tests snapshot ID compatibility and length validation; adjusts unknown-field and truncation checks.
nvx-rs/​src/​host/​template/​manifest.rs Accepts field 18 and validates its 16-byte length.
nvx-rs/​README.md Documents length-only snapshot ID validation.

Review effort: Balanced

Pin the openvmm submodule to 73cf40357, the head of the new
feature/microvm/release/v6.1 branch of microsoft/openvmm. That branch
rebases the 268-commit microVM chain of feature/microvm/dev, through
the previous pin, 5ca20ee08, from ba105dd7f onto microsoft/openvmm main
at 7d90c4104, 44 upstream commits later.

Upstream landed seven of the chain's commits, so the rebase drops v6.0
positions 002, 008, 009, and 014, which microsoft/openvmm#4595,
microsoft/openvmm#4591, microsoft/openvmm#4604, and
microsoft/openvmm#4609 merged, and 051-053, whose MP table builder and
firmware-less Linux direct boot microsoft/openvmm#4554 merged in a
revised form. Replaying the other 261 conflicts at 16 positions, 11 of
them with microsoft/openvmm#4553, upstream's SaveVM and RestoreVM for
the management RPC, which records a snapshot ID in the manifest's field
18 and changes the snapshot publication that the chain replaces. The
rebase publishes upstream's snapshots through the chain's staged
publication, gives a microVM capture the zero snapshot ID, and has
RestoreVM refuse a microVM, which restores from its authoritative
manifest through CreateVM instead. Eight fixups at its tip adapt the
chain to upstream changes that no conflict exposed: the user SID
queries at upstream's path, upstream's MP-table boot module, and six
for microsoft/openvmm#4553. The last two save the VM of upstream's
ttrpc interface test with a VMBus NIC, since the chain's virtio-net
saves only a NIC with a static identity and feature contract, and drop
the page cache of each independent copy that the chain's snapshot
publication makes: on MSHV, with the snapshot on ext4, the VM that the
test restores in place from such a copy of its memory stopped as soon
as it resumed while the copy's pages were still cached.

OpenVMM's snapshot manifests therefore carry field 18, which mesh
writes even when the ID is zero, and nvx-rs's reader of a template's
manifest refuses fields that it does not know. Accept field 18 and
check only that it holds 16 bytes, since a microVM capture leaves it
zero and a template depends on nothing in it, and test that a manifest
without it, one of an earlier OpenVMM, still reads, as does one with an
ID that is not zero. The other vectors, excerpts, contract versions,
and CPU profiles that nvx-rs copies from OpenVMM match the pin.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The feature/microvm/release/v6.1 rebase, which the previous commit
pins, moved the microVM chain from ba105dd7f onto upstream main at
7d90c4104 and dropped the seven commits that upstream landed, so
positions from 003 on are lower than in v6.0: by one through v6.0
position 007, by three through 013, by four through 050, and by seven
from 054 on. Remap the scope, upstream status, graph, branch DAG, the
commits after the mapped tip, PR summary, and commit mapping onto the
rebased commits, and name each commit's v6.0 position in the table of
commits after the mapped tip and in the mapping. Record the dropped
commits and the forms in which upstream landed them, which leave
nothing of PR04, the 16 conflicts that the rebase resolved and the
workflows that it regenerated at position 121, and the eight fixups at
positions 262-269, each with the commits that it folds into.

As of 2026-11-13, microsoft/openvmm#4611 and microsoft/openvmm#4615
are closed, and seven of the ten open upstream pull requests are
drafts. The remarks on whether commits apply to upstream main record
what was found on ba105dd7f and earlier bases; the rebase did not check
them again.

The pin, 73cf40357, is position 269, 145 commits past the mapped tip.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings November 13, 2026 11:01

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.

🔵 Needs a closer look

The 268-commit OpenVMM rebase has an unresolved MSHV RestoreVM regression and failed exact-pin CI, requiring maintainer assessment and passing required runtime validation before promotion.

No open issues 🎉

Review effort: Balanced

@ppenna
Pedro Henrique Penna (ppenna) added this pull request to the merge queue Nov 13, 2026
Merged via the queue into dev with commit c9817ae Nov 13, 2026
55 checks passed
@ppenna
Pedro Henrique Penna (ppenna) deleted the agents/rebase-openvmm-chain-v6.1 branch November 13, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tests-modified Changes existing tests, test data, or test wiring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants