Xen Project 4.5 Release Notes: Difference between revisions
Lars.kurth (talk | contribs) (Created page with "{{TODO|Create from last relevant RC mail}} Category:Xen 4.5") |
Lars.kurth (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{TODO|Create from last relevant RC mail}} |
{{TODO|Create from last relevant RC mail}} |
||
= Overview = |
|||
{{TODO|Similar to Xen_Project_4.4_Release_Notes#Overview}} |
|||
= xm/xend have been removed = |
|||
In Xen 4.5, the [[XM]] toolstack has been removed and been replaced by [[XL]]. [[XL]] has been designed to be '''backwards compatible''' with existing [{XM]] domain configuration files and command line syntax. It is therefore expected that any existing configurations should work with [[XL]] with the following exceptions: |
|||
* Arbitrary embedded python is not supported. Therefore it will be necessary to remove any python code from your configuration files. |
|||
* Managed domains (e.g. <code>xm vm-create</code>, <code>xm vm-start</code> etc) are not supported by <code>xl</code>. Other toolstacks which support managed domains are the [[XAPI]] toolstack and [[Libvirt]]. |
|||
* <code>xl</code> does not support the <code>w!</code> notation to share disks between several DomU's |
|||
* For a complete comparison see [[XL vs Xend Feature Comparison]] |
|||
The other notable difference is that <code>xl</code>, unlike <code>xend</code>, will not perform any host networking configuration for you. The <code>xend</code> code to reconfigure on startup is extremely fragile, prone to bugs when either distro or Xen are upgraded and rather difficult to debug. Instead <code>xl</code> takes the approach of deferring such network configuration to the distribution configuration tools which are usually well understood and documented. Therefore upon upgrading to <code>xl</code> it is necessary to configure your host networking stack appropriately. Please see [[Network_Configuration_Examples_(Xen_4.1+)]] for more details on how to do this. |
|||
<code>xl</code> is designed to be compatible with <code>xm</code>, except for the cases listed above. If you find a situation where <code>xl</code> seems to be incompatible, please file a bug report using the process described in [[Reporting_Bugs_against_Xen_Project]]. |
|||
Also see: |
|||
* Short video overview: [https://www.youtube.com/watch?v=qdJi18VekEY&feature=youtu.be XM to XL: A Short, But Necessary, Journey] |
|||
== xl Upgrade Checklist == |
|||
* Configure your host networking using the configuration tools provided by your distribution. (See: [[Network_Configuration_Examples_(Xen_4.1+)]]) |
|||
* Remove any python code from domU configuration files. |
|||
* Disable xend startup script (if testing on Xen 4.4 or lower) |
|||
* Use <code>xl</code> command instead of <code>xm</code> |
|||
= New Feature Highlights = |
|||
{{TODO|Similar to Xen_Project_4.4_Release_Notes}} |
|||
= Build Requirements = |
|||
{{TODO|Similar to Xen_Project_4.4_Release_Notes}} |
|||
= Other changes = |
|||
{{TODO|Similar to Xen_Project_4.4_Release_Notes}} |
|||
= Known issues = |
|||
{{TODO|Similar to Xen_Project_4.4_Release_Notes}} |
|||
[[Category:Xen]] |
|||
[[Category:Release Notes]] |
|||
[[Category:Users]] |
|||
[[Category:Xen 4.5]] |
[[Category:Xen 4.5]] |
||
Revision as of 15:11, 22 December 2014
|
To Do:
Create from last relevant RC mail |
Overview
|
|
To Do:
Similar to Xen_Project_4.4_Release_Notes#Overview |
xm/xend have been removed
In Xen 4.5, the XM toolstack has been removed and been replaced by XL. XL has been designed to be backwards compatible with existing [{XM]] domain configuration files and command line syntax. It is therefore expected that any existing configurations should work with XL with the following exceptions:
- Arbitrary embedded python is not supported. Therefore it will be necessary to remove any python code from your configuration files.
- Managed domains (e.g.
xm vm-create,xm vm-startetc) are not supported byxl. Other toolstacks which support managed domains are the XAPI toolstack and Libvirt. xldoes not support thew!notation to share disks between several DomU's- For a complete comparison see XL vs Xend Feature Comparison
The other notable difference is that xl, unlike xend, will not perform any host networking configuration for you. The xend code to reconfigure on startup is extremely fragile, prone to bugs when either distro or Xen are upgraded and rather difficult to debug. Instead xl takes the approach of deferring such network configuration to the distribution configuration tools which are usually well understood and documented. Therefore upon upgrading to xl it is necessary to configure your host networking stack appropriately. Please see Network_Configuration_Examples_(Xen_4.1+) for more details on how to do this.
xl is designed to be compatible with xm, except for the cases listed above. If you find a situation where xl seems to be incompatible, please file a bug report using the process described in Reporting_Bugs_against_Xen_Project.
Also see:
- Short video overview: XM to XL: A Short, But Necessary, Journey
xl Upgrade Checklist
- Configure your host networking using the configuration tools provided by your distribution. (See: Network_Configuration_Examples_(Xen_4.1+))
- Remove any python code from domU configuration files.
- Disable xend startup script (if testing on Xen 4.4 or lower)
- Use
xlcommand instead ofxm
New Feature Highlights
|
|
To Do:
Similar to Xen_Project_4.4_Release_Notes |
Build Requirements
|
|
To Do:
Similar to Xen_Project_4.4_Release_Notes |
Other changes
|
|
To Do:
Similar to Xen_Project_4.4_Release_Notes |
Known issues
|
|
To Do:
Similar to Xen_Project_4.4_Release_Notes |
