XEN Hypervisor

The purpose of this page is to give a high level overview of the Xen Hypervisor as it applies to Xilinx devices. 

Table of Contents


Xen is a type-1 Hypervisor defined, maintained and provided to the open source community by the Xen Project. Xilinx actively contributes code to the Xen Project to provide Zynq UltraScale+ MPSoC platform support as well as key enhancements which benefit Xilinx customer use-cases.

Xen allows multiple instances of operating system(s) or bare-metal applications to execute on Zynq UltraScale+ MPSoC. Additional information on the Xen hypervisor can be found at the Xen Project Getting Started page.

Xilinx provides within the PetaLinux Tools and also in our Git tree, core elements and example designs to enable usage of Linux + bare-metal system configurations across the processing cores of Zynq UltraScale+ MPSoC. Key components of these example designs are described below in order to assist our customers to configure, build and deploy these basic configurations and to also identify current functionality gaps which may need to be further addressed within the customer's final system architecture.

One Linux DomU + two Bare-Metal Applications

Linux Dom0 with custom apps + three Bare-Metal Applications

Two Linux DomU + one Bare-Metal Application

Three Linux DomU

Xen-Based-System Feature Summary

Xilinx provides reference designs which include core capabilities for Xen-based systems. The table below lists important system features and the first Xilinx Xen release that makes them available.

FeatureXen release
Cache Coloring2020.1

Using Xen Hypervisor with Xilinx Releases

Additional Commercial Support and Professional Services

Xilinx recommends our Premier Partner: DornerWorks to customers seeking support beyond the example designs described above. DornerWorks has worked with customers to solve complex system problems including new OS support, frontend drivers, performance optimization, DMA accesses, and inter-OS communications.

Related Links

Non-hypervisor AMP Options and Viability: Unsupervised AMP