Comment 5 for bug 2076520

There is only one graphics controller you can select for Linux: VMSVGA
and you can use it with or without 3D acceleration, but it has the same
result. And basically that is the first thing I try in case of any
potential display issue. All my other Linux and older Ubuntu VMs run
fine with this graphics driver.
I do not understand, why Virtualbox is considered an unsupported
hypervisor, since I already use Virtualbox since 2009 with Ubuntu and I
never knew, it was an unsupported hypervisor.

I run the second slowest Ryzen CPU ever and I use it for Virtual
Machines, I don't expect others use VBox VMs on this slow CPU (4C4T;
3.7GHz).
Based on the time I worked on a kernel long ago, I have the feeling,
that we are dealing with a parallel processing problem related to
kernel and virtualbox modules, since it has a timings aspect. Something
like the hypervisor type is not supplied yet by vbox and the kernel
expects it to be present already. On faster CPUs vbox could be in time
to provide the data. Also on faster booting Ubuntu flavors (~7
seconds), the data could be provided mostly on time. But whenever you
have 2 threads working on the same data access must be synchronized to
avoid these type of timing issues.

I can explain the strange behavior, that it boots after the 6th boot by
the fact that I use OpenZFS. So on every run it collects more code in
the 4 GB ZFS memory cache (L1ARC, lz4 compressed) and the next boot is
more from memory and less from the nvme-SSD (3400/2300MB/s). In the
~5th try it did reach the login screen, but it did not login, in the
~6th try I could log in normally. You should also have the log from
this boot as last one and the one I used for journalctl.

Remember I also have occasionally a faulty boot on Ubuntu Budgie 22.04,
but there the second boot is always correct. Some weeks ago, I also had
the problem with 24.10, but there it disappeared.

On Tue, 2024-08-13 at 01:36 +0000, Daniel van Vugt wrote:
> There are several kernel crashes there. And separately vmwgfx seems
> to
> be failing, complaining "*ERROR* vmwgfx seems to be running on an
> unsupported hypervisor". So it's possible the fix here is to choose a
> different virtual graphics card in VirtualBox.
>