I wanted to test Fedora 40 KDE Spin on VirtualBox, installed on Windows 11 Pro 22631.3447, but it failed to boot.
I used the latest VirtualBox 7.0.16, created new VM with default Fedora template (same problem after increasing RAM and CPU), mounted Beta 1.10 iso image and tried to launch.
During boot, it stopped at some point. I restarted, changed kernel parameters (replaced ‘quiet rhgb’ with ‘verbose’), pressed F10. It got into drkonqi-coredum loop.
I tried 1.14 ISO, but it got into dark screen black screen with single cursor.
I tested both releases with safe graphics mode option:
iso 1.10 - drkonqi-coredum loop (same like in normal mode)
iso 1.14 - works (in normal mode - black screen with single cursor)
As far as I know virtualbox will not work trying to run guests using wayland.I tried to install the beta awhile back in virtualbox and it would not work.It did install and work well using gnome boxes.I have Arch and EndeavourOS KDE running as guests in virtualbox and they still have the option to use xorg so they both work well.Neither will boot trying to use wayland.
This is because beta 1.10 compose is from March 21st and the updated gcc build is only from April 12th or so (see https://bugzilla.redhat.com/show_bug.cgi?id=2272758#c53)
Unfortunately, the beta download on getfedora isn’t updated to link to the latest RC iso. It gets published once and therefore fixes from the Freeze phase don’t land in the publicly available beta image.
).