XL vs Xend Feature Comparison: Difference between revisions

From Xen
Jump to navigationJump to search
mNo edit summary
(xm/xend does not support upstream-qemu, so fix the usb 1.1 passthru with qemu-upstream line)
Line 81: Line 81:
|-
|-
|USB 1.1 device passthrough via config file (using upstream qemu)
|USB 1.1 device passthrough via config file (using upstream qemu)
|{{Tick}}
|{{NotDone}}
|{{Tick}}
|{{Tick}}
|-
|-

Revision as of 13:13, 6 January 2015

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)
Sharing storage across DomU's via w! in virtual machines configuration files [ 1 ]
Virtual framebuffer, keyboard and mouse (both para-virtualised and emulated) (includes SDL & VNC support) (includes SDL, VNC & SPICE support)
SPICE framebuffer/console support
QXL graphics device support for SPICE [ 2 ]
PV console devices
PCI device passthrough
VGA graphics device (GPU) passthrough
SCSI LUN/Host passthrough (PVSCSI) [ 2 ]
USB 1.1 device passthrough via config file (using qemu xen traditional)
USB 1.1 device passthrough via config file (using upstream qemu)
USB 1.1 device passthrough via hotplug (using qemu xen traditional) [ 3 ]
USB 1.1 device passthrough via hotplug (using upstream qemu) ?? [ 3 ]
USB 2.0 device passthrough (PVUSB) [ 3 ]
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 [ 2 ]
 
CPU pools (undocumented in XEND man pages)
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
[ 2 ] Feature will be exposed in a future release
[ 3 ] Feature development has started in the Xen 4.5 release cycle, but did not get completed

Also See: