Xen 4.2 Release Notes
Xen 4.2.0 was released on 17 September 2012. Announcement on xen.org blog: http://blog.xen.org/index.php/2012/09/17/xen-4-2-0-released/ and on xen-devel mailinglist: http://lists.xen.org/archives/html/xen-devel/2012-09/msg01271.html
Xen 4.2 contains many new features and improvements to existing functionality. Changes include improvements to Security, Scalability, Performance, RAS, Documentation and to the toolstack.
The XEND toolstack is now deprecated and should be expected to be removed in the 4.3 timescale. Therefore it is strongly recommended that users evaluate Xen 4.2 with XL for their use cases and report any omissions or blockers such that they can be addressed for 4.3. Fixes for serious functionality gaps will also be considered for backport to the 4.2.x releases.
The requirements for building Xen are documented in the README file in the Xen source tree.
- markdown (optional)
In addition Xen will now prefer to use the system wide libaio if it is available. If libaio is not installed then an in tree version will be used. Users are strongly encouraged to install their distribution's version of libaio.
An additional step has also been added to the build process. It is now necessary to run:
before building the tools (e.g. make tools, make world, make dist etc).
As a consequence of this change Xen now defaults to installing libraries into /usr/lib by default. Users on systems which use /usr/lib64 for 64-bit libraries should use the --libdir option. e.g:
$ ./configure --libdir=/usr/lib64
For more information about build dependencies, required packages for common Linux distributions and building Xen from sources please see the Compiling_Xen_From_Source wiki page. Also a separate wiki page is available for RHEL, CentOS or Fedora users for information specific to these distributions Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora.
On systems running a 32-bit hypervisor xl info will report incorrectly report large values for sharing_used_memory and sharing_freed_memory. Memory sharing is not supported on the 32-bit hypervisor and these should read zero.