Xfce installation medium not loading/starting properly on virtualbox hosted on windows

Support Virtualization
, ,
1

Hi,
I’m trying to install manjaro xfce from manjaro-xfce-26.0-260104-linux618.iso on virtualbox Version 7.2.4 r170995 (Qt6.8.0 on windows). My virtualbox runs on windows 10 home, version 22H2, build 19045.6456. I start the virtual machine with the iso inside, expecting to see at a certain point some screen to install manjaro (or the live manjaro startup with a window letting me install the os on the hard disk of the vm).
I’ve already verified the checksum of the distribution. My virtual machine has 6 Gb of Ram, 128Mb of graphics card (no 3d enabled), 2 cpus, hd of 40 Gb.
What happens is that the startup process hangs somewhere with the splash screen iterating indefinitely. If I hit ESC during the startup I can see what is printed on the screen: it seems to hang when trying to start Light Display Manager, because at a certain point it continues to print:

(1 of 2) A start job is running for Hold until boot process finishes up ← many times
(2 of 2) A start job is running for light display manager ← every so and so

What can I do to startup correctly the system and eventually manjaro on the virtual machine ? Or maybe is there something to be fixed in the distro software ?
Thanks in advance

2

It is impossible to say.

There has been several topics on the matter of issues boot XFCE iso, but the issue has never been replicated.

I am thinking the ISO may be somewhat incomplete, they are quite large (blame Nvidia drivers), so did you do a sanity check on the ISO using a signature check and sha256sum check before booting the ISO?

VirtualBox may exhibit strange behavior, and in such case it is suggested to press e on the grub item, then remove splash and quiet from the kernel command line then press F10 to continue booting.

Over the years there have been many issues related to the use of Plymouth splash screen. Some seems to see it as a necessity, while other love to hate it.

Either way Plymouth is used and may occasionally cause an issue like yours when executed in a VirtualBox VM.

1 Like