Beginning with VirtualBox 6.1.14, which is the current version, I find that this problem has been resolved, even when running most Arch-based distros as a VirtualBox guest. I first updated VirtualBox and the VirtualBox Extension Pack on the host, and updated VirtualBox Guest Additions on the guest:
On the host, I performed a normal pacman update to bring VirtualBox to version 6.1.14.
On the host, I downloaded Oracle_VM_VirtualBox_Extension_Pack-6.1.14-140239.vbox-extpack from the Oracle site, and installed it via the VirtualBox GUI.
With VBoxSVGA temporarily set as the graphics controller, and with 3D Acceleration temporarily disabled, I booted into my Arch-based guest.
On the guest, I performed a normal pacman update to bring VirtualBox Guest Additions to version 6.1.14.
I shut down my Arch-based guest, set the graphics controller to VMSVGA, enabled 3D Acceleration, and booted again into my Arch-based guest.
Everything worked perfectly in the guest, including 3D acceleration. In particular, window manager effects worked. No trickery was necessary to keep these VirtualBox graphics settings (as had been necessary with prior versions of VirtualBox).
I find that all of these distros now work without problem (with VMSVGA and 3D Acceleration enabled) as VirtualBox guests:
EndeavourOS Xfce
EndeavourOS Cinnamon
ArchLabs Openbox
Manjaro Xfce
Only this distro fails to load its desktop completely with VMSVGA and 3D Acceleration enabled:
Manjaro KDE
As Manjaro KDE loads on the virtual machine, this message is displayed: āFailed to start VirtualBox Guest VMSVGA resize client.ā A similar issue (but with Xfce) was reported by another user on the Manjaro forums, but no solution has yet been offered:
I havent tried Manjaro in a long time. I used to run Manjaro Cinnamon. Anyway you may be right mostly that the settings stay but i tend to go into the settings after creating a vm and shutting down. I do that which is not always necessary but i do anyway to remove the optical drive. Thatās when i find the setting for the graphics reverts back to default. Once itās all set and you start a vm it wonāt change unless you go back in to those settings. Thatās my experience with it anyway and Iāve been using it for years. Not that i know anything because i know little in the world of Linux. Itās like a galaxy! I will have to try Manjaro though and see. Originally I used to always use VboxVGA but now i use VBoxSVGA.
Iāll have to also try this also:
I shut down my Arch-based guest, set the graphics controller to VMSVGA , enabled 3D Acceleration , and booted again into my Arch-based guest.
So, I struggled a bit. Only caught the full size icon once, but it worked. It requires hyperspeed to catch it lol.
I then tried VBOXVGA and enabled both accelerations (VBOXSVGA only has 3d acceleration). When I was able to install guest editions from the bottom VB panel they went to full size.
I tried installing Manjaro, just to see the changes and it wouldnāt boot, all sorts of errors.
But Linux Mint worked fine
I was also experiencing lots of errors with most guests, but I found that the errors went away after I installed Oracle_VM_VirtualBox_Extension_Pack-6.1.14-140239.vbox-extpack. VMSVGA and 3D Acceleration work for me now with all guests except Manjaro KDE.
Manjaro KDE installs then during installation it throws a bunch of errors that fill the screen very fast. Iām not to bothered by that, donāt really care for Manjaro. I tried Linux Mint, it worked fine and full screen.
I tried Garuda, easy full screen but the KDE version is very heavily themed, so I got to try it out. Fedora is the hardest one I tried, that bugger wont go to full screen no matter what I do.
@Alexander
I did an install of KDE Plasma also just to show you and there were no errors or any issues installing in Virtualbox and is full screen. The resolution currently on this machine is 1680x1050 When installing in virtualbox i always start the installer and when it starts the install i maximize the box. Then as the install starts i click on the view tab in virtual box and wait until the view virtual screen becomes available and i set the resolution. Then it automatically changes at a certain stage. It just works for me and i find this easier than some other ways such as the display settings or using xrandr. This works 99.9% of the time on most distros if you are using VBoxSVGA and setting it as i explained in my earlier post.
Edit: I do not do anything with inserting guest additions cd image if thatās where you say you are getting errors.
I wish there was an easy way to post a video. Maybe Iāll post one off my google drive just so you can see exactly how i set the settings and go through the install. Others may do things differently but this is the way i use virtual-box and i donāt have any issues. I like it because i can set full screen and still have my host taskbar at the bottom or if i want i can go full full screen and cover that too.
Thank you!
So far in the first 2 minutes, I see huge differences in the way I did it and you do it. Iāll finish the video and begin a new install copying your steps.
Yes it is important at the end of the video once the vm is installed to shutdown Virtual-Box and remove optical drive in settings and set VBoxSVGA. Then boot into the newly installed vm and you should be good and it will keep those settings so long as you donāt go into the settings of that particular vm. If you do you must reset the VBoxSVGA because it will revert to default which doesnāt work.
Edit: The reason i do this is because you are no longer booting from the ISO when you start the vm. You are booting from the virtual drive you created and installed to. This way it wonāt try to boot the iso which also can happen sometimes if you are mucking about so to speak.
I donāt seem to have a choice in the drop down menu to enable 1920x1080 like you have, it stays greyed out. I made sure I followed your steps (just used Fedora Cinnamon instead). Itās mind boggling.
May i ask what you current resolution is set at on the installed system. Not sure what desktop you are on? You can check that because it may need to be set to that because virtual-box may not go to a resolution that is higher than the host? Iām not sure?
Iām on 1920X1080
One other difference is that on systemā>processorā>extended features, you were able to click on both PAE/NX and the next one, Nested something, on mine that second option is not selectable, I wonder If this has something to do with it?
Iām not sure why itās not showing in the list if you have it set to that. You may be able to set it in virtual-box using xrandr. Just look at the man pages.
man xrandr
xrandr command will show what it is capable of. Some resolutions can be added.
