Difference between revisions of "Xen Project 4.6 Release Notes"

From Xen
Line 26: Line 26:
   
 
Note also that Xen now requires gcc v4.1 or greater.
 
Note also that Xen now requires gcc v4.1 or greater.
  +
  +
= Build with Raisin =
  +
  +
Besides conventional "./configure; make" routine, you can also build with Raisin.
  +
  +
git clone git://xenbits.xen.org/raisin.git
  +
cd raisin
  +
cp configs/config-4.6 config
  +
./raise -y build
  +
   
 
= Known issues =
 
= Known issues =

Revision as of 10:18, 13 October 2015


Overview

Xen Project 4.6.0 was released on October 13, 2015.

Xen Project 4.6.0 is the work of 8.7 months of development, with 2247 changesets.

Also see Xen Project 4.6 Acknowledgements

New Feature Highlights

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

You can also see an evolution of features on Xen Project Release Features

Documentation is available on Xen Project 4.6 Man Pages

Build Requirements

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.

Build with Raisin

Besides conventional "./configure; make" routine, you can also build with Raisin.

git clone git://xenbits.xen.org/raisin.git
cd raisin
cp configs/config-4.6 config
./raise -y build


Known issues

While we did the utmost to get a release out, there are certain fixes which were not complete on time. As such please reference this section if you are running into trouble.

  • Block script with QEMU is broken.
  • Can't build debug version of toolstack. This was discovered shortly after we tagged RELEASE-4.6.0, use this patch[1] to fix it.