Difference between revisions of "Xen Project 4.15 Release Notes"

From Xen
(edits)
(substance)
Line 15: Line 15:
 
= Build Requirements =
 
= Build Requirements =
   
Xen requires gcc v4.1.2 or later for x86, or gcc 4.8 or later for ARM.
+
Xen requires gcc v4.1.2 or later (x86), gcc 4.9 or later (arm32), or gcc 5.1 or later (arm64).
   
 
= Build =
 
= Build =
First of all you will have to get the Xen 4.14 source code, which you can either download through our release tarball (including signature) from our [https://downloads.xenproject.org/release/xen/4.14.0 download page]. Alternatively, you can get the source in the following way:
+
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 [https://downloads.xenproject.org/release/xen/4.15.0 download page]. Alternatively, you can get the source in the following way:
   
* With a recent enough git (>= 1.7.8.2) just pull from the proper tag (RELEASE-4.14.0) from the [http://xenbits.xenproject.org/xen.git xen.git] repo directly:
+
* With a recent enough git (>= 1.7.8.2) just clone and checkout the proper tag (RELEASE-4.15.0) from the [http://xenbits.xenproject.org/xen.git xen.git] repo directly:
git clone -b RELEASE-4.14.0 https://xenbits.xen.org/git-http/xen.git
+
git clone -b RELEASE-4.15.0 https://xenbits.xen.org/git-http/xen.git
 
* With an older git version (and/or if that does not work, e.g. complaining with a message like this: Remote branch RELEASE-4.14.0 not found in upstream origin, using HEAD instead), do the following:
 
 
git clone https://xenbits.xen.org/git-http/xen.git
 
cd xen
 
git checkout RELEASE-4.14.0
 
   
 
Build instructions can be found at [[Compiling Xen From Source]] or [[Compiling Xen From Source on NetBSD]].
 
Build instructions can be found at [[Compiling Xen From Source]] or [[Compiling Xen From Source on NetBSD]].
Line 33: Line 27:
 
= Changes affecting downstreams and users =
 
= Changes affecting downstreams and users =
   
* In Xen 4.14.0 we changed the minimum Py2 version to 2.7. This is likely to change back to 2.6 with 4.14.1.
+
* In Xen 4.15 for ARM, we increased the minimum GCC support version.
   
 
= Known issues =
 
= Known issues =
Line 41: Line 35:
 
Currently known issues are:
 
Currently known issues are:
   
  +
* Recent versions of qemu mainline do not work as a device model.
* None currently known
 
  +
* 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.
   
 
[[Category:Xen]]
 
[[Category:Xen]]
 
[[Category:Release Notes]]
 
[[Category:Release Notes]]
 
[[Category:Users]]
 
[[Category:Users]]
[[Category:Xen 4.14]]
+
[[Category:Xen 4.15]]

Revision as of 11:37, 7 April 2021

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

  • 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:

  • Recent versions of qemu mainline 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.