They even went as far as making it impossible to save the vm if you had your guest os as linux and graphics set to vboxsvga - in that regard they changed it upon save so it reverted to vmsvga. Several years ago - there was huff&puff with virtualbox where one had to use vboxsvga to get guest resizing - but upstream virtualbox stated very clearly that vboxsvga and vboxvga was intended for windows guests and vmsvga was for linux guests.

I am a t loss here - one side it is great you can work around it - on the other side it is a really strange issue. I guess it should have been mentioned that WINDOWS is the HOST! Is virtualbox-ext-oracle installed? (nevermind, turns out it is a Windows host)Īre the appropriate virtualbox-host-modules installed?( N/A windows host)Īre you a member of the vboxusers group? (nevermind, turns out it is a windows host) VboxSVGA is what works here on a Windows VM.ĭid you install the distribution version of virtualbox? (N/A -windows host) In both Arch-centric VM’s, virtualbox-guest-utils is installed (on guest) otherwise scaling via Ctrl-F does not work. All the other display options for the two Arch based distros result in “Invalid Settings Detected”. On both the Enable 3D Acceleration are unchecked.

Both are set at VMSVGA in display settings and in both instances the setting persists. I don’t have Manjaro installed as a guest, but I do have Arch and EndeavourOS installed as guests. There should be no reason to have to enter sudo VBoxClient–vmsvga to make VMSVGA work.

Install virtualbox linux