Isolate and Protect Your Critical Systems
The QNX Hypervisor offers a comprehensive virtualization solution, including virtual memory, virtual CPUs, virtual interrupt controllers, and virtual and para-virtualized devices. It adds virtual machine management (VMM) to the QNX Neutrino® Real-time Operating System (RTOS) microkernel. So, when you design a system with the QNX Hypervisor, you are building on a foundation whose reliability and performance have been proven over 40 years in hundreds of millions of mission-critical systems.
The QNX Hypervisor protects itself and your system from both internal faults and outside interference, including from guests in its virtual machines. If through error or malicious intent a guest system attempts to overstep the boundaries you set, the QNX Hypervisor prevents the guest from completing the action.
The QNX Hypervisor includes the SMMU manager service (SMMUMAN), which works with your hardware System Memory Management Units (SMMUs) to ensure that Direct Memory Access (DMA) devices are contained.
Versatile Virtualization Model
The QNX Hypervisor leverages the latest ARMv8 and x86-64 hardware virtualization extensions to provide a supremely versatile virtualization solution. With the QNX Hypervisor you can run your OSs and their applications as guest systems in thin virtual machines, limiting your hypervisor to handling events and exceptions. Just as easily, you can run one or more guest systems in virtual machines, while also implementing a full system, including resource managers, drivers and applications, directly on the hypervisor (“bare metal”).
Devices in a QNX Hypervisor system can be physical devices (including pass-through devices), or virtual devices, including emulation and para-virtualized devices from our virtual device library. Not only can diverse OSs share the same SoC, they can share physical devices, reducing product hardware costs.
Whichever model you select as most appropriate for your project, the QNX Hypervisor ensures that the guest systems and the hypervisor itself are contained and isolated from the other systems on the SoC.
Familiar Development Environment
The QNX Hypervisor includes a virtual device developer’s API reference and a virtual device developer’s guide, complete with examples of virtual device source code you can use as models for developing your own virtual devices, including para-virtualized devices designed and built to the VirtIO standards.
If you’re familiar with the QNX Neutrino RTOS you’ll require no ramp-up time to begin your hypervisor development work: the QNX Hypervisor is fully API-compatible with the QNX Neutrino RTOS API.
You’ll be able to develop non-safety as well as safety-critical applications on the same foundations, and of course you’ll be able to continue working in the QNX Software Development Platform’s POSIX-compliant environment and using the QNX Momentics® Tool Suite.
If you’re uncertain about how to see your virtualized system through to market, our virtualization, security and safety experts can assist you at every stage—from design to certification.
View our extensive library of BSPs for a broad selection ARMv7, ARMv8 and x86-64 boards.
Need to run a safety-certified system alongside a non-safety system? The QNX Hypervisor for Safety is certified to IEC 61508 SIL 3 and ISO 26262 ASIL D.
The QNX Neutrino real-time operating system (RTOS) powers hundreds of millions of embedded systems in every industry where reliability matters.
Need to safety-certify your system? The QNX OS for Safety is the only embedded OS certified to IEC 61508 SIL3, IEC 62304 for Class C devices, and ISO 26262 at ASIL D.