Xen Project 4.15 Release Notes

From Xen
Revision as of 11:41, 7 April 2021 by IanJackson (talk | contribs) (note qemu security thing)
Jump to navigationJump to search

Overview

Xen Project 4.15.0 was released on 8th April 2021.

Xen Project 4.15.0 is the work of 9 months of development.

New Feature Highlights

The list of new features can be found on the following page: Xen Project 4.15 Feature List

You can find information on support status (including security support) for various features in SUPPORT.md and Hypervisor Support Matrix.

Documentation is available online: Xen 4.15 Documentation

Build Requirements

Xen requires gcc v4.1.2 or later (x86), gcc 4.9 or later (arm32), or gcc 5.1 or later (arm64).

Build

First of all you will have to get the Xen 4.15 source code, which you can either download through our release tarball (including signature) from our download page. Alternatively, you can get the source in the following way:

  • With a recent enough git (>= 1.7.8.2) just clone and checkout the proper tag (RELEASE-4.15.0) from the xen.git repo directly:
git clone -b RELEASE-4.15.0 https://xenbits.xen.org/git-http/xen.git

Build instructions can be found at Compiling Xen From Source or Compiling Xen From Source on NetBSD.

Changes affecting downstreams and users

  • The very old qemu-xen-traditional device model is deprecated, and no longer security supported, when used as a host process. (It is still fully supported when used as a stub domain device model.)
  • In Xen 4.15 for ARM, we increased the minimum GCC support version.

Known issues

While we do the utmost to make the release perfect, there are always fixes which are not quite complete on time. We will add those here. So if you run into trouble, please check this section.

Currently known issues are:

  • Very recent versions of qemu mainline (qemu 6.0 and later - an RC at the time of writing) do not work as a device model.
  • Some quite new Intel systems which use "ITSSPRC static PIT clock gating" need a `hpet=legacy-replacement` boot option.

We hope to fix these issues in point releases.