Archived/Xen Project Release Features 4.0 to 4.3: Difference between revisions

From Xen
Jump to navigationJump to search
mNo edit summary
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
__TOC__
__TOC__


''Legend:''
''Legend:'' {{Tick}}: Feature {{HalfDone}}: Partial {{NotDone}}: Removed
* {{Tick}}: Feature
* {{HalfDone}}: Partial
* {{NotDone}}: Removed
* For definitions of experimental, preview, supported and deprecated see [[Xen Project Release Features/Definitions|here]]


== Overview ==
== Overview ==
{|class="prettytable" style="text-align: left;" valign="top"
{|class="prettytable" style="text-align: left; width: 100%" valign="top"
!style="width: 48%;"|
!style="width: 48%;"|
!style="width: 13%;"|Xen 4.0
!style="width: 13%;"|Xen 4.0
Line 109: Line 113:
== Limits ==
== Limits ==


{|class="prettytable" style="text-align: left;" valign="top"
{|class="prettytable" style="text-align: left; width: 100%" valign="top"
!style="width: 48%;"|
!style="width: 48%;"|
!style="width: 13%;"|Xen 4.0
!style="width: 13%;"|Xen 4.0
Line 204: Line 208:
== Toolstack and Tools ==
== Toolstack and Tools ==


{|class="prettytable" style="text-align: left;" valign="top"
{|class="prettytable" style="text-align: left; width: 100%" valign="top"
!style="width: 48%;"|
!style="width: 48%;"|
!style="width: 13%;"|Xen 4.0
!style="width: 13%;"|Xen 4.0
Line 278: Line 282:
== Features ==
== Features ==


{|class="prettytable" style="text-align: left;" valign="top"
{|class="prettytable" style="text-align: left; width: 100%" valign="top"
!style="width: 48%;"|
!style="width: 48%;"|
!style="width: 13%;"|Xen 4.0
!style="width: 13%;"|Xen 4.0
Line 429: Line 433:
== Interoperability / Hardware Support ==
== Interoperability / Hardware Support ==


{|class="prettytable" style="text-align: left;" valign="top"
{|class="prettytable" style="text-align: left; width: 100%;" valign="top"
!style="width: 48%;"|
!style="width: 48%;"|
!style="width: 13%;"|Xen 4.0
!style="width: 13%;"|Xen 4.0
Line 485: Line 489:
== Device Models and Virtual Firmware ==
== Device Models and Virtual Firmware ==


{|class="prettytable" style="text-align: left;" valign="top"
{|class="prettytable" style="text-align: left; width: 100%" valign="top"
!style="width: 48%;"|
!style="width: 48%;"|
!style="width: 13%;"|Xen 4.0
!style="width: 13%;"|Xen 4.0
Line 560: Line 564:
<br/><span id="Foot5"><sup>[ 5 ]</sup> Used as a fallback if ''blkback'' and/or ''blktap2'' are not available</span>
<br/><span id="Foot5"><sup>[ 5 ]</sup> Used as a fallback if ''blkback'' and/or ''blktap2'' are not available</span>
<br/><span id="Foot6"><sup>[ 6 ]</sup> See [[Xen ARM with Virtualization Extensions]]; basic functionality implemented; lack of real hardware to validate against
<br/><span id="Foot6"><sup>[ 6 ]</sup> See [[Xen ARM with Virtualization Extensions]]; basic functionality implemented; lack of real hardware to validate against
<br/><span id="Foot7"><sup>[ 7 ]</sup> Limited by supported host memory
<br/><span id="Foot12"><sup>[ 12 ]</sup> Not yet supported on ARM; for a more detailed update on what is supported on ARM see [http://www.slideshare.net/xen_com_mgr/xen-on-arm-xen-developer-summit-2014 here]
<br/><span id="Foot8"><sup>[ 8 ]</sup> Tested on Broadcom 7445D0 A15, Midway (Calxeda), Odroid-XU, OMAP5, OMAP6, DRA7 (Texas Instrument), Exynos5 (Samsung), SunXI (AllWinner) aka A20/A21, CubieTruck, CubieBoard
<br/><span id="Foot9"><sup>[ 9 ]</sup> Tested on Vexpress (ARM Ltd.), Seattle (AMD), Mustang (Applied Micro-X-Gene), McDivitt aka HP Moonshot cartridge (Applied Micro X-Gene)
<br/><span id="Foot10"><sup>[ 10 ]</sup> [[Remus]] has been ported to [[XL]] and has been tested with [[COLO_-_Coarse_Grain_Lock_Stepping|COLO]] which is currently outside the Xen tree, but planned to be included in Xen 4.6. Also see [[Remus Toolkit Differences]] explaining differences between Remus with [[XM]] (not supported in Xen 4.5) and [[XL]]
<br/><span id="Foot11"><sup>[ 11 ]</sup> There are a number of reported crashes that have not yet been fixed and some [[Nested_Virtualization_in_Xen#Know_Issues|known limitations]]
<br/><span id="Foot12"><sup>[ 12 ]</sup> Not yet supported on ARM; for a more detailed update on what is supported on ARM see [http://www.slideshare.net/xen_com_mgr/xen-on-arm-xen-developer-summit-2014 here] and [[Xen_ARM_with_Virtualization_Extensions|here]]
<br/><span id="Foot13"><sup>[ 13 ]</sup> The PCI passthrough features did not make it on time for Xen 4.5, but doing passthrough of MMIO regions did. In the ARM world it is quite common to have no PCIe devices and to only access devices using MMIO regions. As such this feature allows us to have driver domains be in charge of network or storage devices.
<br/><span id="Foot14"><sup>[ 14 ]</sup> Added the following platforms to <sup>[ 8 ]</sup>: Renesas R-Car Gen2, Huawei hip04-d04
<br/><span id="Foot15"><sup>[ 15 ]</sup> Added the following platforms to <sup>[ 9 ]</sup>: Thunder X (partial), Xilinx ZynqMP SoC
<br/><span id="Foot16"><sup>[ 16 ]</sup> Now tested as part of Xen Project Test Lab and OpenStack CI Loop
<br/><span id="Foot17"><sup>[ 17 ]</sup> Now tested as part of Xen Project Test Lab
<br/><span id="Foot18"><sup>[ 18 ]</sup> Migration v2: see [https://www.youtube.com/watch?v=RwiDeG21lrc] and [http://xenbits.xen.org/docs/4.6-testing/features/migration.html]. VM migration using libvirt between two hosts is now tested. Live Migration between hosts of different Xen versions is now tested.
<br/><span id="Foot19"><sup>[ 19 ]</sup> The memory event subsystem has been reworked and extended to a new VM event subsystem. The new VM event subsystems supports both the ARM and x86 architectures.
<br/><span id="Foot20"><sup>[ 20 ]</sup> Passthrough for non-PCI devices allows users to passthrough devices via partial device trees.
<br/><span id="Foot21"><sup>[ 21 ]</sup> Dates for historical releases have not be researched.
<br/><span id="Foot21"><sup>[ 21 ]</sup> Dates for historical releases have not be researched.

<br/><span id="Foot22"><sup>[ 22 ]</sup> The code for hypervisor live patching is NOT enabled by default. When compiling the hypervisor one must [[LivePatch#How_to_enable_it|change the config]] to build it. Note that Live Patching is currently only supported on x86. For more information on live patching, see [[LivePatch]].
<br/><span id="Foot23"><sup>[ 23 ]</sup> CPU ID Levelling enables migration of VM’s between a larger range of non-identical hosts than previously supported.
<br/><span id="Foot24"><sup>[ 24 ]</sup> The COLO Manager has been fully integrated as an experimental feature into Xen 4.7. Note that the COLO Block Replication and COLO Proxy components, both of which are QEMU components, are currently still reviewed by the QEMU community. Both components are available as out-of-tree add-ons to the Xen Project Hypervisor, until fully integrated into QEMU.
<br/><span id="Foot25"><sup>[ 25 ]</sup> Added experimental support for VT-d Posted Interrupts, VMX TSC Scaling, Memory Protection Keys
<br/><span id="Foot26"><sup>[ 26 ]</sup> Removed support for Huawei hip04-d04


[[Category:Xen]] [[Category:Users]] [[Category:Fundamentals]] [[Category:Archived]]
[[Category:Xen]] [[Category:Users]] [[Category:Fundamentals]] [[Category:Archived]]

Latest revision as of 16:38, 12 March 2018

Legend:

  • : Feature
  • : Partial
  • : Removed
  • For definitions of experimental, preview, supported and deprecated see here

Overview

Xen 4.0 Xen 4.1 Xen 4.2 Xen 4.3
Initial Release 7 April 2010 25 March 2011 17 Sept 2012 9 July 2013
Supported until ???[ 21 ] ???[ 21 ] ???[ 21 ] Jan 2015
Security support until ???[ 21 ] ???[ 21 ] Sept 2015 July 2016
Feature List FL 4.2 FL 4.3
Release Notes RN 4.0 RN 4.1 RN 4.2 RN 4.3
Supported Mainline Architectures for the hypervisor (Host)
IA-A32 removed
X86-64
Itanium (ia64) deprecated in this release deprecated removed
ARM v7 + Virtualization Extensions preview [ 6 ]
ARM v8 preview [ 6 ]
Guest Types
For X86 Architectures
Paravirtualised
Traditional Xen Project PV guest
HVM Guest [ 1 ]
Fully virtualised guest using hardware virtualisation extensions
PV-on-HVM Guest [ 1 ]
Fully virtualised guest using PV extensions/drivers for improved performance
For ARM Architectures
ARM Guest
Optimal combination of full virtualization and PV extensions
preview [ 6 ]


Limits

Xen 4.0 Xen 4.1 Xen 4.2 Xen 4.3
Host Limits
For X86 Architectures
Physical CPUs 128 [ 0 ] >255 4095 4095
Physical RAM 1TB 5TB 5TB 16TB
For ARM Architectures
Physical CPUs 8
Physical RAM 16GB
Guest Limits
X86 PV Guest Limits
Virtual CPUs 128 >255 512 512
Virtual RAM 512GB 512GB 512GB 512GB
X86 HVM Guest Limits
Virtual CPUs 128 128 128 128
Virtual RAM 1TB 1TB 1TB 1TB
ARM Guest Limits
Virtual CPUs 8
Virtual RAM 16GB
Number of event channels
Event Channels 1024/4096 1024/4096 1024/4096 1024/4096



Toolstack and Tools

Xen 4.0 Xen 4.1 Xen 4.2 Xen 4.3
Toolstack
Built-in
xend / xm deprecated in this release deprecated
XL initial implementation preview release
Qemu based disk backend (qdisk) for XL
[ 5 ] [ 5 ] [ 5 ]
XL Open vSwitch integration preview
3rd Party
libvirt driver for XL
Tooling
gdbsx
debugger to debug ELF guests
vPMU
Virtual Performance Management Unit for HVM guests
[ 4 ] [ 4 ] [ 4 ] [ 4 ]
Serial console Add EHCI debug support
xentrace
performance analysis


Features

Xen 4.0 Xen 4.1 Xen 4.2 Xen 4.3
Advanced Memory Management
Memory Ballooning
Memory Sharing
allow sharing of identical pages between HVM guests
preview preview preview [ 3 ] preview [ 3 ]
Memory Paging
allow pages belonging to HVM guests to be paged to disk
preview preview preview [ 3 ] preview [ 3 ]
TMEM - Transcendent Memory experimental [ 2 ] experimental [ 2 ] experimental [ 2 ] experimental [ 2 ]
Resource Management
Cpupool
advanced partitioning
Credit 2 Scheduler
designed for latency-sensitive workloads and very large systems.
prototype prototype experimental
NUMA scheduler affinity
Scalability
1GB/2MB super page support
Deliver events to PVHVM guests using Xen event channels
Fair locks (ticket-locks)
High Availability and Fault Tolerance
Live Migration, Save & Restore
Remus Fault Tolerance
X86 vMCE
Forward Machine Check Exceptions to Appropriate guests
Network and Storage
Blktap2
Online resize of virtual disks
Security (also see this presentation or this document)
Driver Domains
Device Model Stub Domains
Virtual Machine Introspection (Memaccess and VM Event APIs)
enabling integration of 3rd party security solutions into Xen virtualized environments
XSM & FLASK
mandatory access control policy providing fine-grained controls over Xen domains, similar to SELinux
XSM & FLASK support for IS_PRIV
vTPM Support

updates and new functionality


Interoperability / Hardware Support

Xen 4.0 Xen 4.1 Xen 4.2 Xen 4.3
X86
X86 Nested Virtualisation
Running a hypervisor inside an HVM guest
experimental experimental
HVM PXE Stack (x86) gPXE iPXE iPXE iPXE
Physical CPU Hotplug
Physical Memory Hotplug
Support for PV kernels in bzImage format
PCI Passthrough [ 12 ]
X86 Advanced Vector eXtension (AVX) [ 4 ]


Device Models and Virtual Firmware

Xen 4.0 Xen 4.1 Xen 4.2 Xen 4.3
Device Models and Virtual Firmware for HVM guests
For X86 Architectures
Traditional Device Model
Device emulator based on Xen fork of Qemu
Qemu Upstream Device Model
Device emulator based on upstream Qemu
preview default, unless stubdomains are used
ROMBIOS
BIOS used with traditional device model only
SeaBIOS
BIOS used with upstream qemu device model and XL only
OVMF/Tianocore
UEFI Firmware used with upstream qemu device model and XL only
experimental [ 4 ] experimental [ 4 ]
PV Bootloader support
For X86 Architectures
PyGrub support for GRUB 2
PyGrub support for /boot on ext4
pvnetboot support
Bootloader supporting network boot of PV guests


Notes

[ 0 ] Compile time limit, can be increased
[ 1 ] Requires hardware virtualisation support
[ 2 ] Disabled by default (enable with hypervisor command line option). Not supported in production and doesn't have full security support
[ 3 ] Preview, due to limited tools support. Hypervisor side in good shape
[ 4 ] Disabled by default (enable with hypervisor command line option)
[ 5 ] Used as a fallback if blkback and/or blktap2 are not available
[ 6 ] See Xen ARM with Virtualization Extensions; basic functionality implemented; lack of real hardware to validate against
[ 12 ] Not yet supported on ARM; for a more detailed update on what is supported on ARM see here
[ 21 ] Dates for historical releases have not be researched.