What’s New in 6.4

OpenNebula 6.4 ‘Archeon’ is the third stable release of the OpenNebula 6 series. The most exciting addition to ‘Archeon’ is the ability to automatically deploy and manage HCI Clusters based on Ceph—the powerful open source software-defined storage solution. This new native hyperconverged infrastructure architecture can be deployed on-premises (just minimal OS and SSH access is required) and also on AWS bare-metal resources, which gives your hybrid OpenNebula Cloud great flexibility. And, of course, you can dynamically add more hosts to your cloud whenever you need to, as well as seamlessly repatriate your workloads from AWS at any time.

This release already comes with a fully-functional new Sunstone interface (FireEdge Sunstone) for managing VM templates and instances, with a similar coverage in terms of features as the traditional Cloud View present in the earlier version of Sunstone, save for the OneFlow integration. If you are a cloud admin, please keep using the ruby-based Sunstone interface (port 9869) but encourage your end-users to migrate to the new Sunstone portal served in port 2616. Our development team has worked hard to streamline the functionality offered in the VM and VM Template tabs, and more UX improvements are on the way, so stay tuned! The old, ruby-based interface also received its share of love, adding all the functionality that OpenNebula incorporates in this new version 6.4.


This new release also includes the notion of network states. Your virtual networks will have states that will allow you to perform custom actions upon creation and destruction of instances, offering a better integration with your datacenter networking infrastructure. Events changing the state of your virtual networks can be tied to the execution of hooks to further tune the behavior of your cloud. There are two components that benefit from this change: OneFlow can now synchronize the creation of virtual networks and service VMs, while vCenter networking does not require any longer the activation of a hook.

There are also a number of additions to the supported hypervisor family, like the new SR-IOV support for the NVIDIA GPU cards and the addition of fine-grain resource control to the LXC driver. The integration with vCenter has also been improved, including the support for filtering and ordering those resources to be imported, the automatic VM Template creation for marketplace appliances, and the ability to set a default prefix for VM names, among others. Performance-wise, the vCenter driver is now more robust in large scale deployments, optimizing memory usage.

OpenNebula 6.4 is named after the Archeon Nebula, located in the Lothal sector of the Outer Rim Territories—a beautiful body of interstellar clouds where stars are born and which provides a popular hyperscape route for smugglers traversing the continuum towards the edge of the Star Wars universe :)

OpenNebula 6.4 ‘Archeon’ is considered to be a stable release and as such it is available to update production environments.

We’d like to thank all the people that support the project, OpenNebula is what it is thanks to its community. Apart from the usual acknowledgements, we’d like to highlight the support we’ve received through the EU-funded H2020 project ONEedge.

OpenNebula Core


vCenter Driver

Ruby Sunstone

FireEdge Sunstone

OneFlow - Service Management


  • New commands to attach/detach Security Group to Virtual Machine

  • New command onevnet recover to recover Virtual Network from locked or error state.

  • New commands oneirb and onelog, also a new sub-command vnc added to onevm.

Distributed Edge Provisioning


  • NVIDIA vGPU support has been added to KVM driver, check this for more information.

  • VM resource assignment supports cgroups version 1 and 2

  • (*) Better live memory resize for KVM. Note: You need to do a power cycle for those VMs you want to resize its memory after the upgrade.


Other Issues Solved

Features Backported to 6.2.x

Additionally, a lot of new functionality is present that was not in OpenNebula 6.2.0, although they debuted in subsequent maintenance releases of the 6.2.x series:

(*) This functionality is present also in previous EE maintenance versions of the 6.2.x series.