Choice of Toolstacks
One really great feature of Xen is that there are several choices of toolstacks that can be used to manage it. Before the introdcution of libxenlight, there was a complicated and inefficient toolstack situation. The issue was that xend, xapi, libvirt, etc. all needed to manage many common low-level operations, which led to code duplication, ineffeciences, bugs, and wasted effort (e.g fixing the same bug in all of of the toolstacks). Further, the default toolstack at the time (xend) was difficult to understand, modify, and extend.
Libxenlight is a small lower-level library written in C. It is meant to be simple to understand and easy to modify and extend. Basically, it is meant to be the common bottom third of any Xen toolstack. It was created to provide a simple and robust API for all the toolstack to use (instead all of the toolstacks each implementing this common functionality). It was also created to be a common codebase to do Xen operations.
libxl Design Principles
- Implement Mechanisms, not policies
- Hide xenstore, libxenctrl, and libxenguest from higher levels
- Be as simple as possible
Choice of Toolstacks
xl was designed to be backwards compatible with the xm CLI for xend.
The Xen management API (xapi) is the default toolstack for Citrix XenServer and XCP. XAPI is fully open source and has been ported to Linux distributions (see Project Kronos). At the time of this writing, work is in progress to port XAPI to use libxenlight. For more information see [the XAPI source code], the [the XAPI mailing list], or the IRC channel (#xen-api on Freenode).
libvirt is a virtualization API/toolkit used to manage various virtualization technologies. There is a libxenlight port of libvirt.
XEND is the previous toolstack and continues to be included as part of the Xen source releases. However as of Xen 4.1 XEND is now deprecated and will likely be removed in a future release. It is recommended that new deployments use one of the other toolstacks discussed above.
xl was designed to be command line compatible with the xm CLI to xend and this should provide the easiest upgrade path.
Command Line Interface (CLI) Tools
The table shows the command line tools to use with each of the toolstacks.
Note: xl does not have a toolstack/cli split since the toolstack is the cli. Hence it appears under both headings.
Toolstack Feature Comparison
|Purpose-built for Xen||X||X|
|Basic VM Operations||X||X||X|
|Flexible, Advanced Storage Types||X|
|Built-in advanced performance monitoring (RRDs)||X|
|Host Plugins (XAPI)||X|
The power and flexibility of the management of Xen is an important feature. Users have a choice to use xl, XAPI, libvirt, or other toolstack to manage their Xen system(s).
- xl is very lightweight and is a great choice for develpers or users who are most comfortable with Unix like CLI tools.
- XAPI is a powerful toolstack that provides domain life-cycle management, pool-awareness (multiple Xen systems added to a central logical pool), and many other advanced features available with Xen.
- libvirt is a generalized virtualization layer for managing various virtualization technlogies with a common toolkit (or toolstack).
Why Choose XAPI?
By far the most versatile and feature-complete Xen toolstack is XAPI. XAPI is production-ready and purpose-built for Xen. It is default in Citrix XenServer and XCP. It is the API that cloud orchestration software such as OpenStack and CloudStack use to interact with Xen. It is available to be installed on standard Linux distributions such as Debian and Ubuntu (Project Kronos). With support for Fedora and CentOS coming soon too (Project Zeus Fedora Spec). Finally, there are several design decisions that make it a better choice than libvirt (see [Why XAPI?]).