On Fri, Sep 9, 2016 at 11:22 PM, Adam Chance <adam.chance10@xxxxxxxxxxxxxx> wrote: > Hello > > I am trying to install Fedora 24 AArch64 into a VM with virt-install with > a Kickstart script, but Anaconda complains that it could not find a > suitable stage1 device. The kickstart we use for aarch64 cloud [2] images is in the fedora-kickstarts repo works. You'll need to use ksflatten to merge the includes (in pykickstart package). There's also details and and example here [3] I'm not sure what your underlying host is and it only really matter because Fedora-24 was the first to ship with the virtual uEFI firmware for aarch64 and various tools needed to be updated for that. The virt-install command I use with aarch64 is: virt-install -n hostname --memory8 --memballoon virtio --disk bus=virtio,path=volgroup/inventory_hostname --vcpus=4 -l https://dl.fedoraproject.org/pub/fedora-secondary/releases/24//Everything/aarch64/os/ -x 'net.ifnames=0 ksdevice=eth0 ks=ks_url console=tty0 console=ttyAMA0 hostname=inventory_hostname nameserver=8.8.8.8 ip=1.2.3.4::255.255.255.0:1.2.3.254:inventory_hostname:eth0:none --network bridge=br0,model=virtio --autostart --noautoconsole With the versions of virt-install in Fedora 24 and later (or RHEL 7.2 and later) you shouldn't need and of the bits about --boot. I used the above to deploy a whole bunch of Fedora 24 VMs this week so it should all be fine. [1] https://pagure.io/fedora-kickstarts/ [2] https://pagure.io/fedora-kickstarts/blob/master/f/fedora-cloud-base-arm.ks [3] https://fedoraproject.org/wiki/Architectures/AArch64/F24/Installation#Network_Installation _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx
