Techniques such as PCI or VGA pass through are used to ensure that the performance of the GPOS remains acceptable despite virtualization. In future RTOSVisor versions, Linux, KVM and QEMU can be used against other mainstream GPOS virtualization solutions such as Microsoft Hyper-V be replaced. They merely form an infrastructure in which non-real-time GPOS can run in addition to the real-time RTOSVisor components including the RTOS. The Linux kernel, KVM and QEMU are subject to the GPL and as such are not a commercial part of RTOSVisor. For this operating mode, the minimal Linux operating system is expanded to include the widely used open source software components KVM and QEMU. Intel VT or AMD-V is only required with RTOSVisor if one or more non-real-time GPOS (such as Windows or Linux) are to be operated in addition to the RTOS. This procedure can be aptly described with the statement 'Partition where we can, virtualize where we must'. This creates so-called partitions for each RTOS. Therefore, the RTOS, which hardware is to control in real time, must be allowed direct and exclusive access to the respective hardware, memory and processor cores. If hard real-time operation is required, the hardware-supported virtualization must not be used on the RTOS, since the real-time capability would suffer due to the “pretense” of hardware and the resulting administrative work. The hardware-supported virtualizations Intel VT or AMD-V, which have only recently been introduced in Intel and AMD processors, are for sole RTOS operation thanks to the paravirtualization, which is compatible with the previous versions the RTOS is not required. Building on this basic scope, one or more instances of the same or different RTOS can initially run. This is booted first, loads and starts the RTOS virtual machines including the RTOS VM hypervisor. In the first version, the hypervisor operating system used is a Linux operating system that has been reduced to a minimum and does not have a graphic surface ('headless'). The user GPOS is not identical to the hypervisor operating system and the two operating systems are therefore independent of each other. As this independence is sometimes a requirement in practice, acontis technologies RTOSVisor presented. If the hypervisor uses the user GPOS directly, as in the previous generation, this cannot be restarted independently of the hypervisor and the RTOS. The RTOS VM hypervisor, like any other Type 2 hypervisor, uses the device drivers of the operating system on which it is running. These are summarized in the RTOS Virtual Machine Framework (VMF) (see picture).

RTOSVisor represents the fifth software generation and mainly consists of the real-time capable RTOS-VM hypervisor and the RTOS-Virtual Machines (VM).

Os9 68k emulator -mac -macos