Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
start [2015/03/04 08:45] admin [Xen Terminology] |
start [2015/03/04 08:56] (current) admin [The Toolstacks: xm (xend), xl (xenlight/libxl), xe (XAPI/XCP)] |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| ==== The Xen Hypervisor (Xen) ==== | ==== The Xen Hypervisor (Xen) ==== | ||
| - | > The Xen Hypervisor is the thin layer that domains (or vms, referred to as dom0 or domu) talk to when they want resources. It is now part of the linux kernel, so it no longer requires a custom kernel to run. The hypervisor does not have a shell or any easy way to mess with it directly. It is generally configured and managed from a SPECIAL vm we call dom0, on which the toolstack is installed. | + | > The Xen Hypervisor is the thin layer that domains (or vms, referred to as dom0 or domU) talk to when they want resources. It is now part of the linux kernel, so it no longer requires a custom kernel to run. The hypervisor does not have a shell or any easy way to mess with it directly. It is generally configured and managed from a SPECIAL vm we call dom0, on which the toolstack is installed. |
| ==== The Toolstacks: xm (xend), xl (xenlight/libxl), xe (XAPI/XCP) ==== | ==== The Toolstacks: xm (xend), xl (xenlight/libxl), xe (XAPI/XCP) ==== | ||
| - | > The Toolstack is a set of programs used to manage all domains on a host and to generally tell the Xen Hypervisor what to do. As you know, the primary toolstacks of choice are xe(XAPI/XCP), xl(xenlight/libxl), and xm(xend). | + | > The Toolstack is a set of programs used to manage all domains on a host and to generally tell the Xen Hypervisor what to do. [...] The primary toolstacks of choice are xe(XAPI/XCP), xl(xenlight/libxl), and xm(xend). |
| > There exist other tools that talk to the various toolstacks and provide another layer of abstraction. The most well known of these is libvirt. | > There exist other tools that talk to the various toolstacks and provide another layer of abstraction. The most well known of these is libvirt. | ||
| Line 23: | Line 23: | ||
| > Not too long ago(ok, maybe awhile ago), xen hypervisor development was taken over by the linux foundation, which opened up a lot of doors as far as development was concerned. The most important things that you need to know are: | > Not too long ago(ok, maybe awhile ago), xen hypervisor development was taken over by the linux foundation, which opened up a lot of doors as far as development was concerned. The most important things that you need to know are: | ||
| - | > 1. xm is going away. This limits your future-proof toolstack choices to xl(libxl) or xapi. | + | > 1. <color darkslateblue>**xm (Xend) is going away**</color>. This limits your future-proof toolstack choices to xl(libxl) or xapi. |
| > 2. The xapi toolstack is working towards building xapi on top of libxl. | > 2. The xapi toolstack is working towards building xapi on top of libxl. | ||
| - | **This is important to note:** xm is deprecated and **it has been removed from Xen 4.5+ !** | + | <color darkorange>**Important Note:**</color> xm (Xend) is deprecated and <color darkslateblue>**it has been removed from Xen 4.5+ !**</color> |
| ==== the xl toolstack ==== | ==== the xl toolstack ==== | ||
