Basic Concept

  • RTS Hypervisor with different OS execution modes
    • Virtualized Mode for General-Purpose Operating Systems
      • Windows 10 / 11
      • Debian, Ubuntu
    • Privileged Mode for Real-Time Operating Systems (RTOS)
  • Virtualization Extensions of the processor used by the RTS Hypervisor

The virtualization extensions are used by the RTS Hypervisor to monitor and execute the Guest Operating Systems. Naturally guest OS can no longer use the virtualization extension of the Processor. With Nested VT we have overcome this limitation for the virtualized mode.

to the topnach oben Pfeil

Nested Virtualization

  • Works with recent Intel processors
  • Processor virtualization extensions available to the VM
  • Windows 10 or Windows 11 with Hyper-V
  • Hyper-V guests (nested VMs):
    • Windows 10 64-bit
    • Windows 11 64-bit
    • Debian 11
    • WSL 2
    • Docker
  • General Availability: Q1 2023

Nested virtualization is a technique where a virtual machine (VM) runs on top of another hypervisor, rather than on physical hardware. In this scenario, the outer hypervisor, also known as the "parent" or "host" hypervisor, is the RTS Hypervisor, which is designed to run real-time operating systems in parallel, while the inner hypervisor is known as the "nested" or "guest" hypervisor and is Hyper-V in this case. Still the natively installed Windows runs on top of the RTS Hypervisor, Users can choose between running Windows with or without RTS Hypervisor. In both cases Hyper-V can now be used.

The RTS Hypervisor allows for real-time processing, which is critical for certain applications such as industrial control systems, medical equipment, and test systems. By running a nested Hyper-V instance within the RTS Hypervisor, it is possible to have both real-time and non-real-time workloads running side by side.

This allows for even more flexibility in terms of testing and development, as well as providing additional layers of isolation for security. Additionally, you can run other technologies such as Docker or WSL 2 on top of the nested Hyper-V, giving you the ability to enable different scenarios and configurations.