It is the yaml dependency that was added since we created the VM. We need to create a new one using Ubuntu 18.04 but I never get the time (if anyone wants to give it a try, it is on github .

As for opengl it is odd, I have never seen that. I just installed the VM, launch the update script, "sudo apt-get install python3-yaml" and the client starts fine for me. I am running Virtualbox 5.2.8 on Linux. What host system are you using?

Hi, so I tested on our dev Mac that also run Mojave and the result is quite counter-intuitive: you need to disable 3D acceleration for the VM.

When testing the VM untouched with the latest version of Virtualbox, it works fine. If I enable 3D acceleration in the VM setting then I get the same message as you got.

My assumption is that Linux has a quite good software OpenGL implementation and this is the one that is used if you have 3D disable in the VM. If you enable 3D then it tries to use the 'virtual' OpenGL of the VM and for some reason this does not work (might require newer version of the guest addition maybe).

An update: if you want to activate 3D acceleration on the VM the problem was the guest addition, I updated guest addition and it worked with 3D acceleration activated in the VM. That said, the OpenGL emulation is working very well already so activating 3D on the VM should not be needed.

Thanks for even further investigating this issue, arnaud. I can confirm the cohesion you described.

Since you’re also running Xubuntu 14.04 as guest on macOS Mojave as host—do you have the same severe performance issues in the VM? It’s impossible to work with it due to input lags for keyboard and mouse clicks.

Is there any solution to this? I‘ve already played around with VirtualBox‘ options regarding RAM, video memory, chipset and 3D acceleration without memorable impact.

Does upgrading to a newer version of Xubuntu increase performance of the VM?