FS#73214 - Latest ArchLinux 2022.01.01 ISO will not boot automatically in EFI (on Virtualbox)
Attached to Project:
Arch Linux
Opened by Jilles Groenendijk (jilles_com) - Saturday, 01 January 2022, 13:45 GMT
Last edited by David Runge (dvzrv) - Tuesday, 01 February 2022, 17:36 GMT
Opened by Jilles Groenendijk (jilles_com) - Saturday, 01 January 2022, 13:45 GMT
Last edited by David Runge (dvzrv) - Tuesday, 01 February 2022, 17:36 GMT
|
Details
Description:
Latest ArchLinux 2022.01.01 will only EFI boot manually in EFI Shell using "Shell> FS1:\EFI\BOOT\BOOTx64.EFI" (on Virtualbox). * Source: http://ftp.nluug.nl/os/Linux/distr/archlinux/iso/2022.01.01/archlinux-2022.01.01-x86_64.iso * SHA1 hash: efc9c33087e756ba1c7f326e67bfaa685eb51be3 archlinux-2022.01.01-x86_64.iso Steps to reproduce: * Virtual Box: Windows Version 6.1.30 r148432 (Qt5.6.2) * Chipset: PIIX3 * Enable I/O APIC * Enable EFI * CDROM Controller IDE/PIIX4 |
This task depends upon
Closed by David Runge (dvzrv)
Tuesday, 01 February 2022, 17:36 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with installation medium 2022.02.01
Tuesday, 01 February 2022, 17:36 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with installation medium 2022.02.01
After trying it, systemd-boot launches fine, but only shows the automatically generated boot entries (EFI Shell and Reboot Into Firmware Interface). The manual boot entries (from loader/entries/) are missing.
This appears to be a systemd bug introduced in v250.
Someone should report this regression to the systemd project: https://github.com/systemd/systemd/issues
But really, you shouldn't use VirtualBox these days. On Linux just use QEMU (libvirt/virt-manager) and on windows you're best option is Hyper-V (unless you don't mind launching/managing QEMU yourself).
Is everybody ok closing this now?
I cannot find it either.
It certainly has been a pain to try and get qemu to work on windows as compared to Linux is a breeze. I think this thread can end here now.