XEN virtualization on iWave’s i.MX8QM System on Module

iWave Systems, a leading embedded solutions provider company based in Bangalore has successfully demonstrated Xen virtualization hypervisor on their i.MX8 QM SoC based System on Module. The multi-core SOM comprises of 2x Arm® Cortex®-A72 @1.8 GHz and 4x Arm® Cortex®-A53 @1.2 GHz and 2x additional Cortex®-M4F @ 266 MHz, rendering a highly powerful integrated solution on a SMARC R2.0 compatible module.
To fully explore the enormous computing capability of the i.MX8 QM SOM, iWave has implemented the virtualization of hardware using the open-source type 1 Xen hypervisor. The Xen hypervisor enables multiple virtual machines to be created over a single hardware resource, each virtual machine capable of running its independent operating system. This enables i.MX8 QM SOM runs multiple operating systems concurrently on the same physical board. The Xen hypervisor allows maximum utilization of resources thereby improving overall system performance and efficiency.

About Xen hypervisor

Xen is an open-source type-1 hypervisor developed by the University of Cambridge and is now being developed by the Linux Foundation. Xen runs directly on the hardware to manage guest operating systems. Hence, it's also considered as a bare-metal hypervisor. Xen has less overhead enabling faster performance and Operating Systems are more secure as they don't rely on base OS for installing the hypervisor.
A system running the Xen hypervisor contains three components:
• Xen Hypervisor
• Domain 0 (Dom0) – Privileged virtual machine running on the hypervisor that can access the hardware directly and interact with other unprivileged virtual machines running on the system.
• Multiple Domain U (DomU) – Unprivileged virtual machine running on the hypervisor and have no direct access to the hardware (e.g. CPU, memory, timer, and interrupts cannot be directly accessed)

During the initial system start-up, Xen hypervisor launches the Dom0 that runs the Linux operating system. The Dom0 has unique privileges to access the Xen hypervisor compared to other Domains. Dom0 manages the DomU, the unprivileged domains running on the system. Dom0 allocate and map hardware resources for the DomU domains.
Advantages: -
• Less overhead compared to type-2 hypervisors since type-1 hypervisors make use of ARM virtualization extensions.
• Having faulty/buggy OS in the DOM-U domain will not disrupt the functionalities of DOM-0 OS.
• DOM-U driver domains can support legacy hardware drivers no longer supported by the new OS.
• Have completely isolated workspaces with different requirements. Eg: gaming and multimedia.
• Better resource management since resources rarely used will not be powered on if the domain it belongs to is not booted.

Xen demo on iWave’s i.MX8QM SOM
In iWave’s Xen Demo on i.MX8QM Board, the DOM-0 OS runs Linux 4.9.88 from eMMC and DOM-U runs Android Oreo 8.1 from USB drives. Such a system can be used where there is a need for both faster, highly reliable OS (such as Linux) and more multi-featured slightly slower OS (such as Android) to be running on the same hardware.

7/B,29th Main
BTM Layout 2nd Stage

iWave Systems Technologies, India is a leading embedded solutions provider company that specializes in the development of low power, high-performance ARM-based System-On-Modules (SOM), SBC and Development Platforms.Our ARM-based platforms are based on a wide variety of industry-leading SOCs including NXP, Renesas, Qualcomm, Intel, Xilinx, etc. enabling solutions for a wide range of embedded applications including but not limited to Industrial, Automotive, IoT & Medical domains.
iWave supports standard and custom SOMs (Qseven, SMARC & SODIMM form factors) with minimum of 10 years longevity support and dedicated technical support on the hardware & software end.
iWave also offers integrated turnkey design services which include Board level Custom Hardware development and Embedded Software Services such as BSP porting, Device driver development, Wi-Fi & GUI services, Firmware, Middleware, Application, Protocols and Stack development.

This release was published on openPR.