Known Issues

A complete list of known issues for OpenNebula is maintained here.

This page will be updated with relevant information about bugs affecting OpenNebula, as well as possible workarounds until a patch is officially published.

Drivers - Virtualization

libvirtd restarts in cycles each 10 minutes with error message in system logs, due to the way libvirtd gets activated per interaction by systemd in 120-second slices. As the default interval for the OpenNebula monitor probe is 600 seconds (10 minutes), each time a probe reactivates libvirtd, it sends those messages to syslog.

Sunstone

Guacamole RDP as is currently shipped in OpenNebula does not support NLA authentication. You can follow these instructions in order to disable NLA in the Windows box to use Guacamole RDP within Sunstone.

Migration

When upgrading to 7.0 the onedb migration might fail if the /etc/one/sunstone-views.yaml file contains a single, unclosed value under the labels_groups key, example:
```
labels_groups:
  default:
```
This can be mitigated by declaring an empty array as the value instead, example:
```
labels_groups:
  default: []
```

Install Linux Graphical Desktop on KVM Virtual Machines

OpenNebula uses the cirrus graphical adapter for KVM Virtual Machines by default. It could happen that after installing a graphical desktop on a Linux VM, the Xorg window system does not load the appropriate video driver. You can force a VESA mode by configuring the kernel parameter vga=VESA_MODE in the GNU GRUB configuration file. Here you can find the VESA mode numbers. For example, adding vga=791 as kernel parameter will select the 16-bit 1024×768 resolution mode.

Backups

Ceph Incremental Backups: Currently, incremental backups cannot be flattened. Support for this functionality is under development and is expected to be included in the next maintenance release.

Market proxy settings

The option --proxy in the MARKET_MAD may not be working correctly. To solve it, execute systemctl edit opennebula and add the following entries:

[Service]
Environment="http_proxy=http://proxy_server"
Environment="https_proxy=http://proxy_server"
Environment="no_proxy=domain1,domain2"

Where proxy_server is the proxy server to be used and no_proxy is a list of the domains or IP ranges that must not be accessed via proxy by opennebula. After that, reload systemd service configuration with systemctl daemon-reload and restart opennebula with a systemctl restart opennebula

We value your feedback

Was this information helpful?

Glad to hear it

Sorry to hear that