[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WF6MVTYEFTS42E2JF5Y28G":3,"skill-same:01M6WF6MVTYEFTS42E2JF5Y28G":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6WF6MVTYEFTS42E2JF5Y28G","nvx-rebase-openvmm-chain",null,"Rebase or reorganize the OpenVMM microVM chain onto the latest upstream main as a new feature\u002Fmicrovm\u002Frelease branch, validate and publish it, pin it in NVX with a remapped roadmap, and land it. Use for microVM release rebases and reorganizations, chain commits that upstream landed, rebase conflicts and fixups, and the release landing order.","microsoft\u002Fnvx","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BJEK52F2VM8QAE8TEX086",841,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-rebase-openvmm-chain\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"nvx rebase openvmm chain","rebase","chain","conflicts","new","for","with","as","feature","draft","upstream","main","microvm","roadmap","ready","use","landing","branch","pin","commits","publish","2026-11-10 10:12:30",false,"---\nname: nvx-rebase-openvmm-chain\ndescription: \"Rebase or reorganize the OpenVMM microVM chain onto the latest upstream main as a new feature\u002Fmicrovm\u002Frelease branch, validate and publish it, pin it in NVX with a remapped roadmap, and land it. Use for microVM release rebases and reorganizations, chain commits that upstream landed, rebase conflicts and fixups, and the release landing order.\"\nargument-hint: \"[rebase|reorganization] [upstream=main] [Draft|Ready]\"\n---\n\n# Rebase The OpenVMM MicroVM Chain\n\n`feature\u002Fmicrovm\u002Fdev` of `microsoft\u002Fopenvmm` carries the microVM chain on a\nfork base taken from upstream `main`. A release moves the whole chain onto a\nnewer upstream `main` as `feature\u002Fmicrovm\u002Frelease\u002FvX.Y`:\n\n- A **rebase**, the next minor version, replays every commit, drops those whose\n  changes upstream landed, resolves conflicts in place, and adds fixups at its\n  tip for upstream changes that break the chain without a conflict.\n- A **reorganization**, the next major version, also folds those fixups into\n  the commits that they fix and regroups commits so that every commit builds\n  on the new base; it may change behavior.\n\nIt rewrites shared branches of `microsoft\u002Fopenvmm`, so push only when the user\nasks. Its NVX commits and pull request follow\n[nvx-promote-openvmm-pin](..\u002Fnvx-promote-openvmm-pin\u002FSKILL.md), except as\nsection 6 says. Commands use `python3`; use `python` on Windows.\n\n## 1. State\n\n- Preserve dirty state in both repositories, and work on the chain in a worktree\n  of `openvmm\u002F` outside both checkouts, never in `openvmm\u002F` itself.\n- Use a remote of `openvmm\u002F` that resolves to `microsoft\u002Fopenvmm`; add one with\n  `git -C openvmm remote add REMOTE https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm.git`\n  when none does, since older checkouts name `nanvix\u002Fopenvmm` `origin`.\n- Record the state:\n\n  ```console\n  python3 scripts\u002Fopenvmm_release.py state --remote REMOTE --kind rebase\n  ```\n\n  It fetches upstream `main`, `feature\u002Fmicrovm\u002Fdev`, and the release branches;\n  stops on a shallow history; and reports `old_head`, `old_base` (which must be\n  the roadmap's fork base), the previous release and its head, NVX's pin,\n  `new_base` and its date, the next version (refusing one that exists), the\n  open OpenVMM pull requests into `feature\u002Fmicrovm\u002Fdev` with their stacked\n  layers, and NVX's open pin promotions. Pass `--kind reorganization` for a\n  major version, and ask which kind it is unless the user said so.\n- Settle the prerequisites: land each open OpenVMM pull request in dependency\n  order, as nvx-promote-openvmm-pin describes, or agree with the user to carry\n  its commits into the release. Retarget a stacked pull request to\n  `feature\u002Fmicrovm\u002Fdev` with `gh pr edit` only once its parent landed, after\n  `gh stack unstack` when a native stack locks its base. Merge or close NVX's\n  open pin promotions, since a revision of the old chain leaves the branch that\n  `.gitmodules` tracks once `feature\u002Fmicrovm\u002Fdev` moves.\n\n## 2. Choose What To Drop\n\n```console\npython3 scripts\u002Fopenvmm_release.py drops --old-base OLD_BASE --old-head OLD_HEAD --new-base NEW_BASE\n```\n\nIt lists upstream's commits since the old base, the chain commits whose patches\nupstream already has, and the roadmap's open upstream pull requests with their\nstates. Drop each commit whose change upstream merged, even in a revised form,\nand adapt the later commits to upstream's version. Drop a commit that an\nupstream change supersedes only once you have shown that upstream covers what\nit does. Record each drop's former position, fork commit, roadmap PR, upstream\npull request, and upstream commit for the roadmap.\n\n## 3. Replay The Chain\n\n1. Add the worktree with an absolute directory outside both checkouts, and\n   replay the chain onto the new base, changing each dropped commit's `pick` to\n   `drop`:\n\n   ```console\n   git -C openvmm worktree add -b microvm-release-VERSION DIRECTORY OLD_HEAD\n   git -C DIRECTORY rebase -i --onto NEW_BASE OLD_BASE\n   ```\n\n2. Keep commit signing on; never pass `--no-gpg-sign` or override\n   `commit.gpgsign`, and stop if signing fails. Drop no other commit without\n   the user's approval, and record each commit that the rebase drops as empty.\n3. Resolve each conflict where it occurs, keeping the intent of both upstream's\n   change and the commit, and record its position, commit, the upstream pull\n   request that it conflicts with, and the resolution:\n   - Regenerate generated pipelines with `cargo xflowey regen` instead of\n     merging their text, and require `cargo xtask fmt --pass verify-flowey` at\n     every commit that changes `flowey\u002F` or the generated files.\n   - In `Cargo.lock`, keep both sides' entries, and require\n     `cargo check --locked` at that commit.\n4. Fix upstream changes that break the chain without a conflict, which builds\n   and tests find. In a rebase, add a fixup commit at the tip for each, naming\n   the upstream pull request and the commits that it folds into at the next\n   reorganization. In a reorganization, fold each fix into the commits that it\n   fixes, keeping the anchor's author and date and crediting the folded\n   commits' authors with `Co-authored-by`; keep commits that can go upstream on\n   their own apart. Record where each fix went.\n5. Check the chain:\n\n   ```console\n   python3 scripts\u002Fopenvmm_release.py check-chain --dir DIRECTORY --new-base NEW_BASE --old-base OLD_BASE --old-head OLD_HEAD\n   ```\n\n   It requires no merges and a signature on every commit, good wherever this\n   host can verify it; it lists the signatures that this host cannot verify,\n   with how to let git verify them, and gives the range diff's counts. Claim\n   tree equivalence only for equal trees; a reorganization that changes\n   behavior claims neither tree nor patch equivalence and rests on per-commit\n   builds and tests.\n\n## 4. Validate The Chain\n\n- `python3 scripts\u002Fopenvmm_release.py check-commits --dir DIRECTORY --new-base NEW_BASE`\n  runs `rustfmt` on the changed Rust files, `cargo check --locked --workspace\n  --all-targets`, and `cargo xtask fmt --pass lints` at each selected commit,\n  on x86_64 Linux and on x86_64 Windows: every commit of a reorganization, and\n  at least the commits of a rebase that a conflict or a fixup changed\n  (`--commits SHA...`). In a rebase, an intermediate failure that an upstream\n  change causes is acceptable with the tip fixup that resolves it; the head\n  must pass.\n- At the head, run [the OpenVMM instructions'](..\u002F..\u002F..\u002Fopenvmm\u002F.github\u002Fcopilot-instructions.md)\n  gates for each package that a conflict, fixup, or fold changed: `cargo xtask\n  fmt`, `cargo clippy --workspace --all-targets -- -D warnings` on Linux and\n  Windows, the packages' unit tests, and the microVM VMM tests through\n  `cargo xflowey vmm-tests-run --filter \"test(microvm)\"`. Report each platform\n  that you could not use as left to OpenVMM CI.\n- OpenVMM's CI does not run NVX's workloads, so section 6 runs NVX's scenarios\n  on the new head too.\n\n## 5. Publish The Release Branch\n\nWhen the user asks:\n\n```console\npython3 scripts\u002Fopenvmm_release.py publish --dir DIRECTORY --version VERSION --remote REMOTE --push\n```\n\nIt pushes the release branch without force, which runs OpenVMM CI, so the\nrelease needs no OpenVMM pull request; waits for that run to appear; and checks\nit with `nvx.py check-openvmm-ci`. The six jobs that NVX requires must pass.\nBefore calling another failed job unrelated, find its root cause and show that\nit fails on upstream `main` or on the previous release too. Fix a failure that\nthe chain causes: a rebase gets a tip fixup, pushed without force; a\nreorganization rewrites the branch, which needs the user's approval, a lease\non the published head, and a `feature\u002Fmicrovm\u002Fdev` that does not point to it\nyet. Tests that encode ABI versions change with a reorganization that restarts\nthem.\n\n## 6. Pin The Release In NVX\n\nBuild the NVX branch, its two commits, and its pull request as sections 3, 5,\nand 6 of nvx-promote-openvmm-pin describe, with these differences:\n\n- No commit of the old chain is an ancestor of the new head, so its roadmap\n  section does not apply: remap the whole roadmap as\n  [references\u002Fremap.md](references\u002Fremap.md) describes, then run\n  `python3 scripts\u002Fopenvmm_pin.py check-roadmap --worktree`.\n- Name the commits `openvmm: pin microVM VERSION, rebased onto upstream main`\n  (or `reorganized onto upstream main`) and\n  `doc: map the OpenVMM roadmap onto the microVM VERSION rebase` (or\n  `reorganization`).\n- The comparisons of what `nvx-rs` copies from OpenVMM decide the gitlink\n  commit's coordinated changes. A release that changes an ABI changes more,\n  such as `nvx::contract`, `SOURCE-MANIFEST.json`, the guest's decoders, and the\n  tests that encode the versions, which the pull request explains under the\n  `tests-modified` label.\n- With the submodule at the new head, build OpenVMM with\n  `python3 scripts\u002Fnvx.py build-openvmm`, and run\n  `python3 scripts\u002Fnvx.py test-microvm --backend BACKEND` on each backend that\n  you can reach, locally or through\n  [nvx-prepare-host](..\u002Fnvx-prepare-host\u002FSKILL.md); leave the others to CI.\n\nIts body gives the OpenVMM source (the pinned revision, the previous pin, the\nnew base, upstream `main` since it, the absence of an OpenVMM pull request, and\nthe signatures), what changed in OpenVMM and in NVX, the equivalence evidence,\nthe validation, and the landing order of section 7. Ask whether it is Draft or\nReady.\n\n## 7. Land The Release\n\nOnce OpenVMM CI passed NVX's required jobs on the new head, and only when the\nuser asks:\n\n```console\npython3 scripts\u002Fopenvmm_release.py land --remote REMOTE --old-head OLD_HEAD --new-head NEW_HEAD --prev-release PREV_RELEASE --push\n```\n\nWithout `--push`, it prints the plan. It fetches `feature\u002Fmicrovm\u002Fdev` again\nand stops when the branch moved: carry the new commits onto the release, repeat\nsections 4 to 6, including publication, OpenVMM CI, and the NVX pin, and land\nagain with the new heads. It then fast-forwards the previous release branch to\nthe old head, never by force, so that every revision of the old line that NVX\npinned stays on a branch that `git submodule update` of an older NVX commit can\nfetch; and it moves `feature\u002Fmicrovm\u002Fdev` to the new head with a lease on the\nold one. Each OpenVMM pull request still open against `feature\u002Fmicrovm\u002Fdev`\nthen needs a rebase. The NVX pull request merges through the merge queue once\na maintainer approves it.\n\n## Report\n\nReport the kind and version of the release; the old and new bases and heads;\nthe drops with their upstream pull requests; the conflicts and their\nresolutions; the fixups or folds; the merge and signature checks; the\nequivalence evidence; the per-commit and head validation; the OpenVMM CI runs;\nthe previous release branch's fast-forward and the move of\n`feature\u002Fmicrovm\u002Fdev`; the NVX commits, pull request, and exact-head workflow\nrun; and every blocked or pending gate.\n","# Rebase The OpenVMM MicroVM Chain\n\n`feature\u002Fmicrovm\u002Fdev` of `microsoft\u002Fopenvmm` carries the microVM chain on a\nfork base taken from upstream `main`. A release moves the whole chain onto a\nnewer upstream `main` as `feature\u002Fmicrovm\u002Frelease\u002FvX.Y`:\n\n- A **rebase**, the next minor version, replays every commit, drops those whose\n  changes upstream landed, resolves conflicts in place, and adds fixups at its\n  tip for upstream changes that break the chain without a conflict.\n- A **reorganization**, the next major version, also folds those fixups into\n  the commits that they fix and regroups commits so that every commit builds\n  on the new base; it may change behavior.\n\nIt rewrites shared branches of `microsoft\u002Fopenvmm`, so push only when the user\nasks. Its NVX commits and pull request follow\n[nvx-promote-openvmm-pin](..\u002Fnvx-promote-openvmm-pin\u002FSKILL.md), except as\nsection 6 says. Commands use `python3`; use `python` on Windows.\n\n## 1. State\n\n- Preserve dirty state in both repositories, and work on the chain in a worktree\n  of `openvmm\u002F` outside both checkouts, never in `openvmm\u002F` itself.\n- Use a remote of `openvmm\u002F` that resolves to `microsoft\u002Fopenvmm`; add one with\n  `git -C openvmm remote add REMOTE https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm.git`\n  when none does, since older checkouts name `nanvix\u002Fopenvmm` `origin`.\n- Record the state:\n\n  ```console\n  python3 scripts\u002Fopenvmm_release.py state --remote REMOTE --kind rebase\n  ```\n\n  It fetches upstream `main`, `feature\u002Fmicrovm\u002Fdev`, and the release branches;\n  stops on a shallow history; and reports `old_head`, `old_base` (which must be\n  the roadmap's fork base), the previous release and its head, NVX's pin,\n  `new_base` and its date, the next version (refusing one that exists), the\n  open OpenVMM pull requests into `feature\u002Fmicrovm\u002Fdev` with their stacked\n  layers, and NVX's open pin promotions. Pass `--kind reorganization` for a\n  major version, and ask which kind it is unless the user said so.\n- Settle the prerequisites: land each open OpenVMM pull request in dependency\n  order, as nvx-promote-openvmm-pin describes, or agree with the user to carry\n  its commits into the release. Retarget a stacked pull request to\n  `feature\u002Fmicrovm\u002Fdev` with `gh pr edit` only once its parent landed, after\n  `gh stack unstack` when a native stack locks its base. Merge or close NVX's\n  open pin promotions, since a revision of the old chain leaves the branch that\n  `.gitmodules` tracks once `feature\u002Fmicrovm\u002Fdev` moves.\n\n## 2. Choose What To Drop\n\n```console\npython3 scripts\u002Fopenvmm_release.py drops --old-base OLD_BASE --old-head OLD_HEAD --new-base NEW_BASE\n```\n\nIt lists upstream's commits since the old base, the chain commits whose patches\nupstream already has, and the roadmap's open upstream pull requests with their\nstates. Drop each commit whose change upstream merged, even in a revised form,\nand adapt the later commits to upstream's version. Drop a commit that an\nupstream change supersedes only once you have shown that upstream covers what\nit does. Record each drop's former position, fork commit, roadmap PR, upstream\npull request, and upstream commit for the roadmap.\n\n## 3. Replay The Chain\n\n1. Add the worktree with an absolute directory outside both checkouts, and\n   replay the chain onto the new base, changing each dropped commit's `pick` to\n   `drop`:\n\n   ```console\n   git -C openvmm worktree add -b microvm-release-VERSION DIRECTORY OLD_HEAD\n   git -C DIRECTORY rebase -i --onto NEW_BASE OLD_BASE\n   ```\n\n2. Keep commit signing on; never pass `--no-gpg-sign` or override\n   `commit.gpgsign`, and stop if signing fails. Drop no other commit without\n   the user's approval, and record each commit that the rebase drops as empty.\n3. Resolve each conflict where it occurs, keeping the intent of both upstream's\n   change and the commit, and record its position, commit, the upstream pull\n   request that it conflicts with, and the resolution:\n   - Regenerate generated pipelines with `cargo xflowey regen` instead of\n     merging their text, and require `cargo xtask fmt --pass verify-flowey` at\n     every commit that changes `flowey\u002F` or the generated files.\n   - In `Cargo.lock`, keep both sides' entries, and require\n     `cargo check --locked` at that commit.\n4. Fix upstream changes that break the chain without a conflict, which builds\n   and tests find. In a rebase, add a fixup commit at the tip for each, naming\n   the upstream pull request and the commits that it folds into at the next\n   reorganization. In a reorganization, fold each fix into the commits that it\n   fixes, keeping the anchor's author and date and crediting the folded\n   commits' authors with `Co-authored-by`; keep commits that can go upstream on\n   their own apart. Record where each fix went.\n5. Check the chain:\n\n   ```console\n   python3 scripts\u002Fopenvmm_release.py check-chain --dir DIRECTORY --new-base NEW_BASE --old-base OLD_BASE --old-head OLD_HEAD\n   ```\n\n   It requires no merges and a signature on every commit, good wherever this\n   host can verify it; it lists the signatures that this host cannot verify,\n   with how to let git verify them, and gives the range diff's counts. Claim\n   tree equivalence only for equal trees; a reorganization that changes\n   behavior claims neither tree nor patch equivalence and rests on per-commit\n   builds and tests.\n\n## 4. Validate The Chain\n\n- `python3 scripts\u002Fopenvmm_release.py check-commits --dir DIRECTORY --new-base NEW_BASE`\n  runs `rustfmt` on the changed Rust files, `cargo check --locked --workspace\n  --all-targets`, and `cargo xtask fmt --pass lints` at each selected commit,\n  on x86_64 Linux and on x86_64 Windows: every commit of a reorganization, and\n  at least the commits of a rebase that a conflict or a fixup changed\n  (`--commits SHA...`). In a rebase, an intermediate failure that an upstream\n  change causes is acceptable with the tip fixup that resolves it; the head\n  must pass.\n- At the head, run [the OpenVMM instructions'](..\u002F..\u002F..\u002Fopenvmm\u002F.github\u002Fcopilot-instructions.md)\n  gates for each package that a conflict, fixup, or fold changed: `cargo xtask\n  fmt`, `cargo clippy --workspace --all-targets -- -D warnings` on Linux and\n  Windows, the packages' unit tests, and the microVM VMM tests through\n  `cargo xflowey vmm-tests-run --filter \"test(microvm)\"`. Report each platform\n  that you could not use as left to OpenVMM CI.\n- OpenVMM's CI does not run NVX's workloads, so section 6 runs NVX's scenarios\n  on the new head too.\n\n## 5. Publish The Release Branch\n\nWhen the user asks:\n\n```console\npython3 scripts\u002Fopenvmm_release.py publish --dir DIRECTORY --version VERSION --remote REMOTE --push\n```\n\nIt pushes the release branch without force, which runs OpenVMM CI, so the\nrelease needs no OpenVMM pull request; waits for that run to appear; and checks\nit with `nvx.py check-openvmm-ci`. The six jobs that NVX requires must pass.\nBefore calling another failed job unrelated, find its root cause and show that\nit fails on upstream `main` or on the previous release too. Fix a failure that\nthe chain causes: a rebase gets a tip fixup, pushed without force; a\nreorganization rewrites the branch, which needs the user's approval, a lease\non the published head, and a `feature\u002Fmicrovm\u002Fdev` that does not point to it\nyet. Tests that encode ABI versions change with a reorganization that restarts\nthem.\n\n## 6. Pin The Release In NVX\n\nBuild the NVX branch, its two commits, and its pull request as sections 3, 5,\nand 6 of nvx-promote-openvmm-pin describe, with these differences:\n\n- No commit of the old chain is an ancestor of the new head, so its roadmap\n  section does not apply: remap the whole roadmap as\n  [references\u002Fremap.md](references\u002Fremap.md) describes, then run\n  `python3 scripts\u002Fopenvmm_pin.py check-roadmap --worktree`.\n- Name the commits `openvmm: pin microVM VERSION, rebased onto upstream main`\n  (or `reorganized onto upstream main`) and\n  `doc: map the OpenVMM roadmap onto the microVM VERSION rebase` (or\n  `reorganization`).\n- The comparisons of what `nvx-rs` copies from OpenVMM decide the gitlink\n  commit's coordinated changes. A release that changes an ABI changes more,\n  such as `nvx::contract`, `SOURCE-MANIFEST.json`, the guest's decoders, and the\n  tests that encode the versions, which the pull request explains under the\n  `tests-modified` label.\n- With the submodule at the new head, build OpenVMM with\n  `python3 scripts\u002Fnvx.py build-openvmm`, and run\n  `python3 scripts\u002Fnvx.py test-microvm --backend BACKEND` on each backend that\n  you can reach, locally or through\n  [nvx-prepare-host](..\u002Fnvx-prepare-host\u002FSKILL.md); leave the others to CI.\n\nIts body gives the OpenVMM source (the pinned revision, the previous pin, the\nnew base, upstream `main` since it, the absence of an OpenVMM pull request, and\nthe signatures), what changed in OpenVMM and in NVX, the equivalence evidence,\nthe validation, and the landing order of section 7. Ask whether it is Draft or\nReady.\n\n## 7. Land The Release\n\nOnce OpenVMM CI passed NVX's required jobs on the new head, and only when the\nuser asks:\n\n```console\npython3 scripts\u002Fopenvmm_release.py land --remote REMOTE --old-head OLD_HEAD --new-head NEW_HEAD --prev-release PREV_RELEASE --push\n```\n\nWithout `--push`, it prints the plan. It fetches `feature\u002Fmicrovm\u002Fdev` again\nand stops when the branch moved: carry the new commits onto the release, repeat\nsections 4 to 6, including publication, OpenVMM CI, and the NVX pin, and land\nagain with the new heads. It then fast-forwards the previous release branch to\nthe old head, never by force, so that every revision of the old line that NVX\npinned stays on a branch that `git submodule update` of an older NVX commit can\nfetch; and it moves `feature\u002Fmicrovm\u002Fdev` to the new head with a lease on the\nold one. Each OpenVMM pull request still open against `feature\u002Fmicrovm\u002Fdev`\nthen needs a rebase. The NVX pull request merges through the merge queue once\na maintainer approves it.\n\n## Report\n\nReport the kind and version of the release; the old and new bases and heads;\nthe drops with their upstream pull requests; the conflicts and their\nresolutions; the fixups or folds; the merge and signature checks; the\nequivalence evidence; the per-commit and head validation; the OpenVMM CI runs;\nthe previous release branch's fast-forward and the move of\n`feature\u002Fmicrovm\u002Fdev`; the NVX commits, pull request, and exact-head workflow\nrun; and every blocked or pending gate.\n",{"name":5,"description":7,"argument-hint":45},"[rebase|reorganization] [upstream=main] [Draft|Ready]","dev","683eddaab528d71572503a8c687c124f35d98e10",".github\u002Fskills\u002Fnvx-rebase-openvmm-chain",59,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 02:56:57",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002Fnvx --skill nvx-rebase-openvmm-chain",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002Fnvx --skill nvx-rebase-openvmm-chain",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002Fnvx --skill nvx-rebase-openvmm-chain","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-rebase-openvmm-chain\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fremap.md","REFERENCE","参考文档",1822,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-rebase-openvmm-chain\u002Freferences\u002Fremap.md",[76,103,130,153,175,194],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":40},"01M6WF70QXSEFAVRE1H17HCKKR","nvx-triage-ci-run","Triage a failed, cancelled, or hanging microsoft\u002Fnvx GitHub Actions run: classify supersession and queueing, find the first causal failure for the exact head, reproduce it on the matching platform, and fix it locally without committing. Use for workflow run URLs or IDs, red pull-request checks, runner, matrix, and artifact-handoff failures, and performance-gate or benchmark-host failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-triage-ci-run\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"triage","run","ci","nvx triage ci run","handoff","performance","workflow","benchmark","pull","actions","github actions","ids","fix","runner","artifact","classify","host","URL","matrix","request",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":114,"publishedAt":40},"01M6WF6V0QC9BBS0DW6TB3JQN8","nvx-run-microvm","Boot an NVX microVM with nvx-rs on Linux\u002FKVM, Linux\u002FMSHV, or Windows\u002FWHP, exercise the guest, and debug failed boots. Use for boot smoke tests, guest shell sessions, virtio-fs mounts, networking, kernel command lines, missing boot markers, OpenVMM errors, guest hangs, and benchmark acceptance failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-run-microvm\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[84,31,115,116,117,118,119,120,121,122,123,34,124,125,126,99,127,128,129,24],"nvx run","nvx run microvm","kernel","linux","sessions","smoke tests","windows","kvm","exercise","smoke","local","tests","missing","markers","errors",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":139,"publishedAt":40},"01M6WF6DF1X138HP9B9CQCSRWA","nvx-promote-openvmm-pin","Pin a reviewed OpenVMM revision in NVX: verify its provenance and signature, commit the gitlink and the OpenVMM roadmap mapping, validate the exact pin, and land the OpenVMM pull request by fast-forward. Use for OpenVMM pin updates, clean replacement pull requests, source-equivalence checks, and mapping new chain commits in the OpenVMM upstream roadmap.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-promote-openvmm-pin\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000031","产品经理",[140,37,141,142,143,144,46,145,91,146,38,34,33,32,147,29,28,148,21,149,100,150,151,24,152,102,23],"promote","nvx promote openvmm pin","pull requests","commit","pr","land","provenance","clean","origin","mapping","revision","updates","source",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":40},"01M6WF66SSSZZZDPZEA9TR57SA","nvx-prepare-host","Prepare a local host or a configured SSH host for NVX work: resolve its profile, probe its KVM, MSHV, or WHP backend and checkout, check out the requested revision in a temporary worktree, and stage nvx-rs and the artifacts. Use before running, debugging, or benchmarking NVX on a host, or to diagnose a host's prerequisites.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-prepare-host\u002FSKILL.md",[],[160,99,161,162,163,164,122,165,166,167,168,169,34,170,171,125,172,173,24,174],"prepare","nvx prepare host","benchmarking","diagnose","debugging","artifacts","worktree","ssh","work","check","backend","probe","stage","checkout","running",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":40},"01M6WF60T85KGK0DDB14W1MQYZ","nvx-fix-issue","Fix one microsoft\u002Fnvx issue end to end: reproduce it on the configured hosts, commit signed fixes, open a Ready pull request against dev, and drive CI and review until only a maintainer's approval remains. Use when invoked with an NVX issue number or URL.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-fix-issue\u002FSKILL.md",[],[182,95,183,184,185,143,186,91,85,187,188,33,189,26,100,190,191,192,102,193],"fix issue","issue","nvx fix issue","review","issues","open","only","end","number","hosts","fixes","when",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":40},"01M6WF5V4D4J0MBBMTQTY7P5V2","nvx-collect-benchmarks","Collect fresh NVX benchmark results on a prepared Linux\u002FKVM, Linux\u002FMSHV, or Windows\u002FWHP host with the smoke, CI-equivalent, or canonical profile. Use for acceptance runs, performance suites, p50 collection, benchmark artifacts, and same-host performance comparisons.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-collect-benchmarks\u002FSKILL.md",[],[201,202,203,118,88,121,122,204,165,205,85,206,207,34,124,125,208,99,25,24],"collect","benchmarks","nvx collect benchmarks","nvx benchmark","acceptance","collection","results","fresh"]