If Elmo #Musk is the world's most hated billionaire than Oracle's #LarryEllison comes in second, as far as I am aware.
#Virtualbox for Linux is one of the biggest P.O.S. programs for Debian Linux. I have a T480 laptop with 1080p resolution. It is a pretty fast machine and everything is set up correctly. I consider myself an expert in Linux GUI on Windows 11 VM's -- kind of a unique area and so what if it is? Linux VM's running on Linux OSes shouldn't be much different, right?
My first hint that the latest iteration of Virtualbox is messed up when installing this on Linux is that a single MOK message came up when running "sudo /sbin/virtualbox" yet there wasn't anything post-install that indicated that I needed to go through the MOK-based steps of registering and then entering in MOK's crypto key password during the host system's boot. I use #Libreboot so that could have been why? Probably not. This is the first #Linux laptop I've owned that uses something besides GRUB. I think Virtualbox's Linux developers forgot to do something regarding MOK.
The last nail in the coffin was Virtualbox's Guest Additions subprogram messing the GUI up after I was able to compile or integrate graphics support directly into the Linux VM's kernel. #NVIDIA started the whole "reversion" or going backwards in time argument over making their video drivers closed and proprietary. The Open Source people really dislike Jensen Huang for this. So, from all the years of recriminations concerning this big fight between the Open Source people who won't take a position and NVIDIA itself; who has a ton of money and a lot more time to waste -- Guest Additions on Virtualbox is a minefield of crap.
When I ran this program it started slowly shrinking my Virtualbox GUI incrementally. I think I need to recalibrate MOK so my system "sees" that Virtualbox's video driver is working properly. I believe Virtualbox's display settings through Debian GNU/Linux is limited to VMSVGA, only. All the other options will not engage, including 3D acceleration.
This is yet another "FU" to the world of Open Source, likely caused in part by others who will not fully and properly maintain some open standard in video drivers. I'm pretty sure I've tried every setting.
PS -- I'm going to check my #MOK configuration again. I don't think something worked the first time like it was supposed to? All the other programs I've used with MOK had something built into said program to run MOK after the fact so when you reboot your system you will then have to take the next step with MOK security. And of course, Oracle's Virtualbox apparently left that one step out because THEY SUCK!