Micro To The Max

MicroV is an open source hypervisor built from the ground up, designed specifically to execute Micro VMs (i.e., tiny virtual machines with no emulation needed to execute them). AIS developed MicroV to support its U.S. Gov’t and commercial customers with everything from basic research to operational environments with strict requirements on performance, security, reliability, disaggregation, isolation, and a small trusted computing base.

Unprecedented Flexibility

AIS has over 13 years of hypervisor experience ranging from basic research like the [MoRE](link) hypervisor, to operational hypervisors like [SecureView](link). To support our wide range of customer requirements, AIS uniquely designed MicroV to support as many use cases as possible. MicroV’s design supports both type 1 and type 2 configurations, while simultaneously supporting any root OS of your choice including Windows, Linux and UEFI. MicroV could even be easily modified to support more esoteric environments like ThreadX, FreeRTOS or even a custom operating system. In addition, MicroV has been designed with AUTOSAR compliance in mind to support critical systems applications like automotive, medical, space and aviation. No other hypervisor currently available provides this same level of flexibility.

To support mobile, embedded, IoT and even cloud computing, performance and power efficiency was a priority in MicroV’s design. To accomplish this, MicroV is designed to run everything, including the root OS, in a virtual machine while delegating scheduling and power management. This design choice not only ensures MicroV has a small trusted computing base with strong security and isolation, it provides exceptional performance and battery life by allowing the operating system that was designed for a device to manage the device. Finally, AIS leveraged it’s experience with SecureView to ensure MicroV was designed with security in mind. Unlike most other hypervisors, MicroV’s internal design includes a small microkernel, executing the majority of the hypervisor in a deprivileged environment, complete with SELinux style enforcement of the hypervisor’s internal communications. Whether you need a hypervisor for research, cloud computing, embedded/IoT, government or critical systems, MicroV was designed for you.


Isolate Everything

Everything, including the root operating system, runs on a virtual machine. This allows MicroV to protect the root operating system from Micro VMs, as well as protecting Micro VMs from the root operating system.


MicroV can support any root operating system. Currently MicroV supports Windows, Linux and UEFI, but support can easily be added for any operating system including an RTOS as MicroV is implemented as a self-contained binary.


MicroV removes the need for emulation by requiring each Micro VM to execute a fully enlightened kernel (or unikernel). By default MicroV provides support for Linux, but MicroV’s APIs can be leveraged to support any guest operating system of your choice.

Power and Scheduling

MicroV leverages the scheduler in the root operating system to schedule Micro VMs, improving both performance and battery life dramatically. Unlike KVM, MicroV accomplishes this without running the entire Linux kernel in the hypervisor.

AUTOSAR Compliance

MicroV was written in C++ using the AUTOSAR standards, enabling MicroV’s use in critical systems including automotive, medical and government spaces.


Unlike most other hypervisors, MicroV is open sourced under the MIT license. Feel free to use MicroV in your own commercial products. If you find a bug or want to add a feature, contact us.

Under The Hood

MicroV’s hypervisor is built using the Bareflank SDK. Running on top of the Bareflank Microkernel, MicroV is a deprivileged Bareflank extension designed specifically to execute small, fully enlightened virtual machines called Micro VMs. MicroV can either start directly from the root operating system, demoting it into a virtual machine, or it can start from UEFI and boot the root operating system inside a virtual machine. From there, additional Micro VMs can be created and executed. Unlike other hypervisors, MicroV gives the root operating system full access to most of the hardware on the device, while still executing under MicroV inside a virtual machine. This allows MicroV to protect the Micro VMs in addition to the root operating system. MicroV uses the root operating system’s scheduler and power management routines to execute each Micro VM. Not only does this improve performance and battery life, it also provides support for any scheduling algorithm you might need including real-time. MicroV removes the need for emulation by requiring each Micro VM to use a fully enlightened kernel (or unikernel), meaning the Micro VM doesn’t have access emulated hardware. MicroV accomplishes this by providing its own, custom virtual interface that is designed to further reduce the need for emulation (even more so than existing PV interfaces like virtio). As a result, the entire architecture is dramatically simplified. Addition technical details about MicroV can be found on our GitHub page.

Common Questions

What is the current status of MicroV?

MicroV is currently under heavy development by AIS. The initial version is expected around the end of 2022.

What architectures does MicroV support?

Support for Intel and AMD is planned for the initial release. Support for ARM will follow.

What operating systems does MicroV support in each Micro VM?

Support for a custom Linux kernel is currently planned for the initial release. Support for unikraft (and possibly other unikernels) will likely follow.

What is MicroV licensed under?

MIT. Feel free to use it to build your own products and services. If you find a bug, would like to see a specific feature or even contribute, let us know.

What root operating systems does MicroV support?

Support for Windows 10, Linux (tested on Ubuntu, Fedora and Arch) and limited support for UEFI are planned for the initial release. Additional operating systems can be added by request.

What about Windows in a Micro VM?

Believe it or not, we think we can make this happen in the future.

Why did you build another hypervisor?

To support our US Government and commercial customers. None of the existing hypervisor solutions provide this type of design approach.

Can MicroV be used to support containers?

Yes, it’s not the focus of this project, but MicroV’s design can absolutely be used in this way.

Want To Learn More?

Reach out to us on Slack, ask a question in our GitHub issue tracker or fill out the form below and an AIS representative will be in touch.

    [anr_nocaptcha g-recaptcha-response]
    Privacy Settings
    We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
    Consent to display content from - Youtube
    Consent to display content from - Vimeo
    Google Maps
    Consent to display content from - Google
    Consent to display content from - Spotify
    Sound Cloud
    Consent to display content from - Sound