[fedora-arm] AArch64 Kickstart install failed: "failed to find suitable stage1 device"

[Adam Chance]

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.

Here is my Kickstart script:

#install
#url
--mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$release
ver&arch=$basearch
#
#cmdline
#lang en_GB.UTF-8
#keyboard gb
#timezone --utc Europe/London
#
#selinux --enforcing
#rootpw --lock root
#
#firewall --disabled
#
#bootloader --timeout=1 --append="no_timer_check console=tty1
console=ttyAMA0,115200n8"
#
#network --bootproto=dhcp --device=link --activate --onboot=on
#services
--enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config,clou
d-final
#
#zerombr
#clearpart
#part /boot --fstype=ext4 --size=500 --fsoptions="noatime,discard"
#part /boot/efi --fstype=efi --size=100 --fsoptions="noatime,discard"
#part btrfs.01 --grow --fsoptions="noatime,discard"
#btrfs none --label=fedora btrfs.01
#btrfs / --subvol --name=root fedora
#btrfs /home --subvol --name=home fedora
#
#poweroff
#
#%packages --excludedocs
#
#kernel-core
#@^cloud-server-environment
#systemd-udev
#
#-dracut-config-rescue
#
#-biosdevname
#-NetworkManager
#-iprutils
#-uboot-tools
#-kernel
#
#efibootmgr
#grub2-efi
#-syslinux-extlinux
#
#%end

And here is my virt-install command:
#virt-install --name Fedora_24_AArch64 --ram 2048 --arch aarch64 --disk
path=cloud_aarch64.img,size=8,format=raw,discard=unmap --location
../Fedora-Everything-netinst-aarch64-24-1.1.iso --extra-args
"inst.ks=https://storage.gra1.cloud.ovh.net/v1/AUTH_cb7a5e3329844fd1a8ab7205
fdc70060/public/scripts/linux/fedora/kickstart/fedora-cloud-base.ks
console=AMA0,115200n8" --boot uefi --noreboot

[Adam Chance]

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.

Here is my Kickstart script:

#install
#url --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
#
#cmdline
#lang en_GB.UTF-8
#keyboard gb
#timezone --utc Europe/London
#
#selinux --enforcing
#rootpw --lock root
#
#firewall --disabled
#
#bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyAMA0,115200n8"
#
#network --bootproto=dhcp --device=link --activate --onboot=on #services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config,cloud-final
#
#zerombr
#clearpart
#part /boot --fstype=ext4 --size=500 --fsoptions="noatime,discard"
#part /boot/efi --fstype=efi --size=100 --fsoptions="noatime,discard"
#part btrfs.01 --grow --fsoptions="noatime,discard"
#btrfs none --label=fedora btrfs.01
#btrfs / --subvol --name=root fedora
#btrfs /home --subvol --name=home fedora # #poweroff # #%packages --excludedocs # #kernel-core #@^cloud-server-environment #systemd-udev # #-dracut-config-rescue # #-biosdevname #-NetworkManager #-iprutils #-uboot-tools #-kernel # #efibootmgr #grub2-efi #-syslinux-extlinux # #%end

And here is my virt-install command:
#virt-install --name Fedora_24_AArch64 --ram 2048 --arch aarch64 --disk path=cloud_aarch64.img,size=8,format=raw,discard=unmap --location ../Fedora-Everything-netinst-aarch64-24-1.1.iso --extra-args "inst.ks=https://storage.gra1.cloud.ovh.net/v1/AUTH_cb7a5e3329844fd1a8ab7205fdc70060/public/scripts/linux/fedora/kickstart/fedora-cloud-base.ks console=AMA0,115200n8" --boot uefi --noreboot

[Peter Robinson]

On Fri, Sep 9, 2016 at 11:22 PM, Adam Chance

Post by Adam Chance
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

[Adam Chance]

My Kickstart was actually modified from the fedora-kickstarts project, but I decided to start again by making modifications to the fedora-kickstarts script. I can't tell what has changed (other than formatting), but the installation now succeeds. I'm not sure why this is, but thank you for your time.