Xen Project Release Features: Difference between revisions

From Xen
Jump to navigationJump to search
(Confirm some features of 4.2)
No edit summary
Line 98: Line 98:
|-
|-
|[http://oss.oracle.com/projects/tmem/ TMEM] -- Transcendent Memory
|[http://oss.oracle.com/projects/tmem/ TMEM] -- Transcendent Memory
|{{Tick}} <sup>[ [[#Foot2|2]] ]</sup>
|{{HalfDone}} <sup>[ [[#Foot2|2]] ]</sup>
|{{Tick}} <sup>[ [[#Foot2|2]] ]</sup>
|{{HalfDone}} <sup>[ [[#Foot2|2]] ]</sup>
|{{Tick}} <sup>[ [[#Foot2|2]] ]</sup>
|{{HalfDone}} <sup>[ [[#Foot2|2]] ]</sup>
|-
|-
|gdbsx<br/><small>debugger to debug ELF guests</small>
|gdbsx<br/><small>debugger to debug ELF guests</small>
Line 107: Line 107:
|{{Tick}}
|{{Tick}}
|-
|-
|Memory Sharing<br/><small>allow sharing of identical pages between HVM guests</small>
|Memory Sharing
|{{HalfDone}}<small>tech preview</small>
|{{HalfDone}}<small>tech preview</small>
|{{HalfDone}}<small>tech preview</small>
|{{HalfDone}}<small>tech preview</small> <sup>[ [[#Foot3|3]] ]</sup>
|-
|Memory Paging<br/><small>allow pages belonging to HVM guests to be paged to disk</small>
|{{HalfDone}}<small>tech preview</small>
|{{HalfDone}}<small>tech preview</small>
|{{HalfDone}}<small>tech preview</small>
|{{HalfDone}}<small>tech preview</small>
|{{HalfDone}}<small>tech preview</small> <sup>[ [[#Foot3|3]] ]</sup>
|-
|-
|Online resize of virtual disks
|Online resize of virtual disks
Line 149: Line 154:
|x86 Advanced Vector eXtension (AVX)
|x86 Advanced Vector eXtension (AVX)
|
|
|{{Tick}} <sup>[ [[#Foot2|2]] ]</sup>
|{{Tick}} <sup>[ [[#Foot4|4]] ]</sup>
|{{Tick}} <sup>[ [[#Foot2|2]] ]</sup>
|{{Tick}} <sup>[ [[#Foot4|4]] ]</sup>
|-
|-
|cpupool<br/><small>advanced partitioning</small>
|cpupool<br/><small>advanced partitioning</small>
Line 179: Line 184:
|qemu based disk backend (''qdisk'') for [[XL]]<br/>
|qemu based disk backend (''qdisk'') for [[XL]]<br/>
|
|
|{{Tick}} <sup>[ [[#Foot3|3]] ]</sup>
|{{Tick}} <sup>[ [[#Foot5|5]] ]</sup>
|{{Tick}} <sup>[ [[#Foot3|3]] ]</sup>
|{{Tick}} <sup>[ [[#Foot5|5]] ]</sup>
|-
|-
|[[Xen Security Modules : XSM-FLASK|FLASK]]<br/><small>mandatory access control policy providing fine-grained controls over Xen domains, similar to SELinux</small>
|[[Xen Security Modules : XSM-FLASK|FLASK]]<br/><small>mandatory access control policy providing fine-grained controls over Xen domains, similar to SELinux</small>
|{{Tick}}
|{{Tick}}
|{{Tick}}
|{{Tick}}
|{{Tick}}
|-
|vPMU<br/><small>Virtual Power Management Unit for HVM guests</small>
|{{Tick}}
|{{Tick}}
|{{Tick}}
|-
|vMCE<br/><small>Forward Machine Check Exceptions to Appropriate guests</small>
|?
|?
|{{Tick}}
|{{Tick}}
|-
|-
Line 211: Line 226:
<span id="Foot1"><sup>[ 0 ]</sup> Compile time limit, can be increased</span><br/>
<span id="Foot1"><sup>[ 0 ]</sup> Compile time limit, can be increased</span><br/>
<span id="Foot0"><sup>[ 1 ]</sup> Requires hardware virtualisation support</span><br/>
<span id="Foot0"><sup>[ 1 ]</sup> Requires hardware virtualisation support</span><br/>
<span id="Foot2"><sup>[ 2 ]</sup> Disabled by default (enable with hypervisor command line option)</span><br/>
<span id="Foot2"><sup>[ 2 ]</sup> Ddisabled by default (enable with hypervisor command line option). Not supported in production and doesn't have full security support</span><br/>
<span id="Foot3"><sup>[ 3 ]</sup> Used as a fallback if ''blkback'' and/or ''blktap2'' are not available</span><br/>
<span id="Foot3"><sup>[ 3 ]</sup> Preview, due to limited tools support. Hypervisor side in good shape</span><br/>
<span id="Foot4"><sup>[ 4 ]</sup> Disabled by default (enable with hypervisor command line option)</span><br/>
<span id="Foot5"><sup>[ 5 ]</sup> Used as a fallback if ''blkback'' and/or ''blktap2'' are not available</span><br/>


[[Category:Xen]] [[Category:Users]]
[[Category:Xen]] [[Category:Users]]

Revision as of 10:57, 10 September 2012

Xen 4.0 Xen 4.1 Xen 4.2 (Testing)
Initial Release 7 April 2010 25 March 2011 TBD
Host Limits
Physical CPUs 128 [ 0 ] >255 4095
RAM 1TB 5TB 5TB
Guest Types
Paravirtualised
Traditional Xen PV guest
HVM Guest [ 1 ]
Fully virtualised guest using hardware virtualisation extensions
PV-on_HVM Guest [ 1 ]
Fully virtualised guest using PV extensions for improved performance
PV Guest Limits
Virtual CPUs 128 >255 512
RAM 512GB 512GB 512GB
HVM Guest Limits
Virtual CPUs 128 128 256
RAM 1TB 1TB 1TB
Toolstack
xend / xm deprecated in this release
XL initial implementation preview release
Features
Live Migration, Save & Restore
Memory ballooning
Blktap2
PCI Passthrough
TMEM -- Transcendent Memory [ 2 ] [ 2 ] [ 2 ]
gdbsx
debugger to debug ELF guests
Memory Sharing
allow sharing of identical pages between HVM guests
tech preview tech preview tech preview [ 3 ]
Memory Paging
allow pages belonging to HVM guests to be paged to disk
tech preview tech preview tech preview [ 3 ]
Online resize of virtual disks
Remus Fault Tolerance
Physical CPU Hotplug
Physical Memory Hotplug
Support for PV kernels in bzImage format
Credit 2 Scheduler
designed for latency-sensitive workloads and very large systems.
prototype prototype
1GB/2MB super page support
x86 Advanced Vector eXtension (AVX) [ 4 ] [ 4 ]
cpupool
advanced partitioning
memaccess API
enabling integration of 3rd party security solutions into Xen virtualized environments
Deliver events to PVHVM guests using event channels
HVM PXE Stack gPXE iPXE iPXE
xentrace
performance analysis
qemu based disk backend (qdisk) for XL
[ 5 ] [ 5 ]
FLASK
mandatory access control policy providing fine-grained controls over Xen domains, similar to SELinux
vPMU
Virtual Power Management Unit for HVM guests
vMCE
Forward Machine Check Exceptions to Appropriate guests
? ?
PyGrub
Support for GRUB 2
Support for /boot on ext4
Third Party
libvirt driver for XL

[ 0 ] Compile time limit, can be increased
[ 1 ] Requires hardware virtualisation support
[ 2 ] Ddisabled 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