How zero-tang/noirvisor works
NoirVisor is a Type-1 AMD64 hypervisor supporting Intel VT-x/EPT and AMD-V/NPT, with a customizable-VM API. The principal boot workflow is firmware or a Windows kernel driver loading the hypervisor, whose entry point selects the processor-specific virtualization backend and subverts the host. Custom VMs are exposed through a separate API surface. The graph preserves the documented IOMMU, ACPI, and disassembly capabilities; unsampled subsystem relationships are omitted rather than inferred.
Main entry points: lib.rs Hypervisor Entry · vt_core/mod.rs Intel VT-x · svm_core/mod.rs AMD-V SVM · main.rs EFI Loader
Components 19
Boot and Interfaces
- EFI Loader
crates/loadefi/src/main.rs - UEFI Runtime Driver
src/booting/uefirtdrv/src/uefihvm.rs - Windows Driver
crates/windrv/src/lib.rs
Hypervisor Backends
- Hypervisor Entry
src/lib.rs - Intel VT-x
src/vt_core/mod.rs - Intel EPT
src/vt_core/ept.rs - AMD-V SVM
src/svm_core/mod.rs - AMD NPT
src/svm_core/npt.rs
Custom Virtualization
- CVM API
crates/nvcvm/src/interface/c_api.rs - CVM x86 State
src/cvm_core/x86/cpuid.rs - Instruction Emulator
src/disasm/emulator.rs - VM Lifecycle
src/cvm_core/x86/mod.rs
Platform Services
- ACPI Tables
src/drv_core/acpi/tables.rs - IOMMU Drivers
src/drv_core/iommu/mod.rs - Hypervisor Calls
src/mshv_core/hvcall.rs
Core Framework
- x86 Framework
src/xpf_core/x86.rs - Memory Allocator
src/xpf_core/allocator.rs
Other components
- UEFI Firmware
- Windows Service
Connections 17
- UEFI Firmware → EFI Loader: boots
README.md - EFI Loader → UEFI Runtime Driver: loads image
crates/loadefi/src/main.rs - Windows Service → Windows Driver: starts driver
README.md - UEFI Runtime Driver → Hypervisor Entry: invokes core
- Windows Driver → Hypervisor Entry: invokes core
- Hypervisor Entry → Intel VT-x: selects backend
src/lib.rs - Hypervisor Entry → AMD-V SVM: selects backend
src/lib.rs - Intel VT-x → Intel EPT: initializes EPT
src/vt_core/mod.rs - AMD-V SVM → AMD NPT: builds NPT
src/svm_core/mod.rs - CVM API → VM Lifecycle: delegates lifecycle
- VM Lifecycle → CVM x86 State: syncs state
src/cvm_core/x86/mod.rs - Instruction Emulator → x86 Framework: uses definitions
src/disasm/emulator.rs - IOMMU Drivers → ACPI Tables: reads tables
src/drv_core/iommu/mod.rs - Intel VT-x → Hypervisor Calls: supports calls
- AMD-V SVM → Hypervisor Calls: supports calls
- Hypervisor Entry → x86 Framework: uses definitions
- Hypervisor Entry → Memory Allocator: uses allocator
src/lib.rs