XL vs Xend Feature Comparison: Difference between revisions
From Xen
Jump to navigationJump to search
Lars.kurth (talk | contribs) No edit summary |
Lars.kurth (talk | contribs) (Two more {{NotDone}}) |
||
Line 104: | Line 104: | ||
|Managed Domains |
|Managed Domains |
||
|{{Tick}} |
|{{Tick}} |
||
| |
|{{NotDone}} <sup>[ [[#Foot1|1]] ]</sup> |
||
|- |
|- |
||
|Python code in configuration files |
|Python code in configuration files |
||
|{{Tick}} |
|{{Tick}} |
||
| |
|{{NotDone}} <sup>[ [[#Foot1|1]] ]</sup> |
||
|} |
|} |
||
Revision as of 10:06, 9 August 2012
The following compares the featureset of the xend toolstack vs the xl toolstack as of Xen 4.2.
xm / xend | xl | |
---|---|---|
Guest Types | ||
PV guests | ✓ | ✓ |
HVM guests | ✓ | ✓ |
Guest lifecycle operations | ||
Create, shutdown, reboot | ✓ | ✓ |
Pause, unpause | ✓ | ✓ |
List, rename | ✓ | ✓ |
Live migration and save/restore | ✓ | ✓ |
Guest device support | ||
Network devices (both para-virtualised and emulated) | ✓ | ✓ |
Block devices (both para-virtualised and emulated) | ✓ | ✓ |
Virtual framebuffer, keyboard and mouse (both para-virtualised and emulated) | ✓ (includes SDL & VNC support) | ✓ (includes SDL, VNC & SPICE support) |
PV console devices | ✗ | ✓ |
PCI passthrough | ✓ | ✓ |
Device Model Support | ||
Qemu Xen Traditional Device Model | ✓ | ✓ |
Upstream Qemu Device Model | ✗ | ✓ |
Stub domain Qemu Xen Traditional Device Model | ✓ | ✓ |
Stub domain Upstream Qemu Device Model | ✗ | ✗ |
CPU pools | ??? | ✓ |
Cpupool-per-NUMA node. | ✗ | ✓ |
Control of CPU scheduler parameters | ✓ | ✓ |
TMEM | ✓ | ✓ |
XSM/Flash policy control | ✓ | ✓ |
Control of CPUID features exposed to guests. | ✓ | ✓ (syntax greatly improved) |
Managed Domains | ✓ | ✗ [ 1 ] |
Python code in configuration files | ✓ | ✗ [ 1 ] |
[ 1 ] Feature is explicitly not supported by xl, see XL Anti-Features