kyrios wrote: ↑
Sun Jul 01, 2018 11:50 am
This problem was fixed quite a while ago. This should work (I don't have windows to test but the host shouldn't really matters) :
Thank you! This really helped me, even though I had to make some adjustments. So far I used to build virtualbox drivers from guest additions CD manually.
In order to use existing Solus image all you need to do:
1) update host to Virtualbox 5.2.12 (not sure if even this is necessary)
2) uninstall any old guest additions as instructed at https://solus-project.com/articles/soft ... ualbox/en/
3) Optional: uninstall linux-current kernel (while the bug kyrios mentioned is not fixed)
4) install lts kernel
6) 'sudo eopkg it virtualbox-guest'. This is important! Do not install virtualbox-guest-current as it requires linux-current. On lts kernel you need to use virtualbox-guest.
Now graphics should work as well as well as shared folders, shared clipboard etc. The key point is not to manually build guest additions but to use Solus package insteads. Should have tried already, but luckily there is no need to build your VM images from scratch.
EDIT: Yes this works on Windows host with Virtualbox 5.1.30 (you may skip step 1 above). This is important because of the audio bug: https://www.virtualbox.org/ticket/17225
. Since VB 5.1.30, the audio playback has been broken on Windows host with Linux and Windows guests.
Virtualbox users are punished hard, many will be seeking for alternatives. The other critical is already mentioned https://www.virtualbox.org/ticket/17827
and yesterday's release 5.2.14 made no difference...