Custom Multi-layer hypervisor for intel system

$250-750 USD

Posted 1 minute ago

•

Ends in 6 days

$250-750 USD

Paid on delivery

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.

Project ID: 40816273

About the project

11 proposals

Open for bidding

Remote project

Active 13 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

11 freelancers are bidding on average $517 USD for this job

User Avatar
Flag of UKRAINE

Hello, This project’s key challenge is keeping UEFI initialization, the resident VT-x/EPT layer, and the Windows control application strictly separated while preserving reliable communication and safe recovery. I would begin with a documented architecture and lab-only proof of concept covering VMX lifecycle, EPT setup, VM-exit routing, and a narrowly scoped authenticated IPC boundary. My background includes low-level full-stack systems, Node.js/Python services, cloud deployments, and automation workflows. For this work, I would prioritize signed, authorized components, explicit state transitions, diagnostics, and rollback-friendly testing rather than coupling hypervisor initialization to the Windows UI. Within 7 days, I can deliver the first working milestone: architecture specification, build layout, boot-to-resident initialization skeleton, management-interface contract, and validation plan for an authorized test environment. Best regards, Bohdan

User Avatar
Flag of INDIA

Hello Sir, I can develop a custom multi-stage hypervisor architecture for Intel x64 systems, utilizing Intel VT-x and Extended Page Tables. My approach will involve creating a UEFI-compatible boot component for initialization, a persistent resident hypervisor for privileged operations, and a Windows management interface for user interactions. I will ensure modularity and stability throughout the system. I'm ready to start right away. Could you clarify any specific security requirements for the hypervisor? Thanks, Deepak

User Avatar
Flag of UNITED STATES

Your project calls for careful separation between privileged infrastructure and a controlled Windows-facing interface, and software architecture is my core skill. I design modular systems with clear boundaries between initialization, backend services, communication layers, and management applications, which aligns directly with your staged hypervisor architecture. My full-stack background covers backend APIs, microservices, Python, FastAPI, Django, JavaScript/TypeScript, React, and scalable deployment practices. This is especially relevant to building the Windows-accessible management layer and a well-defined interface for authorized interaction with resident services, while keeping the UI separate from low-level virtualization functionality. I also focus on clean, maintainable code and reliable system organization across the full development lifecycle. I would be glad to contribute my architecture and systems-integration expertise to this project and help shape a robust, modular design for the multi-stage platform.

User Avatar
Flag of UNITED STATES

Hello, My strength is software architecture: I focus on separating complex systems into clear, maintainable components with well-defined interfaces. That aligns directly with your need for distinct boot initialization, a resident virtualization layer, and a Windows management application rather than a monolithic tool. I can contribute architectural structure for the overall multi-stage design, including boundaries between privileged services and user-facing operations, communication contracts, lifecycle responsibilities, and diagnostic integration. My background emphasizes organized, buildable solutions and coordination between system components, which is important for maintaining stability across the UEFI, resident hypervisor, and Windows layers. I would be pleased to apply my software architecture expertise to help shape this modular system and its management interface. Thanks!

User Avatar
Flag of UKRAINE

Hi there, You’re looking for a stable, modular, multi-stage virtualization stack on Intel x64 (VT-x + EPT) with a UEFI boot initializer, a persistent resident hypervisor, and a Windows-accessible management UI that communicates via a controlled interface. As a Full Stack Developer with 10+ years of experience in building secure, layered systems (including low-level integration and service-oriented interfaces), I’ll structure the architecture into clear components: Stage 1 (UEFI init, security + memory isolation), Stage 2 (resident VT-x/EPT engine with VM-exit handling and safe physical memory inspection), and Stage 3 (Windows GUI that talks to the hypervisor through an explicit, permissioned communication boundary). This separation keeps the UI independent from hypervisor re-initialization while improving reliability and testability. Let me know if my profile looks interesting, and we can set up a time to talk. Best regards, Vadym P.-

User Avatar
Flag of SOUTH AFRICA

### Project Bid Proposal Hi there, we might be new to the platform but I'd love to share some relevant examples. Your project on developing a custom multi-stage hypervisor architecture for Intel x64 systems sounds right up our alley, and we would love to exceed your expectations. I understand you need a robust UEFI-compatible boot component to initialize the virtualization environment while ensuring memory isolation and security configurations. Our expertise in designing reliable multi-stage systems will ensure a polished, seamless integration of the boot initialization and resident hypervisor. While we might be new to Freelancer, we have over nine years of experience off-site and multiple 5-star reviews on similar projects. We rank in the top 1% among 75 million users. I truly appreciate you taking your time to review our proposal, and I would love to discuss this project more. Kind regards, Trichelle. Client name is and my name is Trich123.

User Avatar
Flag of UNITED KINGDOM

Hello! I've reviewed your project requirements, and they closely match a project I previously built for a client. The main similarities are low-level system architecture, C/C++ development, memory management, modular system components, and Windows integration. The main difference is the multi-stage UEFI boot architecture with Intel VT-x and EPT. I've already looked into the implementation approach. My proposed solution is to separate the UEFI initialization component, resident hypervisor, and Windows management application into independent modules, using C/C++, Intel VMX instructions, EPT, VM-exit handling, and a controlled communication interface. To implement this properly, I'll need your target CPU models, UEFI/firmware requirements, Windows versions, hardware access, and detailed specifications for authorized memory operations and communication protocols. I'm happy to discuss the technical details and clarify the approach before getting started. Looking forward to hearing from you!

User Avatar
Flag of UNITED STATES

Your project requires careful separation between boot initialization, resident privileged services, and a Windows management layer—an architecture-focused approach that matches my Software Architecture expertise. I specialize in designing scalable, modular systems with clear boundaries between components, secure APIs, and maintainable interfaces. My background in backend and full-stack engineering includes Python, FastAPI, Node.js, REST APIs, database design, microservices, Docker, Kubernetes, and cloud architecture. These skills are directly relevant to structuring the Windows-accessible management application and its controlled communication layer, while keeping the overall system modular and service-oriented. I also emphasize clean, maintainable code and security throughout the design. I would be glad to contribute my architecture and systems engineering skills to this multi-stage Intel virtualization project and help shape a robust, maintainable solution.

User Avatar
Flag of INDIA

Hello, You're looking for a multi-stage hypervisor architecture that separates boot initialization, resident hypervisor functionality, and a Windows management interface, all while ensuring security and modularity. The tricky part here is managing the communication interface between the Windows application and the hypervisor without compromising isolation or stability. I'd start by implementing the UEFI-compatible boot component to initialize the virtualization environment and set up memory isolation. Next, I'd develop the resident hypervisor with VM-exit handling and memory translation, ensuring it operates independently of Windows processes. Finally, I'd build the Windows management application to communicate securely with the hypervisor, focusing on controlled access and diagnostics. Do you already have a preferred communication protocol or API in mind for the Windows application to interact with the hypervisor?

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅