summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxengineering <me@xengineering.eu>2025-10-15 18:49:31 +0200
committerxengineering <me@xengineering.eu>2025-10-15 18:49:31 +0200
commitbc6bf0d877781fe1648b40cbc27a1c719f458172 (patch)
tree014893618f27a8cd1805192ef134082f16143936
parent4ef4cb49bf5e8a49c814695763f3aabfce9168ad (diff)
downloadwebsite-uefi.tar
website-uefi.tar.zst
website-uefi.zip
WIP: articles: arch-installation: Switch to UEFIuefi
TODO: Does not work properly in Qemu with console instead of graphical output. Since it is very annoying to type in commands by hand (required for graphical output) this is a problem.
-rw-r--r--content/articles/arch-installation.md19
1 files changed, 12 insertions, 7 deletions
diff --git a/content/articles/arch-installation.md b/content/articles/arch-installation.md
index 5da4b22..bf56805 100644
--- a/content/articles/arch-installation.md
+++ b/content/articles/arch-installation.md
@@ -20,29 +20,30 @@ file which can be written to a physical drive like an USB stick or SSD.
The installation is based on the following design decisions.
-- MBR-based partition table and BIOS / legacy boot
+- GPT-based partition table and UEFI boot
- full disc encryption
- Btrfs filesystem
- only a minimalistic set of installed packages (no graphical environment)
-Those might change in the future. A GPT-based partition table and a UEFI boot
-based on a unified kernel image would be appreciated to support secure boot but
-could not be achieved so far.
+Support for secure boot is appreciated but not yet implemented.
#### Installation
First a virtual drive is created as a file as a starting point for the VM
-installation.
+installation. Additionally a copy of the UEFI variable file of [OVMF][4] is
+copied to allow independent modifications.
```
qemu-img create -f qcow2 archlinux.qcow2 8G
+cp /usr/share/edk2/x64/OVMF_VARS.4m.fd .
```
It is expected that the Arch Linux `*.iso` installation image is downloaded,
verified and saved in the same folder. See the [download page][3] for details.
The installation image can be booted with `qemu-system-x86_64`. The just
-created virtual machine disk is attached as an additional drive.
+created virtual machine disk, UEFI variables and UEFI firmware are attached as
+additional drives.
```
qemu-system-x86_64 \
@@ -50,9 +51,12 @@ qemu-system-x86_64 \
-m 4G \
-nic user,model=virtio \
-drive file=archlinux.qcow2,media=disk,if=virtio \
+ -drive if=pflash,format=raw,readonly=on,file=/usr/share/edk2/x64/OVMF_CODE.4m.fd \
+ -drive if=pflash,format=raw,file=OVMF_VARS.4m.fd \
-smp cpus=4 \
- -nographic \
-boot order=d \
+ -serial mon:stdio \
+ -nographic \
-cdrom archlinux-*.iso
```
@@ -240,3 +244,4 @@ With this step the installation is finished.
[1]: https://archlinux.org/
[2]: https://wiki.archlinux.org/title/Installation_guide
[3]: https://archlinux.org/download/
+[4]: https://github.com/tianocore/tianocore.github.io/wiki/OVMF