Bug #3841

Drivers for xen4 should use xl or xm toolstack depending on /etc/default/xen and not on the version

Added by Hector Sanjuan about 6 years ago. Updated almost 6 years ago.

Status:ClosedStart date:06/15/2015
Priority:NormalDue date:
Assignee:Javi Fontan% Done:


Category:Drivers - MonitorEstimated time:2.00 hours
Target version:Release 4.14
Resolution:wontfix Pull request:
Affected Versions:OpenNebula 4.12


Even though it is not the default, it is still possible to use xm as toolstack in Xen. The correct toolstack is defined in /etc/default/xen

When a different toolstack is configured than what OpenNebula assumes, errors happen because commands return with: ERROR: A different toolstack (xl) have been selected!


#1 Updated by Hector Sanjuan about 6 years ago

I have added a pull request: https://github.com/OpenNebula/one/pull/60

#2 Updated by Ruben S. Montero about 6 years ago

  • Status changed from Pending to New
  • Assignee set to Javi Fontan
  • Target version set to Release 4.14


#3 Updated by Javi Fontan about 6 years ago

Can this be fixed using xen3 drivers? The name may be misleading but the difference is that xen3 uses xm and xen4 uses xl. We've tested hosts with Xen 4.x and xm tools using xen3 drivers.

Maybe the name should be xen-xm and xen-xl.

#4 Updated by Hector Sanjuan almost 6 years ago

It probably can be fixed like that... however, if that is the only difference, there is no use in having 2 different xen drivers and they should just autoselect the toolstack just as xen does (xen-toolstack command or so).

In my case, since we are upgrading xen and eventually switching from XM to XL, it's easier to assume opennebula will just select the right one...

#5 Updated by Javi Fontan almost 6 years ago

  • Status changed from New to Closed
  • Resolution set to wontfix

We are going to deprecate Xen 3 drivers (xm) in 5.0 release so we think it's better not to change the code of the drivers. When the nodes get upgraded the driver can be reconfigured in oned.conf keeping the same name. This way the hosts don't need to be edited.

If you're doing the migration host by host you can copy the files from xen3 drivers to xen4 and only update the nodes using xl.

Also available in: Atom PDF