Description of problem: $ virt-install \ --transient \ --name=tmp-jffrn1m6 \ --ram=4096 \ --arch=armv7l \ --features pae=on \ --vcpus=1 \ --os-variant=fedora34 \ --initrd-inject=fedora-34-armv7l.ks \ --extra-args="inst.ks=file:/fedora-34-armv7l.ks console=tty0 console=ttyAMA0,115200 rd_NO_PLYMOUTH" \ --disk=/home/rjones/d/guestfs-tools/builder/templates/tmp-jffrn1m6.img,size=6,format=raw \ --location=https://mirror.bytemark.co.uk/fedora/linux/releases/34/Server/armhfp/os/ \ --serial=pty \ --nographics The kickstart is fairly uninteresting but I'll attach it. This fails at the dracut stage. Inside the rescue shell we can see that there are no virtio devices, because no PCI devices. Version-Release number of selected component (if applicable): virt-install-3.2.0-3.fc34.noarch qemu-6.1.0-5.fc36.aarch64 How reproducible: 100% Steps to Reproduce: 1. See above
Created attachment 1822773 [details] dmesg output I should note the --features pae=on flag seems to make no difference. There is a weird error in the attached dmesg output: [ 11.737291] pci-host-generic 4010000000.pcie: host bridge /pcie@10000000 rang es: [ 11.741242] pci-host-generic 4010000000.pcie: IO 0x003eff0000..0x003eff ffff -> 0x0000000000 [ 11.745955] pci-host-generic 4010000000.pcie: MEM 0x0010000000..0x003efe ffff -> 0x0010000000 [ 11.750621] pci-host-generic 4010000000.pcie: MEM 0x8000000000..0xffffff ffff -> 0x8000000000 [ 11.755398] pci-host-generic 4010000000.pcie: can't claim ECAM area [mem 0x10000000-0x1fffffff]: address conflict with pcie@10000000 [mem 0x10000000-0x3efeffff] [ 11.762959] pci-host-generic: probe of 4010000000.pcie failed with error -16 I previously tried with less RAM (2G or 3.5G) and it made no difference.
Created attachment 1822774 [details] fedora-34-armv7l.ks
Seems very similar to bug 1633328. "virt-install --machine virt-2.11" workaround still works.
*** Bug 1633328 has been marked as a duplicate of this bug. ***
Another more direct workaround would be to use qemu's -machine highmem=off flag. However virt-install doesn't support passing this flag, and I'm not clear that libvirt does either.
Rich did the VM use uefi? I think nowadays fedora arm32 -M virt UEFI is basically required. virt-install will prefer it if it's available. Need to install edk2-arm I just added a Requires: edk2-arm to qemu-system-arm in f36+, that was missing. And yeah, highmem= flag was never added to libvirt
I don't know the answer, but ... I'm going to close this because I was trying to build a 32 bit armv7 Fedora image for virt-builder. 32 bit armv7 is now dead in Fedora >= 37.