[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69BX123NC683P7MH2Y7B08K":3,"skill-same:01M69BX123NC683P7MH2Y7B08K":65},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M69BX123NC683P7MH2Y7B08K","vmm-tests",null,"Run VMM tests locally with cargo xflowey vmm-tests-run. Load when running or debugging VMM tests, or when you need to understand the petri test framework, artifact handling, or cross-compilation for VMM tests.","microsoft\u002Fopenvmm","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69BWP49YBS03WTCPVZB5TY8",1972,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvmm-tests\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"vmm","vmm tests","tests","running","test","when","for","load","you","with","understand","cargo","artifact","framework","run","debugging","test framework","2026-11-10 10:12:30",false,"---\nname: vmm-tests\ndescription: \"Run VMM tests locally with cargo xflowey vmm-tests-run. Load when running or debugging VMM tests, or when you need to understand the petri test framework, artifact handling, or cross-compilation for VMM tests.\"\n---\n\n# Running VMM Tests\n\nVMM tests boot full virtual machines and validate behavior. They live in\n`vmm_tests\u002Fvmm_tests\u002Ftests\u002Ftests\u002F` and use the `petri` test framework.\n\n**Always use `cargo xflowey vmm-tests-run`** — never raw `cargo nextest run -p\nvmm_tests`. The xflowey command handles artifact discovery, dependency\nbuilding, and test execution automatically.\n\n## Quick Start\n\n```bash\n# Run a specific test\ncargo xflowey vmm-tests-run --filter \"test(my_test_name)\"\n\n# Run all tests matching a prefix\ncargo xflowey vmm-tests-run --filter \"test(\u002F^boot_\u002F)\"\n\n# Run all tests (rarely needed locally)\ncargo xflowey vmm-tests-run --filter \"all()\"\n```\n\nOmitting `--filter` selects all tests. Use an explicit selection so the\ncommand's scope is clear.\n\n## Output Directory\n\nUsually you don't need `--dir` — it defaults to `target\u002Fvmm_tests`. When\ncross-compiling for Windows from WSL2, `--dir` on the Windows filesystem (e.g.,\n`--dir \u002Fmnt\u002Fd\u002Fvmm_tests`) is required **only** when the selected tests use disk\nimages that need a Windows filesystem: **Hyper-V tests**, or tests using **VHDX\n\u002F dynamic VHD1** images. For everything else (streamed disks, or plain fixed\nVHD1 \u002F VMGS \u002F ISO files), the default WSL-side directory works. `vmm-tests-run`\ndetects this and errors with a clear message if `--dir` is required.\n\n## Filter Syntax\n\nFilters use [nextest filter expressions](https:\u002F\u002Fnexte.st\u002Fdocs\u002Ffiltersets\u002F):\n\n| Expression | Matches |\n|-----------|---------|\n| `test(foo)` | Tests with `foo` in the name |\n| `test(\u002F^boot_\u002F)` | Tests starting with `boot_` (regex) |\n| `test(foo) & !test(hyperv)` | `foo` tests excluding Hyper-V variants |\n| `all()` | Everything |\n\n## Platform Targeting\n\nBy default, tests build for the current host. Use `--target` for\ncross-compilation:\n\n```bash\n# Cross-compile and run Windows tests from WSL2\ncargo xflowey vmm-tests-run --target windows-x64 --filter \"test(my_test_name)\"\n```\n\n| Target | Description |\n|--------|-------------|\n| `windows-x64` | Windows x86_64 (Hyper-V \u002F WHP) |\n| `windows-aarch64` | Windows ARM64 (Hyper-V \u002F WHP) |\n| `linux-x64` | Linux x86_64 |\n\n**Windows from WSL2**: Cross-compilation setup is required first — see\n`Guide\u002Fsrc\u002Fdev_guide\u002Fgetting_started\u002Fcross_compile.md`.\n\n## Artifact Handling (Lazy Fetch)\n\nBy default, disk images (VHDs\u002FISOs) are streamed on demand via HTTP with local\nSQLite caching. This avoids multi-GB upfront downloads.\n\n- `--no-lazy-fetch` — download all images upfront instead of streaming\n- Lazy fetch is automatically disabled for Hyper-V tests (they need local files)\n- `--skip-vhd-prompt` — skip interactive VHD download prompts (useful for\n  automation)\n\n## Viewing Logs\n\nTest output (petri logs, guest serial, etc.) is shown by default on failure.\nFor full OpenVMM tracing, set the `OPENVMM_LOG` environment variable:\n\n```bash\nOPENVMM_LOG=trace cargo xflowey vmm-tests-run --filter \"test(foo)\"\n```\n\n## Other Useful Flags\n\n| Flag | Purpose |\n|------|---------|\n| `--release` | Release build (default: debug) |\n| `--build-only` | Build without running |\n| `--verbose` | Verbose cargo output |\n| `--install-missing-deps` | Auto-install missing system dependencies |\n| `--custom-uefi-firmware \u003CPATH>` | Use a custom UEFI firmware (MSVM.fd) |\n| `--custom-kernel \u003CPATH>` | Use a custom kernel image |\n\nRun `cargo xflowey vmm-tests-run --help` for the full option list.\n\n## Common Pitfalls\n\n- **Don't use `cargo nextest run -p vmm_tests` directly** — artifacts won't\n  be present and tests will fail with missing-artifact errors.\n- **Hyper-V tests** — require Hyper-V Administrators group membership and\n  disable lazy fetch automatically.\n- **CI failures** — use the `openvmm-ci-investigation` skill to diagnose\n  failing VMM tests in CI, not this workflow.\n","# Running VMM Tests\n\nVMM tests boot full virtual machines and validate behavior. They live in\n`vmm_tests\u002Fvmm_tests\u002Ftests\u002Ftests\u002F` and use the `petri` test framework.\n\n**Always use `cargo xflowey vmm-tests-run`** — never raw `cargo nextest run -p\nvmm_tests`. The xflowey command handles artifact discovery, dependency\nbuilding, and test execution automatically.\n\n## Quick Start\n\n```bash\n# Run a specific test\ncargo xflowey vmm-tests-run --filter \"test(my_test_name)\"\n\n# Run all tests matching a prefix\ncargo xflowey vmm-tests-run --filter \"test(\u002F^boot_\u002F)\"\n\n# Run all tests (rarely needed locally)\ncargo xflowey vmm-tests-run --filter \"all()\"\n```\n\nOmitting `--filter` selects all tests. Use an explicit selection so the\ncommand's scope is clear.\n\n## Output Directory\n\nUsually you don't need `--dir` — it defaults to `target\u002Fvmm_tests`. When\ncross-compiling for Windows from WSL2, `--dir` on the Windows filesystem (e.g.,\n`--dir \u002Fmnt\u002Fd\u002Fvmm_tests`) is required **only** when the selected tests use disk\nimages that need a Windows filesystem: **Hyper-V tests**, or tests using **VHDX\n\u002F dynamic VHD1** images. For everything else (streamed disks, or plain fixed\nVHD1 \u002F VMGS \u002F ISO files), the default WSL-side directory works. `vmm-tests-run`\ndetects this and errors with a clear message if `--dir` is required.\n\n## Filter Syntax\n\nFilters use [nextest filter expressions](https:\u002F\u002Fnexte.st\u002Fdocs\u002Ffiltersets\u002F):\n\n| Expression | Matches |\n|-----------|---------|\n| `test(foo)` | Tests with `foo` in the name |\n| `test(\u002F^boot_\u002F)` | Tests starting with `boot_` (regex) |\n| `test(foo) & !test(hyperv)` | `foo` tests excluding Hyper-V variants |\n| `all()` | Everything |\n\n## Platform Targeting\n\nBy default, tests build for the current host. Use `--target` for\ncross-compilation:\n\n```bash\n# Cross-compile and run Windows tests from WSL2\ncargo xflowey vmm-tests-run --target windows-x64 --filter \"test(my_test_name)\"\n```\n\n| Target | Description |\n|--------|-------------|\n| `windows-x64` | Windows x86_64 (Hyper-V \u002F WHP) |\n| `windows-aarch64` | Windows ARM64 (Hyper-V \u002F WHP) |\n| `linux-x64` | Linux x86_64 |\n\n**Windows from WSL2**: Cross-compilation setup is required first — see\n`Guide\u002Fsrc\u002Fdev_guide\u002Fgetting_started\u002Fcross_compile.md`.\n\n## Artifact Handling (Lazy Fetch)\n\nBy default, disk images (VHDs\u002FISOs) are streamed on demand via HTTP with local\nSQLite caching. This avoids multi-GB upfront downloads.\n\n- `--no-lazy-fetch` — download all images upfront instead of streaming\n- Lazy fetch is automatically disabled for Hyper-V tests (they need local files)\n- `--skip-vhd-prompt` — skip interactive VHD download prompts (useful for\n  automation)\n\n## Viewing Logs\n\nTest output (petri logs, guest serial, etc.) is shown by default on failure.\nFor full OpenVMM tracing, set the `OPENVMM_LOG` environment variable:\n\n```bash\nOPENVMM_LOG=trace cargo xflowey vmm-tests-run --filter \"test(foo)\"\n```\n\n## Other Useful Flags\n\n| Flag | Purpose |\n|------|---------|\n| `--release` | Release build (default: debug) |\n| `--build-only` | Build without running |\n| `--verbose` | Verbose cargo output |\n| `--install-missing-deps` | Auto-install missing system dependencies |\n| `--custom-uefi-firmware \u003CPATH>` | Use a custom UEFI firmware (MSVM.fd) |\n| `--custom-kernel \u003CPATH>` | Use a custom kernel image |\n\nRun `cargo xflowey vmm-tests-run --help` for the full option list.\n\n## Common Pitfalls\n\n- **Don't use `cargo nextest run -p vmm_tests` directly** — artifacts won't\n  be present and tests will fail with missing-artifact errors.\n- **Hyper-V tests** — require Hyper-V Administrators group membership and\n  disable lazy fetch automatically.\n- **CI failures** — use the `openvmm-ci-investigation` skill to diagnose\n  failing VMM tests in CI, not this workflow.\n",{"name":5,"description":7},"main","ebcd3302222379403963385f25538e35afcd3222",".github\u002Fskills\u002Fvmm-tests",277,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm","http:\u002F\u002Fopenvmm.dev\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 02:18:15",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add microsoft\u002Fopenvmm --skill vmm-tests",{"tool":57,"command":58},"bunx","bunx skills add microsoft\u002Fopenvmm --skill vmm-tests",{"tool":60,"command":61},"pnpm","pnpm dlx skills add microsoft\u002Fopenvmm --skill vmm-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvmm-tests\u002FSKILL.md",true,[],[66,86,111,131],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":36},"01M69BWYZCDJJASP457EK9EPWB","update-mu-msvm","Update OpenVMM UEFI firmware to the latest published microsoft\u002Fmu_msvm release. Use when updating mu_msvm, bumping the UEFI dependency, refreshing firmware Nix hashes, or preparing the firmware ingestion pull request.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fupdate-mu-msvm\u002FSKILL.md",[],[73,74,75,24,76,77,78,79,80,81,82,83,84,9,85],"update mu msvm","update","pull","request","latest","ingestion","dependency","use","firmware","UEFI","release","pull request","nix",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":36},"01M69BWX0NY6SCW7H5EMVVC7R1","openvmm-ci-investigation","Investigate CI failures on OpenVMM PRs. Load when a PR has failing CI checks, you need to download and analyze test artifacts, or you need to diagnose build, fmt, clippy, or VMM test failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fopenvmm-ci-investigation\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[98,99,100,101,27,102,103,104,105,106,19,107,108,26,109,24,110,23],"openvmm ci investigation","ci","investigation","download","clippy","build","analyze","prs","investigate","artifacts","pr","failing","diagnose",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":36},"01M69BWVDKTXGYTGQ5AGFBB8AQ","guide-maintenance","Maintain the OpenVMM Guide. Load when: (1) adding, removing, or moving Guide pages, (2) adding new device crates or adding or changing CLI interfaces that need doc coverage, or (3) auditing Guide freshness against code changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fguide-maintenance\u002FSKILL.md",[],[118,119,120,121,122,123,124,125,126,127,128,129,26,130,24],"guide maintenance","maintenance","guide","new","cli","code","doc","coverage","doc coverage","device","maintain","pages","changes",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":142,"publishedAt":36},"01M69BWS8XZJH7G018FXMXR1QV","fuzzing","Run, optimize, and debug OpenVMM fuzzers. Covers cargo-fuzz targets, crash reproduction, lldb debugging, code coverage analysis, entropy optimization, and multi-target parallel campaigns.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fopenvmm\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffuzzing\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[133,143,144,145,34,33,123,146,147,148,149,125,150,151,152,153,30,154,155,156],"multi","coverage analysis","debug","Optimization","entropy","analysis","parallel","crash","optimize","campaigns","code coverage","targets","lldb","target"]