[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WF66SSSZZZDPZEA9TR57SA":3,"skill-same:01M6WF66SSSZZZDPZEA9TR57SA":68},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6WF66SSSZZZDPZEA9TR57SA","nvx-prepare-host",null,"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.","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-prepare-host\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"nvx prepare host","host","prepare","use","running","for","checkout","stage","local","probe","backend","check","work","ssh","worktree","artifacts","kvm","debugging","diagnose","benchmarking","2026-11-10 10:12:30",false,"---\nname: nvx-prepare-host\ndescription: \"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.\"\nargument-hint: \"[local|host-profile] [revision]\"\n---\n\n# Prepare An NVX Host\n\nEstablish a verified execution context, report it, and stop; then continue\nwith [nvx-run-microvm](..\u002Fnvx-run-microvm\u002FSKILL.md) or\n[nvx-collect-benchmarks](..\u002Fnvx-collect-benchmarks\u002FSKILL.md). Run the commands\nfrom the NVX checkout. They use `python3`; use `python` on Windows.\n\n## 1. Choose The Host\n\nWork locally when the user asks for it or the local host provides the backend.\nOtherwise, list the profiles of the developer's inventory, the ignored\n`.nvx-hosts.json` that [Setup](..\u002F..\u002F..\u002Fdoc\u002Fsetup.md#remote-agent-hosts) describes,\nwhich the tool reads from the main worktree when you work in a linked one:\n\n```console\npython3 scripts\u002Fnvx_hosts.py list\n```\n\n- When `remote_enabled` is `false`, no remote host is configured: say so and\n  work locally.\n- Use the profile that the user or the calling skill named, or ask the user to\n  choose one. `python3 scripts\u002Fnvx_hosts.py show PROFILE` returns its\n  `ssh_target`, `backend`, `platform`, `host_type`, and `remote_repo`, which\n  are authoritative: never connect to a target outside the inventory, override\n  its backend, or infer bare metal or a virtual machine from probes. When\n  `remote_repo` is `null`, ask for the checkout's absolute path, and pass it\n  as `--cwd`.\n\n## 2. Safety\n\n- Never ask for or handle passwords, keys, tokens, or passphrases; when SSH\n  asks for one, the user types it in the terminal. Never disable host-key\n  checking, and stop on a changed host key.\n- Never reset, clean, switch, pull, overwrite, or update submodules in a dirty\n  checkout. Test another revision in a temporary worktree, and ask before\n  copying uncommitted files to a host.\n- Never install packages, enable Windows features, change device permissions,\n  edit `sudoers`, load kernel modules, reboot, or use `sudo` to get past an\n  access check without the user's approval.\n- Select one backend explicitly, never `both`.\n- Never terminate an OpenVMM process that this session did not start.\n\n## 3. Probe\n\nProbe the local host or the profile's checkout:\n\n```console\npython3 scripts\u002Fhost_probe.py --backend BACKEND\npython3 scripts\u002Fnvx_hosts.py probe PROFILE\n```\n\nBoth report the OS, Python, `HEAD`, the dirty state, the OpenVMM pin and\ncheckout, `nvx.py verify`, the backend's access (`\u002Fdev\u002Fkvm`, `\u002Fdev\u002Fmshv`, or\nWHP), `nvx-rs` and the artifacts, and running OpenVMM processes. On a host,\n`nvx_hosts.py` runs this checkout's copy of the probe, so the host's checkout\nmay predate it. Report a failed access check as the probe states it. When KVM\nand MSHV are both usable and no backend was named, ask which one to use. A\nsmoke run is the definitive WHP check.\n\n## 4. Revision\n\nUse the checkout as it is only when it is clean and at the requested revision,\nor when the user approves. To test another revision, such as a branch that you\npushed, without touching the checkout, add a temporary worktree, which checks\nthe remotes, fetches the branch, and checks out the worktree's OpenVMM pin:\n\n```console\npython3 scripts\u002Fnvx_hosts.py worktree PROFILE -- add FETCH_HEAD --fetch BRANCH\n```\n\nOn a host, this runs this checkout's `host_worktree.py`, as `probe` does;\nlocally, run `python3 scripts\u002Fhost_worktree.py add ...` directly. Work in the\nworktree that it prints, passing it as `--cwd` on a remote host, and remove it\nat the end with the same command, `remove PATH` taking the place of `add ...`.\n\n## 5. Artifacts\n\nBuild `nvx-rs`, which runs microVMs and sandboxes and downloads releases, from\nthe checkout's root, and again after `nvx-rs` changes; no package contains it:\n\n```console\ncargo build --release --locked --features cli --manifest-path nvx-rs\u002FCargo.toml --target-dir nvx-rs\u002Ftarget\n```\n\nThen stage the artifacts that the task's provenance calls for:\n\n- Packaged: `nvx-rs\u002Ftarget\u002Frelease\u002Fnvx-rs download --hypervisor BACKEND`\n  installs the release built from `HEAD`, or from its nearest released\n  first-parent ancestor; report that release. It replaces every artifact, so\n  never run it over artifacts that the user wants to keep.\n- Changed inputs: the matching `nvx.py build-guest`, `build-openvmm`, or\n  `build` command of [Build](..\u002F..\u002F..\u002Fdoc\u002Fbuild.md).\n- Changes to the coordinator only: the matching release artifacts in place,\n  with their provenance reported.\n- The public sandbox scenarios of `test-microvm` also need\n  `build\u002Fubuntu-smoke-scratch.ext4`, which `download` installs from the\n  releases that ship it. For an older release, format it on a Linux host with\n  `python3 scripts\u002Fnvx.py build-scratch-template` and copy it to a Windows\n  host.\n\nA run downloads a release only into a checkout that holds no artifacts;\n`NVX_AUTO_DOWNLOAD=0` turns that off. Check the generated command and its files\nwithout starting a VM:\n\n```console\nnvx-rs\u002Ftarget\u002Frelease\u002Fnvx-rs run --hypervisor BACKEND --dry-run\n```\n\n## Handoff\n\nReport the host or local execution, the checkout and any temporary worktree,\nthe OS, backend, platform, and host type, the commit and dirty state, the\nartifact source and the commands that staged it, the dry run's result, any\nrunning OpenVMM process, and every privilege or platform limitation. For\ninteractive work on a remote host, open `ssh -tt \u003Cssh_target>` and change to\nthat directory.\n","# Prepare An NVX Host\n\nEstablish a verified execution context, report it, and stop; then continue\nwith [nvx-run-microvm](..\u002Fnvx-run-microvm\u002FSKILL.md) or\n[nvx-collect-benchmarks](..\u002Fnvx-collect-benchmarks\u002FSKILL.md). Run the commands\nfrom the NVX checkout. They use `python3`; use `python` on Windows.\n\n## 1. Choose The Host\n\nWork locally when the user asks for it or the local host provides the backend.\nOtherwise, list the profiles of the developer's inventory, the ignored\n`.nvx-hosts.json` that [Setup](..\u002F..\u002F..\u002Fdoc\u002Fsetup.md#remote-agent-hosts) describes,\nwhich the tool reads from the main worktree when you work in a linked one:\n\n```console\npython3 scripts\u002Fnvx_hosts.py list\n```\n\n- When `remote_enabled` is `false`, no remote host is configured: say so and\n  work locally.\n- Use the profile that the user or the calling skill named, or ask the user to\n  choose one. `python3 scripts\u002Fnvx_hosts.py show PROFILE` returns its\n  `ssh_target`, `backend`, `platform`, `host_type`, and `remote_repo`, which\n  are authoritative: never connect to a target outside the inventory, override\n  its backend, or infer bare metal or a virtual machine from probes. When\n  `remote_repo` is `null`, ask for the checkout's absolute path, and pass it\n  as `--cwd`.\n\n## 2. Safety\n\n- Never ask for or handle passwords, keys, tokens, or passphrases; when SSH\n  asks for one, the user types it in the terminal. Never disable host-key\n  checking, and stop on a changed host key.\n- Never reset, clean, switch, pull, overwrite, or update submodules in a dirty\n  checkout. Test another revision in a temporary worktree, and ask before\n  copying uncommitted files to a host.\n- Never install packages, enable Windows features, change device permissions,\n  edit `sudoers`, load kernel modules, reboot, or use `sudo` to get past an\n  access check without the user's approval.\n- Select one backend explicitly, never `both`.\n- Never terminate an OpenVMM process that this session did not start.\n\n## 3. Probe\n\nProbe the local host or the profile's checkout:\n\n```console\npython3 scripts\u002Fhost_probe.py --backend BACKEND\npython3 scripts\u002Fnvx_hosts.py probe PROFILE\n```\n\nBoth report the OS, Python, `HEAD`, the dirty state, the OpenVMM pin and\ncheckout, `nvx.py verify`, the backend's access (`\u002Fdev\u002Fkvm`, `\u002Fdev\u002Fmshv`, or\nWHP), `nvx-rs` and the artifacts, and running OpenVMM processes. On a host,\n`nvx_hosts.py` runs this checkout's copy of the probe, so the host's checkout\nmay predate it. Report a failed access check as the probe states it. When KVM\nand MSHV are both usable and no backend was named, ask which one to use. A\nsmoke run is the definitive WHP check.\n\n## 4. Revision\n\nUse the checkout as it is only when it is clean and at the requested revision,\nor when the user approves. To test another revision, such as a branch that you\npushed, without touching the checkout, add a temporary worktree, which checks\nthe remotes, fetches the branch, and checks out the worktree's OpenVMM pin:\n\n```console\npython3 scripts\u002Fnvx_hosts.py worktree PROFILE -- add FETCH_HEAD --fetch BRANCH\n```\n\nOn a host, this runs this checkout's `host_worktree.py`, as `probe` does;\nlocally, run `python3 scripts\u002Fhost_worktree.py add ...` directly. Work in the\nworktree that it prints, passing it as `--cwd` on a remote host, and remove it\nat the end with the same command, `remove PATH` taking the place of `add ...`.\n\n## 5. Artifacts\n\nBuild `nvx-rs`, which runs microVMs and sandboxes and downloads releases, from\nthe checkout's root, and again after `nvx-rs` changes; no package contains it:\n\n```console\ncargo build --release --locked --features cli --manifest-path nvx-rs\u002FCargo.toml --target-dir nvx-rs\u002Ftarget\n```\n\nThen stage the artifacts that the task's provenance calls for:\n\n- Packaged: `nvx-rs\u002Ftarget\u002Frelease\u002Fnvx-rs download --hypervisor BACKEND`\n  installs the release built from `HEAD`, or from its nearest released\n  first-parent ancestor; report that release. It replaces every artifact, so\n  never run it over artifacts that the user wants to keep.\n- Changed inputs: the matching `nvx.py build-guest`, `build-openvmm`, or\n  `build` command of [Build](..\u002F..\u002F..\u002Fdoc\u002Fbuild.md).\n- Changes to the coordinator only: the matching release artifacts in place,\n  with their provenance reported.\n- The public sandbox scenarios of `test-microvm` also need\n  `build\u002Fubuntu-smoke-scratch.ext4`, which `download` installs from the\n  releases that ship it. For an older release, format it on a Linux host with\n  `python3 scripts\u002Fnvx.py build-scratch-template` and copy it to a Windows\n  host.\n\nA run downloads a release only into a checkout that holds no artifacts;\n`NVX_AUTO_DOWNLOAD=0` turns that off. Check the generated command and its files\nwithout starting a VM:\n\n```console\nnvx-rs\u002Ftarget\u002Frelease\u002Fnvx-rs run --hypervisor BACKEND --dry-run\n```\n\n## Handoff\n\nReport the host or local execution, the checkout and any temporary worktree,\nthe OS, backend, platform, and host type, the commit and dirty state, the\nartifact source and the commands that staged it, the dry run's result, any\nrunning OpenVMM process, and every privilege or platform limitation. For\ninteractive work on a remote host, open `ssh -tt \u003Cssh_target>` and change to\nthat directory.\n",{"name":5,"description":7,"argument-hint":44},"[local|host-profile] [revision]","dev","683eddaab528d71572503a8c687c124f35d98e10",".github\u002Fskills\u002Fnvx-prepare-host",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add microsoft\u002Fnvx --skill nvx-prepare-host",{"tool":60,"command":61},"bunx","bunx skills add microsoft\u002Fnvx --skill nvx-prepare-host",{"tool":63,"command":64},"pnpm","pnpm dlx skills add microsoft\u002Fnvx --skill nvx-prepare-host","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-prepare-host\u002FSKILL.md",true,[],[69,95,121,146,169,188],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":39},"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",[],[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,20,92,93,94],"triage","run","ci","nvx triage ci run","handoff","performance","workflow","benchmark","pull","actions","github actions","ids","fix","runner","artifact","classify","URL","matrix","request",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":106,"publishedAt":39},"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",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[77,107,108,109,110,111,112,113,114,35,115,22,116,27,117,20,118,119,120,24],"microvm","nvx run","nvx run microvm","kernel","linux","sessions","smoke tests","windows","exercise","smoke","tests","missing","markers","errors",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":39},"01M6WF6MVTYEFTS42E2JF5Y28G","nvx-rebase-openvmm-chain","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fnvx\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fnvx-rebase-openvmm-chain\u002FSKILL.md",[],[128,129,130,107,131,132,133,134,135,22,136,137,138,139,140,141,142,143,144,24,145],"rebase","chain","nvx rebase openvmm chain","publish","commits","pin","branch","landing","ready","roadmap","conflicts","main","upstream","draft","feature","as","with","new",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":39},"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",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000031","产品经理",[156,133,157,158,159,160,45,161,84,162,132,22,136,137,163,140,141,164,129,165,92,166,167,24,168,94,145],"promote","nvx promote openvmm pin","pull requests","commit","pr","land","provenance","clean","origin","mapping","revision","updates","source",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":39},"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",[],[176,88,177,178,179,159,180,84,78,181,182,136,183,143,92,184,185,186,94,187],"fix issue","issue","nvx fix issue","review","issues","open","only","end","number","hosts","fixes","when",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":39},"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",[],[195,196,197,111,81,114,35,198,34,199,78,200,201,22,116,27,202,20,144,24],"collect","benchmarks","nvx collect benchmarks","nvx benchmark","acceptance","collection","results","fresh"]