Diagnose Hyper-V architecture, nested virtualization, WSL2 plumbing, and VBS security boundaries.
npx skills add https://github.com/psmfd/pi-config --skill hyperv-expert-psmfd
Please help me install this Agent Skill. Skill: hyperv-expert Source: https://github.com/psmfd/pi-config/tree/main/agent/skills/hyperv-expert Command: npx skills add https://github.com/psmfd/pi-config --skill hyperv-expert-psmfd
Enable-VMNestedVirtualization cmdlet, conflating the Hyper-V role with the VirtualMachinePlatform feature, and nested KVM silently blocked by VBS/HVCI. This Skill provides a read-only reference that resolves these issues with correct cmdlets, feature names, and verification recipes sourced from Microsoft Learn. ## Core Features & Use Cases - Nested virtualization enablement: Correct per-VM setup via Set-VMProcessor -ExposeVirtualizationExtensions $true, including CPU prerequisites and the stopped-VM requirement. - Feature disambiguation: Clear separation of Microsoft-Hyper-V-All, HypervisorPlatform (WHPX), and VirtualMachinePlatform (the WSL2 substrate), with DISM commands to query and enable each. - VBS/HVCI diagnostics: Win32_DeviceGuard queries to detect when Virtualization-Based Security suppresses an L2 hypervisor such as KVM inside WSL2. - Use Case: A developer finds /dev/kvm missing inside WSL2 on an Azure VM. The Skill walks through checking .wslconfig nestedVirtualization, the per-VM exposure flag, and VBS runtime state to pinpoint the blocker. ## Quick Start Ask the hyperv-expert subagent why nested KVM is unavailable inside your WSL2 distro on a Windows host and request the verification commands to run.High-intent search queries and answers about installing and using this skill.
Stop the L1 VM, then run Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $true. The host CPU needs Intel VT-x with EPT or AMD-V with RVI, and the widely cited Enable-VMNestedVirtualization cmdlet does not exist.
Microsoft-Hyper-V-All installs the full Type-1 hypervisor and management tools, HypervisorPlatform provides the WHPX API for third-party accelerators like QEMU, and VirtualMachinePlatform is the lightweight substrate WSL2 uses. WSL2 needs only VirtualMachinePlatform, not the full Hyper-V role.
VBS, HVCI, or Credential Guard running in the L1 guest consumes the virtualization extensions, blocking any L2 hypervisor. Check with Get-CimInstance Win32_DeviceGuard; VirtualizationBasedSecurityStatus = 2 means VBS is active and suppressing KVM.
No. WSL2 runs on the VirtualMachinePlatform optional feature, which is separate from Microsoft-Hyper-V-All. Its lightweight utility VM does not appear in Get-VM and is not managed through Hyper-V cmdlets.
No. Microsoft-hosted windows-latest, windows-2022, and windows-2019 runners do not expose nested virtualization. Use self-hosted runners on capable hardware or Azure Dv3/Ev3 and later VM families, or switch to ubuntu-latest which exposes /dev/kvm.
clfigueiredoDiagnose, configure, and operate Hyper-V VMs, switches, storage, and clusters via PowerShell.
bitan-delAutomate host security hardening and risk-tolerance configuration for Gods Eye deployments.
Greg-T8Automate Active Directory lab creation on Hyper-V with Terraform.
aspenkitExecutes Claude/Codex prompts via CLI with stream-json output parsing and skill file generation.