Architectures/ARM/AArch64/QuickStart

From FedoraProject

< Architectures | ARM | AArch64(Difference between revisions)
Jump to: navigation, search
(Getting Started with the Aarch64 Bootstrap)
(Aarch64 Quickstart Guide)
(44 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
{{lang|en|zh-cn|page=Architectures/ARM/AArch64/QuickStart}}
 +
[[Category:AArch64]]{{shortcut|Arch:ARM}}
 
=Aarch64 Quickstart Guide=
 
=Aarch64 Quickstart Guide=
This page will help those new to aarch64(armv8) get started with the Foundation Model provided by ARM. The are a number of options available when using the model, including use of a disk image file or NFS root filesystem, as well as a choice of kernel if you would like to use Systemd or Busybox as the init process.  
+
This page will help those new to aarch64 (ARMv8) get started with the Foundation Model provided by ARM. The F19-aarch64-efi tarball provides an F19-based disk image, which includes a kernel, initramfs, and device tree blob, files to support booting the kernel using EFI, and a sample script for starting the model.
  
 
== Download the Foundation Model ==
 
== Download the Foundation Model ==
The first step will be to download the Foundation model from ARM. The model is not redistributable and will therefor require you to create a free account with ARM. Once completed you will be able to download the Foundation Model and begin.  
+
The first step is to download the Foundation model from ARM. The model is not redistributable and will therefor require you to create a free account with ARM. Once completed, you will be able to download the Foundation Model and begin.  
  
 
* [http://www.arm.com/products/tools/models/fast-models/foundation-model.php The Foundation Model]
 
* [http://www.arm.com/products/tools/models/fast-models/foundation-model.php The Foundation Model]
Line 13: Line 15:
 
==Extract the Foundation Model==
 
==Extract the Foundation Model==
  
Once you have downloaded the model, you will need to set up your environment. The model can extracted to a path of your choosing, in this example we will use your home directory.  
+
Once you have downloaded the model, you will need to set up your environment. The model can be extracted to a path of your choosing.  Your home directory will be used in this example.
 +
 
 
Unpack the model:
 
Unpack the model:
  
Line 22: Line 25:
 
== Using the Model with an Image ==
 
== Using the Model with an Image ==
  
{{admon/important|Bug!|There is a bug in the Foundation Model Virtual Disk I/O implementation that makes the model unstableUntil it has been fixed using an NFS root will provide greater stability.}}
+
Using the commands below, download and extract the Aarch64 root filesystem tarball.
 +
 
 +
{{admon/note|Note: The extracted disk image requires approximately 12GB disk spacePlease ensure you have adequate free space.  This may take several minutes to unpack, depending on your hardware.}}
  
Using the commands below, download and extract the Aarch64 root filesystem disk image. The disk image will extract to roughly 8GB in size and may take several minutes to unpack depending on your hardware.
 
 
  cd ~/aarch64
 
  cd ~/aarch64
  wget http://fedorapeople.org/~pwhalen/aarch64/stage4-root-20130423.img.tar.bz2
+
  wget http://dmarlin.fedorapeople.org/fedora-arm/aarch64/F19-aarch64-efi.tar.xz
  tar xvjf stage4-root-20130423.img.tar.bz2
+
  tar Jxvf F19-aarch64-efi.tar.xz
  
Download and extract the kernel package:
+
=== Starting the Model ===
wget http://fedorapeople.org/~pwhalen/aarch64/aarch64-kernels.tar.bz2
+
tar xvjf aarch64-kernels.tar.bz2
+
  
The model can now be launched using the disk image as the root filesystem with the commands below:
+
The kernel supports virtio, so the kernel image, initramfs, and device tree blob included on the image will be used in the boot processYou no longer need to use separate "Kernel Packages".
Systemd:
+
sudo Foundation_v8pkg/Foundation_v8 --image aarch64-kernels/systemd-3.7-image-foundation.axf --block-device stage4-root-20130423.img --network=bridged
+
  Busybox:
+
sudo Foundation_v8pkg/Foundation_v8 --image aarch64-kernels/busybox-3.7-image-foundation.axf --block-device stage4-root-20130423.img --network=bridged
+
  
The model will take a few moments to start. The '''root password is 'fedora', there is also another account called 'builder' password 'builder''''.
+
An example script for starting the model has been included in the tarball.  This script performs the following steps to start the model:
  
==== Network Configuration ====
+
<pre>
 +
sudo ../Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 \
 +
  --cores=1 \
 +
  --visualization \
 +
  --image=linux-system-el3-foundation.axf \
 +
  --data=RTSM_VE_FOUNDATIONV8_EFI.fd@0xA0000000 \
 +
  --block-device `pwd`/aarch64-efi.img \
 +
  --network=bridged \
 +
  --network-bridge=ARM1 &
 +
sleep 5
 +
sudo ifconfig ARM1 10.0.1.1 netmask 255.255.255.0
 +
</pre>
  
After launching the model, sign in using the root account for the network to be auto-configured.
 
  
On the host system:
+
Both console (telnet) and ssh access are supported.  To start the model, change to the F19-aarch64-efi subdirectory and run the script:
sudo ifconfig ARM0 10.0.0.1 netmask 255.255.255.0
+
  
== Using the model with an NFS root ==
+
  cd ~/aarch64/F19-aarch64-efi
 +
  ./efi-aarch64.sh
  
Using the model through an NFS is recommended as it will allow the most flexibility when working with the system. It is important to use the paths provided as the kernel will expect the root file system to be mounted through NFS from the given path.
+
{{admon/note|Note: | You must have 'sudo' access in order to run this script.}}
  
== Setting up an NFS Root Filesystem ==
+
{{admon/note|Note: | The script assumes the foundation model is in:
First you will need to create a directory for the root filesystem. It is important you use the same path in the example as the kernel expects the rootfs to be at the path used below (extracting may take several minutes depending on your hardware):
+
    ~/aarch64/Foundation_v8pkg.
 +
Adjust as necessary for your environment.}}
  
sudo mkdir -p /var/exports/aarch64/stage4-nfs-root
 
cd /var/exports/aarch64/
 
sudo wget http://fedorapeople.org/~pwhalen/aarch64/stage4-root-20130423.tar.xz
 
cd stage4-nfs-root
 
sudo tar xvJf ../stage4-root-20130423.tar.xz
 
sudo mv stage4-root-20130423/* .
 
sudo mv stage4-root-20130423/.profile .
 
sudo rm -rf stage4-root-20130423
 
  
* Now create an NFS share for the rootfs, edit /etc/exports
+
You should be able to ssh to the model once it has fully booted. You can use telnet to connect to the serial console using the provided ports as it boots.
sudo vi /etc/exports
+
/var/exports/aarch64/stage4-nfs-root *(rw,no_root_squash,no_all_squash,async)
+
  
* Start the service
+
{{admon/note|Note: |  Connecting using telnet will also close the xterm popup window.}}
sudo systemctl start nfs.service  # Fedora
+
service nfs start  # RHEL
+
  
== Booting the Model with an NFS root ==
+
{{admon/note|Note: |  It may take several minutes for the model to be fully booted.}}
  
You need to setup the network for use with the aarch64 model and the addressing used in the kernel arguments.
 
Start the model using one of the following depending on if you would like to use systemd or busybox as your init process (Busybox is currently recommended).
 
*Systemd:
 
sudo Foundation_v8pkg/Foundation_v8 --image aarch64-kernels/systemd-3.7-nfs-foundation.axf --network=bridged
 
*Busybox:
 
sudo Foundation_v8pkg/Foundation_v8 --image aarch64-kernels/busybox-3.7-nfs-foundation.axf --network=bridged
 
After starting the model you will see a new device created on your host system named 'ARM0', use the following to assign an IP address for use with the model:
 
sudo ifconfig ARM0 10.0.0.1 netmask 255.255.255.0
 
  
Once this adapter is assigned an IP address, the system should boot to either a login prompt or boot with busybox as the init process.
+
* For console:
 +
telnet 10.0.1.1 5000    # note this is the IP of the gateway and not the model
 +
* For ssh login:
 +
ssh root@10.0.1.2        # note this is the IP address of the model
  
You may need to adjust your firewall to allow connections to the NFS server (Port 2049).
+
 
 +
The '''root password is 'fedora''''.
  
  
Line 95: Line 88:
 
* Set up Network Address Translation:
 
* Set up Network Address Translation:
 
  HOSTEXTERNAL=eth0 # Replace this with your outside interface
 
  HOSTEXTERNAL=eth0 # Replace this with your outside interface
  sudo iptables -t nat -A POSTROUTING -o $HOSTEXTERNAL -j MASQUERADE
+
  sudo iptables -t nat -I POSTROUTING -o $HOSTEXTERNAL -j MASQUERADE
  sudo iptables -A FORWARD -i $HOSTEXTERNAL -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
+
  sudo iptables -I FORWARD -i $HOSTEXTERNAL -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
  sudo iptables -A FORWARD -i ARM0 -o $HOSTEXTERNAL -j ACCEPT
+
  sudo iptables -I FORWARD -i ARM1 -o $HOSTEXTERNAL -j ACCEPT
  
 
* Firewall trouble? Try this:
 
* Firewall trouble? Try this:
  sudo iptables -A INPUT -i ARM0 -j ACCEPT
+
  sudo iptables -I INPUT -i ARM1 -j ACCEPT
  
 
The model uses Google's Public DNS server (8.8.8.8) for name resolution (/etc/resolv.conf).
 
The model uses Google's Public DNS server (8.8.8.8) for name resolution (/etc/resolv.conf).
  
= Getting Started with the Aarch64 Bootstrap =
+
= Fixing build failures =
Consider setting the date to something more current.  The following command, run as root, will set the date to April 19 2000 hours, 2013:
+
If you want to debug a broken package, please visit the [[ Architectures/ARM/AArch64/Stage4_Problem_Packages | problem package list]], follow the directions and claim the packages of your choice.
date 041920002013
+
 
+
Log in using the root account (using the Busybox kernel this will be done by default)
+
su - builder
+
 
+
Then execute the script:
+
/usr/sbin/arm-rebuild.sh
+
 
+
The first time you run arm-rebuild.sh it will retrieve arm-temp.ausil.us's ssh host key and ask if you want to continue connecting.  Say yes, per the following:
+
<pre>
+
The authenticity of host 'arm-temp.ausil.us (74.119.218.150)' can't be established.
+
RSA key fingerprint is ae:aa:1d:58:0f:c5:c3:f3:00:95:c7:e8:8b:15:c3:da.
+
Are you sure you want to continue connecting (yes/no)? yes
+
Warning: Permanently added 'arm-temp.ausil.us,74.119.218.150' (RSA) to the list of known hosts.
+
</pre>
+

Revision as of 17:53, 21 October 2013

Shortcut:
Arch:ARM

Contents

Aarch64 Quickstart Guide

This page will help those new to aarch64 (ARMv8) get started with the Foundation Model provided by ARM. The F19-aarch64-efi tarball provides an F19-based disk image, which includes a kernel, initramfs, and device tree blob, files to support booting the kernel using EFI, and a sample script for starting the model.

Download the Foundation Model

The first step is to download the Foundation model from ARM. The model is not redistributable and will therefor require you to create a free account with ARM. Once completed, you will be able to download the Foundation Model and begin.

To run the model you may need to install some additional software with the following command:

sudo yum install xterm xorg-x11-fonts-{misc,100dpi,75dpi}* telnet bridge-utils

Extract the Foundation Model

Once you have downloaded the model, you will need to set up your environment. The model can be extracted to a path of your choosing. Your home directory will be used in this example.

Unpack the model:

mkdir ~/aarch64
cd ~/aarch64
tar xvzf FM000-KT-00035-r0p8-44rel23.tgz

Using the Model with an Image

Using the commands below, download and extract the Aarch64 root filesystem tarball.

Note.png
Note: The extracted disk image requires approximately 12GB disk space. Please ensure you have adequate free space. This may take several minutes to unpack, depending on your hardware.
cd ~/aarch64
wget http://dmarlin.fedorapeople.org/fedora-arm/aarch64/F19-aarch64-efi.tar.xz
tar Jxvf F19-aarch64-efi.tar.xz 

Starting the Model

The kernel supports virtio, so the kernel image, initramfs, and device tree blob included on the image will be used in the boot process. You no longer need to use separate "Kernel Packages".

An example script for starting the model has been included in the tarball. This script performs the following steps to start the model:

sudo ../Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 \
  --cores=1 \
  --visualization \
  --image=linux-system-el3-foundation.axf \
  --data=RTSM_VE_FOUNDATIONV8_EFI.fd@0xA0000000 \
  --block-device `pwd`/aarch64-efi.img \
  --network=bridged \
  --network-bridge=ARM1 &
sleep 5
sudo ifconfig ARM1 10.0.1.1 netmask 255.255.255.0


Both console (telnet) and ssh access are supported. To start the model, change to the F19-aarch64-efi subdirectory and run the script:

 cd ~/aarch64/F19-aarch64-efi
 ./efi-aarch64.sh
Note.png
Note:
You must have 'sudo' access in order to run this script.
Note.png
Note:
The script assumes the foundation model is in:
   ~/aarch64/Foundation_v8pkg.
Adjust as necessary for your environment.


You should be able to ssh to the model once it has fully booted. You can use telnet to connect to the serial console using the provided ports as it boots.

Note.png
Note:
Connecting using telnet will also close the xterm popup window.
Note.png
Note:
It may take several minutes for the model to be fully booted.


  • For console:
telnet 10.0.1.1 5000     # note this is the IP of the gateway and not the model
  • For ssh login:
ssh root@10.0.1.2        # note this is the IP address of the model


The root password is 'fedora'.


Allowing the Model to Connect to the Internet

On the host:

  • Enable IP forwarding (as root)
echo 1 > /proc/sys/net/ipv4/ip_forward
  • Set up Network Address Translation:
HOSTEXTERNAL=eth0 # Replace this with your outside interface
sudo iptables -t nat -I POSTROUTING -o $HOSTEXTERNAL -j MASQUERADE
sudo iptables -I FORWARD -i $HOSTEXTERNAL -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
sudo iptables -I FORWARD -i ARM1 -o $HOSTEXTERNAL -j ACCEPT
  • Firewall trouble? Try this:
sudo iptables -I INPUT -i ARM1 -j ACCEPT

The model uses Google's Public DNS server (8.8.8.8) for name resolution (/etc/resolv.conf).

Fixing build failures

If you want to debug a broken package, please visit the problem package list, follow the directions and claim the packages of your choice.