

Try closing all the apps before starting your VM. This may not be a solution, but can be called a permanent workaround. If Ubuntu is freezing in Oracle VirtualBox, check out the following solutions to resolve the issue. Sometimes, updating alone can resolve the issue, so, do that and if it didn’t work, move to the solutions. Ubuntu freezing or not starting in VirtualBoxīefore going to the troubleshooting guide, it is important to update your system. Without wasting any time, let us hop into it. If you want a smooth run with Ubuntu, then try the solutions and workarounds mentioned hereinafter. There are some other settings that we are going to make to make the app work. Your VM tries to adjust its performance as per the resources you allocate to it, so, if you feed it fewer resources, it will make sure that it doesn’t crash by dialing down the resources. Talking about resources, when you create the VM, you allocate RAMs, CPUs, etc to it. It needs some resources and when you distribute your CPU, GPU, RAM to other apps as well, VirtualBox is left with scarce resources. If you have a ton of applications running in the background, you can’t be expecting VirtualBox to run smoothly. We are going to resolve this issue with some simple solutions.Ī very logical reason why Ubuntu runs slow on your system is the lack of resources. However, a lot of users are complaining that Ubuntu is freezing in Oracle VirtualBox. A Windows user can enjoy Linux, Mac, and other operating systems. The solution that worked for me was to remove the system level and user level mesa shader cache folders $ sudo rm -rf /var/lib/gdm3/.cache/mesa_shader_cacheĪfter both were removed, the graphical user login screen was displayed on start up and after logging in, the full Gnome desktop created by the original installation was displayed.Virtual Machines are like a gateway to enjoying multiple OSs on a single system. Which led me (via this post) to the mesa_shader_cache. I (eventually) found the significant failure in the journalctl -b log wsone-VirtualBox kernel: traps: gnome-shell trap invalid opcode ip:7f44240a60d3 sp:7ffe59ab40a0 error:0 I was then able to use + to switch to a tty login. In the end there is only a blinking text cursor in the top level corner. After the OS boots with the graphical loading screen the screen turns black, occasionally showing the mouse cursor as multiple attempts to start the Gnome greeter login screen fail.

I'd imported a VirtualBox 6.1.28 OVA for a VM with Ubuntu 20.04.3 Gnome desktop set up for one user. In my case the blank, black screen was not caused by VirtualBox settings, it was the GDM mesa shader cache created by the original Ubuntu installation.
