[SOLVED] No bootable medium found!

Help
1

Downloaded neon-user-20240929-1217.iso today.

Created a new VM in Oracle Virtualbox 7.0.20 r163906 (Qt5.15.2).

The .iso booted up fine. I clicked on the Install and did my usual. The installation went off without incident. At the end I was presented with the All Done. screen (KDE neon 6.0 has been installed on your computer. You may now restart into your new system, or continue using the KDE neon Live environment.) Restart now was checked. I clicked on Done.

The Live session shut down, and the VM was relaunched. But, I was then presented with a pop-up window that said:

“The virtual machine failed to boot. That might be caused by a missing operating system or misconfigured boot order. Mounting an operating system install DVD might solve this problem. Selecting an ISO file will attempt to mount it after the dialog is closed.”

This window is specifically asking for an OS install DVD! Two buttons: Mount and Retry Boot and Cancel.

This window sits on top of a console window that contains:

“No bootable medium found!
Please insert a bootable medium and reboot.”

In all my years of using Oracle Virtualbox for my VMs, I’ve never seen this before.

Anyone else having this issue? Is there something amiss with the .iso?

https://imgur.com/a/vmMMrBx

2

Bottom line, I figured out the issue. KDE neon User Edition, running as a VM in Virtualbox 7.0, on my Desktop PC running Kubuntu 24.04 is now booting just fine.

I had to create a a fat32 /boot/efi partition (I made it 512 MiB) with the boot flag set in addition to the btrfs partition I created. After the installation was finished, I rebooted the VM and everything ran as expected.

When I created KDE neon User Edition VM on my iMac (with Oracle Virtualbox 7.0) back in February, I didn’t have to have a /boot/efi partition; I had to create an 8 MiB unformated partition with the bios-grub flag set.

So clearly something has changed in the installer (?) used by the latest KDE neon builds that now requires a /boot/efi partition, even though not having one created during manual partitioning doesn’t cause the installation to complain.