Custom Multi-layer hypervisor for intel system
Budget / Salary$250–750
TypeFreelance project
LocationRemote
Posted2 hours ago
Develop a custom multi-stage hypervisor architecture for Intel x64 systems using Intel VT-x and Extended Page Tables (EPT).
The system should consist of two primary low-level stages and a Windows-accessible management interface.
Stage 1 — Boot Initialization: A UEFI-compatible boot component initializes the virtualization environment, establishes the required memory isolation and security configurations, and prepares the resident hypervisor before Windows starts.
Stage 2 — Resident Hypervisor: A persistent virtualization component operates independently of ordinary Windows user-mode processes. It provides controlled physical memory inspection, memory translation, VM-exit handling, and a communication interface for authorized client applications.
Stage 3 — Windows Management Menu: Once Windows starts, a graphical management application can connect to the resident hypervisor through a defined communication interface. This application acts as the user-facing control panel, allowing authorized operations, displaying diagnostic information, and interacting with services maintained by the hypervisor.
The architecture should separate boot initialization, privileged virtualization functionality, and user-interface operations. The Windows management application should not need to contain or reinitialize the hypervisor itself.
Primary Objective: Create a stable, modular, multi-stage virtualization system where an initial boot component establishes the environment, a resident hypervisor provides privileged functionality, and a Windows-accessible menu communicates with those services through a controlled interface.
The system should consist of two primary low-level stages and a Windows-accessible management interface.
Stage 1 — Boot Initialization: A UEFI-compatible boot component initializes the virtualization environment, establishes the required memory isolation and security configurations, and prepares the resident hypervisor before Windows starts.
Stage 2 — Resident Hypervisor: A persistent virtualization component operates independently of ordinary Windows user-mode processes. It provides controlled physical memory inspection, memory translation, VM-exit handling, and a communication interface for authorized client applications.
Stage 3 — Windows Management Menu: Once Windows starts, a graphical management application can connect to the resident hypervisor through a defined communication interface. This application acts as the user-facing control panel, allowing authorized operations, displaying diagnostic information, and interacting with services maintained by the hypervisor.
The architecture should separate boot initialization, privileged virtualization functionality, and user-interface operations. The Windows management application should not need to contain or reinitialize the hypervisor itself.
Primary Objective: Create a stable, modular, multi-stage virtualization system where an initial boot component establishes the environment, a resident hypervisor provides privileged functionality, and a Windows-accessible menu communicates with those services through a controlled interface.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.