You are not logged in.
I noticed that, starting from the 2026-08 installation ISO, if I boot it under an hypervisor in UEFI mode (both VirtualBox and qemu on Arch itself show this problem) I can get to the console, but during boot one unit fails and this leaves the system in `degraded` state as per `systemctl is-system-running` rather than `running`. The same thing does not happen if I boot in BIOS mode.
This problem alone would not be a roadblock, but I use my own set of installation scripts which expect the system to be in `running` state and this breaks things for me.
The culprit seems to be some instance of `systemd-loop@.service` which tries to mount the ISO somewhere and fails because it says there is no partition table on it.
My current workaround is to mask that service via the kernel commandline when booting VMs: this seems to fix the problem without any (visible) side effect, but I'd like to know why this started happening.
So the question is: where's the correct place to file a report? The documentation points to archiso, but correct me before I open it in the wrong place.
Also, am I the only one hit by this issue?
Offline