Hypervizers Xen 4.17

After the year of development published the release of a free hypervisor xen 4.17 . Companies such as Amazon, ARM, Bitdefender, Citrix, Epam Systems and AMD / Xilinx took part in the development of the new issue. Issues of updates for the branch of XEN 4.17 will last until June 12, 2024, and the publication of vulnerabilities up to December 12 2025.

Key changes in Xen 4.17:

• Partial compliance with the requirements for the development of safe and reliable programs in SI formulated in the specifications misra–c used in creating critical systems. The XEN has officially introduced 4 directives and 24 Misra-C rules (out of 143 rules and 16 directives), and integration to the assembly processes of the static analyzer Misra-C, which verifies the implementation of the specification requirements.
• Provides the possibility of determining the static Xen configuration for ARM systems, which strictly determines all the resources necessary for loading guest systems in advance. All resources such as the divided memory, channels to notify the events and place in the heap of the hypervisor, are distributed in advance at the start of the hypervisor, and Do not distinguish dynamically, which excludes possible malfunctions due to lack of resources during operation.
• For built-in systems based on ARM architecture, experimental (Tech Preview) support for virtualization of input/output using protocols virtio . To exchange data with a virtual input/output device, Virtio-Mmio transport is involved, which allowed compatibility with a wide range of Virtio devices. Support for Linux, tools (Libxl/XL), Dom0less and Bacendes launched in the user space (tested Virtio-Disk, Virtio-Net, I2C and GPIO).

are implemented.

• Improved support for the DOM0less mode, which allows you to do without expanding the DOM0 environment when starting virtual machines at an early stage of server loading. The possibility of determining the CPU bullets (CPUPool) was provided at the download stage through Device Tree, which allows you to use pools in configurations without DOM0, for example, to bind different types of CPU cores on the Big.little architecture, combining powerful but consuming powerful but consuming in one chip A lot of energy, nuclei, and less productive, but more energy -efficient nuclei. In addition, Dom0less provides the opportunity to bind the front end/backend of PARARAROWAREMENCE to guest systems, which allows you to load guest systems with the necessary PARAROWAROMENCED devices.