Xen 4.2 Release Notes: Difference between revisions
(Reference 4.2 feature list instead of duplicating.) |
(Add links, formatting and fix typos) |
||
| Line 11: | Line 11: | ||
== Default Toolstack == |
== Default Toolstack == |
||
[[XL]] is now the default toolstack supplied with Xen. Please see the [[XL]] page for guidance on migrating from |
[[XL]] is now the default toolstack supplied with Xen. Please see the [[XL]] page for guidance on migrating from [[XEND]]. |
||
The |
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. |
||
= Build Requirements = |
= Build Requirements = |
||
The requirements for building Xen are documented in the <tt>README</tt> file in the Xen source tree. |
The requirements for building Xen are documented in the [http://xenbits.xen.org/hg/xen-4.2-testing.hg/file/tip/README <tt>README</tt> file in the Xen source tree]. |
||
Some additional build dependencies have been added since [[Xen 4.1 Release Notes|Xen 4.1]]: |
Some additional build dependencies have been added since [[Xen 4.1 Release Notes|Xen 4.1]]: |
||
| Line 26: | Line 26: | ||
* markdown (optional) |
* 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 addition Xen will now prefer to use the system wide <tt>libaio</tt> if it is available. If <tt>libaio</tt> is not installed then an in tree version will be used. Users are strongly encouraged to install their distribution's version of <tt>libaio</tt>. |
||
An additional step has also been added to the build process. It is now necessary to run: |
An additional step has also been added to the build process. It is now necessary to run: |
||
Revision as of 12:17, 7 September 2012
|
This is a draft of the Xen 4.2 release notes. Xen 4.2 is not yet released. |
Overview
New Features
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.
For a list of new features and changes see Xen 4.2 Feature List.
Default Toolstack
XL is now the default toolstack supplied with Xen. Please see the XL page for guidance on migrating from XEND.
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.
Build Requirements
The requirements for building Xen are documented in the README file in the Xen source tree.
Some additional build dependencies have been added since Xen 4.1:
- libyajl
- glib
- pkg-config
- 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:
$ ./configure
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
Known issues
XL's default configuration is not compatible with driver domains. To use driver domains with XL you should set run_hotplug_scripts=0 in /etc/xen/xl.conf.
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.
