< Architectures | AArch64
Fedora 21 for AArch64
The Fedora ARM Team is pleased to announce the release of Fedora 21 for AArch64, ready to run on your next generation servers. Fedora 21 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 21 AArch64 Release
Fedora 21 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 21 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 21.
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 21, the Server flavor ships with a role deployment mechanism. One of the roles offered in 21 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.
- Applied Micro X-Gene (Mustang)
- Advanced Micro Devices Opteron A1100 (aka Seattle)
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:
Once configured use the Fedora 21 AArch64 installation tree below:
It is possible to start an installation of Fedora 21 without going through the steps of setting up a PXE server, and rather initiating a network installation through a USB drive formatted appropriately. This may be created using the Fedora 21 installation media provided, or the following prepared image.
Copy the USB image to an appropriate USB device (minimum 128MB USB stick).
MEDIA= # location of your USB device xzcat Fedora-Server-netinst-aarch64-21.img.xz | sudo dd of=$MEDIA bs=4M
Insert the USB device into the bottom port located at the back of the Mustang board (below the network port), power on the machine and interrupt the boot, choosing the 'shell' option. Once at the EFI shell, enter:
FS0:\EFI\BOOT\BOOTAA64.EFI # NOTE - if you recieve an error try - FS1:\EFI\BOOT\BOOTAA64.efi
This will boot the Fedora 21 installer. When prompted, choose either VNC or Text installation. By default the installer will use the Fedora Master Mirror but you can also use the "Closest Mirror" option for best results.
Reported Bugs and Known Issues
- When using an encrypted partition the appropriate console argument must be included on the kernel command line (e.g., for Mustang "console=ttyS0,115200n8" or for Seattle "console=ttyAMA0,115200n8"). Failure to do so will not allow you to enter the passphrase to unlock the encrypted partition. (BZ#1172740).
- At the end of the installation on a Mustang you may receive an error about removing or adding the 'EFI' boot menu entry. If so, type 'yes' to continue the installation, and once rebooted, interrupt the boot process (press any key) and add a boot menu entry as shown below (BZ#1151571):
TianoCore 1.1.0-rh-0.13 UEFI 2.4.0 Oct 28 2014 07:28:29 CPU: APM ARM 64-bit Potenza 2400MHz PCP 2400MHz 32 KB ICACHE, 32 KB DCACHE SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz Board: X-Gene Mustang Board SLIMpro FW : 2.1 The default boot selection will start in 3 seconds  Shell  Boot Manager  Reboot  Shutdown Start: 2  Add Boot Device Entry  Update Boot Device Entry  Remove Boot Device Entry  Set Boot Timeout  Return to main menu Choice: 1  (199 MB) - PciRoot(0x6)/Pci(0x0,0x0)/Sata(0x0,0x0,0x0)/HD(1,GPT,4F55C7E4-DDD6-4060-8C4D-2BC9D3A61B37,0x800,0x64000)  VenHw(6C9CEEF0-A406-11E3-A5E2-0800200C9A66) - VenHw(6C9CEEF0-A406-11E3-A5E2-0800200C9A66)  VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) - VenHw(02118005-9DA7-443A-92D5-781F022AEDBB)  VenHw(F40A3869-92C4-4275-8501-4491A1A20C19) - VenHw(F40A3869-92C4-4275-8501-4491A1A20C19)  VenHw(B225ED30-6DFD-43A9-BF6B-5753358F2F70) - VenHw(B225ED30-6DFD-43A9-BF6B-5753358F2F70)  PXE on MAC Address: 00:11:22:33:44:55 - MAC(2C59E5369A4C,0x1)  PXE on MAC Address: 00:11:22:33:44:56 - MAC(001122334456,0x1)  PXE on MAC Address: 00:11:22:33:44:57 - MAC(001122334457,0x1)  PXE on MAC Address: 00:11:22:33:44:58 - MAC(001122334458,0x1)  TFTP on MAC Address: 00:11:22:33:44:55 - MAC(2C59E5369A4C,0x1)  TFTP on MAC Address: 00:11:22:33:44:56 - MAC(001122334456,0x1)  TFTP on MAC Address: 00:11:22:33:44:57 - MAC(001122334457,0x1)  TFTP on MAC Address: 00:11:22:33:44:58 - MAC(001122334458,0x1)  Return to Main Menu Select the Boot Device: 1 File path of the EFI Application or the kernel: EFI\fedora\grubaa64.efi Is an EFI Application? [y/n] y Is your application is an OS loader? [y/n] y Arguments to pass to the EFI Application: Description for this new Entry: Fedora 21