Difference between revisions of "Xen Project 4.13 Release Notes"
(Created page with " = Overview = Xen Project 4.13.0 was released on XXX Xen Project 4.13.0 is the work of YYY months of development. Also see Xen Project 4.13 Acknowledgements = New Feat...")
|Line 1:||Line 1:|
= Overview =
= Overview =
Latest revision as of 14:20, 4 April 2019
Xen Project 4.13.0 was released on XXX
Xen Project 4.13.0 is the work of YYY months of development.
Also see Xen Project 4.13 Acknowledgements
New Feature Highlights
The list of new features can be found on the following page: Xen Project 4.13 Feature List
Documentation is available on Xen Project 4.13 Man Pages
The default installation prefix has been changed to /usr/local. Previously the default installation prefix was /usr To restore the previous behaviour, specify --prefix=/usr when running ./configure, e.g.:
$ ./configure --prefix=/usr
If you choose to accept the new default then be sure to cleanup any residual bits of the old installation in the old prefix, especially libraries and tools which you might pick up by mistake.
Due to this change it may also now be necessary to run /sbin/ldconfig as root after installing Xen.
Note also that Xen now requires gcc v4.1 or greater.
First of all you will have to get the Xen 4.13 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 (>= 184.108.40.206) just pull from the proper tag (RELEASE-4.13.0) from the xen.git repo directly:
git clone -b RELEASE-4.13.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.13.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.13.0
Changes affecting downstreams and users
- Xen 4.13 is now fully Py3 compatible
- In Xen 4.13 we changed the minimum Py2 version to 2.6
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:
- None currently known