In conclusion, I reinstalled it with F31, in my case the virtualization part is a must, so I postpone the upgrade until support for that behavior. The file server implemented for general servers works fine even after uploading to F32. F32 works fine for servers.
You can try VMWare Workstation which inherently provides 3D acceleration by taking a small chunk of RAM and deputing it as the video memory for the virtualized OS. Keep in mind that it has great support for OpenGL and a workable one for Vulkan. Personally, I would not use VirtualBox if 3D acceleration is my priority.
Rolling back to the previous version of Fedora is definitely not a solution. It is just a workaround. Unreliable at that too. You gotta wait for a bit @simmon before the solutions start flowing in.
Dear t0xic0der
I do not use vmware. I considered the basic application system and ease of use, and this is the conclusion after verifying the stability by installing additionally on other equipment. I personally concluded that the F31 I verified was stable on my desktop rather than the unstable F32 system. Other general purpose servers are running great with F32.
I like making videos in virtualbox and testing the operating system.
When 3D acceleration is not supported in the virtual environment in F32, the operation is limited and the system freezes. There is a hassle of going back to the F31, but if the virtualbox is supported on the F32 in the future, I can upgrade.
I’ve been using Fedora for a long time and I think it’s really great in terms of performance.
Prior to running on the F31, I thoroughly tested the stability of the F32, but couldn’t even verify the rpmfusion of the virtualbox. Nevertheless, as of F31, I am writing this article with great satisfaction.
If it is a single server, it uses F32 and always supports the Fedora policy.
