Fedora 22 for AArch64
The Fedora ARM Team is pleased to announce the release of Fedora 22 for AArch64, ready to run on your next generation servers. Fedora 22 is a game-changer for the Fedora Project, and we think you're going to be very pleased with the results.
Highlights in the Fedora 22 AArch64 Release
Fedora 22 Server
The Fedora Server flavor is a common base platform that is meant to run featured application stacks, which are produced, tested, and distributed by the Server Working Group. Want to use Fedora as a Web server, file server, database server, or platform for an Infrastructure-as-a-Service? Fedora 22 Server is for you.
Fedora Server Management Features
The Fedora Server flavor introduces new Server management features aimed at making it easier to install discrete infrastructure services. The Fedora Server introduces three new technologies to handle this task, rolekit, Cockpit, and OpenLMI.
Rolekit is a Role deployment and management toolkit that provides a consistent interface to administrators to install and configure all the packages needed to implement a specific server role. Rolekit is at an early stage of development in Fedora 22.
Cockpit is a user interface for configuring and monitoring your server or servers. It is accessible remotely via a web browser.
OpenLMI is a remote management system built atop DMTF-CIM. Use OpenLMI for scripting management functions across many machines and for querying for capabilities and monitoring for system events.
Domain Controller Server Role
As part of the server role offerings available for Fedora 22, the Server flavor ships with a role deployment mechanism. One of the roles offered in 22 is the Domain Controller Service.
The Domain Controller Service packages freeIPA's integrated identity and authentication solution for Linux/UNIX networked environments.
A FreeIPA server provides centralized authentication, authorization, and account information by storing data about users, groups, hosts, and other objects necessary to manage the security aspects of a network of computers.
Mirror List
Supported Hardware
- Applied Micro X-Gene (Mustang)
- Advanced Micro Devices Opteron A1100 (aka Seattle)
Overview of Hardware Support Status
| Hardware | ACPI | Network | USB | DVD | Display | Audio | Link | Notes |
|---|---|---|---|---|---|---|---|---|
| Advanced Micro Devices Opteron A1100 (Seattle) |  |
|
Tested with 74E firmware. | |||||
| Applied Micro X-Gene (Mustang) | |
|
 |
Tested with APM Tianocore - 1.15.10. | ||||
Network Installation
A network installation is the preferred installation method for current Aarch64 hardware targets. In order to begin you will need to setup the installation server, a guide can be found below:
http://docs.fedoraproject.org/en-US/Fedora/22/html/Installation_Guide/chap-pxe-server-setup.html
The above documentation references grubx86.efi, but this is the name for x86_64 EFI grub binaries. The grub binary name on AArch64 systems is grubaa64.efi.
Once configured use the Fedora 22 AArch64 installation tree below:
Installation Tree
http://dl.fedoraproject.org/pub/fedora-secondary/releases/22/Server/aarch64/os/
Install with QEMU
You will need to use qemu-2.3.0-4.fc22+ for the below to work.
To use Fedora 22 on QEMU you will need to use a build of UEFI that is not hosted by Fedora for licensing reasons. For convenience a yum repository had been created
curl -O https://www.kraxel.org/repos/firmware.repo; sudo mv firmware.repo /etc/yum.repos.d/ sudo yum install edk2.git-aarch64 libguestfs-tools-c
To install:
sudo virt-install \
--name Fedora_22 --ram 2048 --arch aarch64 \
--boot loader_ro=yes,loader_type=pflash,loader=/usr/share/edk2.git/aarch64/QEMU_EFI-pflash.raw,nvram_template=/usr/share/edk2.git/aarch64/vars-template-pflash.raw \
--disk size=8 --os-variant fedora22 \
--location http://dl.fedoraproject.org/pub/fedora-secondary/releases/22/Server/aarch64/os/
For a full list of QEMU installation options and instrucions:
http://fedoraproject.org/wiki/Architectures/AArch64/Install_with_QEMU
Reported Bugs and Known Issues
- When using an encrypted partition, "plymouth.enable=0" must be added to the kernel command line. Failure to do so will not allow the passphrase to be entered to unlock the encrypted partition. (BZ#1172740).