Architectures/AArch64/FoundationModelQuickStart

From FedoraProject

< Architectures | AArch64(Difference between revisions)
Jump to: navigation, search
(Getting Started with the Aarch64 Bootstrap)
(Clarify that Fast Models are not supported)
(30 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
{{lang|en|zh-cn|page=Architectures/ARM/AArch64/QuickStart}}
 
{{lang|en|zh-cn|page=Architectures/ARM/AArch64/QuickStart}}
 
[[Category:AArch64]]{{shortcut|Arch:ARM}}
 
[[Category:AArch64]]{{shortcut|Arch:ARM}}
 +
{{admon/warning|IMPORTANT |<b>This is pre-release software and not intended for general use.</b>}}
 
=Aarch64 Quickstart Guide=
 
=Aarch64 Quickstart Guide=
This page will help those new to aarch64(armv8) get started with the Foundation Model provided by ARM. There 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 F21-20140628-foundation-v8 Remix tarball provides an F21-based disk image, which boots the kernel from the image using UEFI(Tianocore) and Grub2, and a sample script for starting the model. This Fedora Remix uses a look aside repository for the kernel package, which includes patches that are headed upstream, but not yet added to Fedora.
  
 
== 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 re-distributable and will therefore require you to create a free account with ARM. Once completed, you will be able to download the Foundation Model and begin.  
 +
{{admon/note|Note: It is important to use the latest Foundation Model, if you encounter any issues check to see that you have the most recent version. }}
 +
{{admon/warning|IMPORTANT: The Fast Models are not currently supported. }}
  
 
* [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 15: Line 18:
 
==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:
  
 
  mkdir ~/aarch64
 
  mkdir ~/aarch64
 
  cd ~/aarch64
 
  cd ~/aarch64
  tar xvzf FM000-KT-00035-r0p8-44rel23.tgz
+
  tar xvzf FM000-KT-00035-r0p8-52rel06.tgz
  
 
== Using the Model with an Image ==
 
== Using the Model with an Image ==
  
Using the commands below, download and extract the Aarch64 root filesystem disk image. The disk image will extract to roughly 12GB in size and may take several minutes to unpack depending on your hardware.
+
Using the commands below, download and extract the Aarch64 root filesystem tarball.  
cd ~/aarch64
+
wget http://fedorapeople.org/~pwhalen/aarch64/stage4-root-20130528.img.tar.bz2
+
tar xvjf stage4-root-20130528.img.tar.bz2
+
  
==== Kernel Packages ====
+
{{admon/note|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.}}
The Foundation model seems to have some performance issues when using a serial console, there are two kernel packages to choose from - one that includes the console, the other does not and is intended for use by connecting through ssh. The kernels use the wrapper to set the hostname and networking. For example 'systemd-3.9-image-2G-1.axf' will set a hostname of 'model-1' with and IP address of 10.0.1.2, the default gw should be set to 10.0.1.1. The last number in the kernel name indicates which network, hostname will be used when it boots.  
+
* With console:
+
<pre>
+
wget http://fedorapeople.org/~pwhalen/aarch64/systemd-3.9-image-2G.tar.bz2
+
tar xvjf systemd-3.9-image-2G.tar.bz2
+
</pre>
+
* No console:
+
<pre>
+
wget http://fedorapeople.org/~pwhalen/aarch64/systemd-3.9-image-ns-2G.tar.bz2
+
tar xvjf systemd-3.9-image-ns-2G.tar.bz2
+
</pre>
+
  
===== Starting the Model =====
+
cd ~/aarch64
NOTE: You may need to adjust your path for the model depending on the version in use.
+
wget http://dmarlin.fedorapeople.org/fedora-arm/aarch64/F21-20140628-foundation-v8.tar.xz
* With console:
+
tar xvf F21-20140628-foundation-v8.tar.xz
<pre>
+
sudo Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 \
+
--image systemd-3.9-image-2G/systemd-3.9-image-2G-1.axf \
+
--network=bridged \
+
--network-bridge=ARM1 \
+
--block-device stage4-root-20130528.img 
+
</pre>
+
* No console:
+
<pre>
+
sudo Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 \
+
--image systemd-3.9-image-ns-2G/systemd-3.9-image-ns-2G-1.axf \
+
--network=bridged \
+
--network-bridge=ARM1 \
+
--block-device stage4-root-20130528.img 
+
</pre>
+
 
+
On the host immediately after launching the model:
+
 
+
sudo ifconfig ARM1 10.0.1.1 netmask 255.255.255.0
+
 
+
You should now be able to ssh to the model once it has fully booted. If your using the console enabled kernels you can use telnet to connect to the serial console using the provided ports as it boots, this will also close the xterm popup window.
+
* For console:
+
telnet 10.0.1.1 5003 # note this is the IP of the gateway and not the model
+
The port number seems to be inconsistent and can vary depending on how quickly you attempt to connect, but is usually the last listed port.
+
* No console (also works on console)
+
ssh root@10.0.1.2 # note this is the IP address of the model
+
The '''root password is 'fedora', there is also another account called 'builder' password 'builder''''.
+
 
+
== Using the model with an NFS root ==
+
 
+
Using the model through an NFS root is no longer recommended or supported here.
+
  
== Allowing the Model to Connect to the Internet ==
+
=== Allowing the Model to Connect to the Internet ===
 
On the host:
 
On the host:
 
* Enable IP forwarding (as root)
 
* Enable IP forwarding (as root)
Line 93: Line 52:
 
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 =
+
=== Starting the Model ===
Use either ssh or the console to connect to the model, if this is your first time running the model it is recommended to use a kernel that will provide a console for troubleshooting any problems that arise.
+
  
Before getting started, its very important to set the correct date on the model, the below example will set the date to 12:00pm, 29 May 2013
+
The kernel supports virtio, so the kernel image and initramfs included on the image will be used in the boot process. This image boots using UEFI (tianocore) and Grub2.
  date 052912002013
+
  
Then execute the script(as builder):
+
An example script for starting the model has been included in the tarball.  This script performs the following steps to start the model:
  su - builder
+
/usr/sbin/arm-rebuild.sh
+
  
The system should begin building packages for the aarch64 bootstrap, below is an example of the output you should see:
 
 
<pre>
 
<pre>
[builder@aarch64 ~]$ /usr/sbin/arm-rebuild.sh
+
sudo ../Foundation_v8pkg/models/Linux64_GCC-4.1/Foundation_v8 \
building: bouncycastle-1.46-7.fc19 at Thu Apr 25 22:43:27 GMT 2013
+
  --cores=1 \
INFO: mock.py version 1.1.30 starting...
+
  --visualization \
Start: init plugins
+
  --image=linux-system-el3-foundation.axf \
INFO: selinux disabled
+
  --data=RTSM_VE_FOUNDATIONV8_EFI.fd@0xA0000000 \
Finish: init plugins
+
  --block-device `pwd`/${IMAGE} \
Start: run
+
  --network=bridged \
INFO: Start(/home/builder/bouncycastle-1.46-7.fc19.src.rpm)  Config(stage4-aarch64)
+
  --network-bridge=ARM1 &
Start: lock buildroot
+
sleep 5
Start: clean chroot
+
sudo ifconfig ARM1 192.168.1.1 netmask 255.255.255.0
Finish: clean chroot
+
Finish: lock buildroot
+
Start: chroot init
+
Start: lock buildroot
+
Mock Version: 1.1.30
+
INFO: Mock Version: 1.1.30
+
INFO: calling preinit hooks
+
INFO: enabled root cache
+
INFO: enabled yum cache
+
Start: cleaning yum metadata
+
Finish: cleaning yum metadata
+
INFO: enabled ccache
+
Start: device setup
+
Finish: device setup
+
Start: yum update
+
 
</pre>
 
</pre>
 +
{{admon/note|Note: |  Depending on your environment you may need to change the IP addressing used.}}
  
= Fixing build failures =
+
To start the model, change to the image subdirectory and run the script:
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.  It is best to stop the arm-rebuild.sh script while doing local debugging as system performance will be further decreased doing two builds at once.
+
  
= Notes =
+
  cd ~/F21-20140628-foundation-v8
* When using the model with a kernel that provides a serial console you may see intermittent 'ttyAMA0: 1 input overrun(s)'.
+
  ./efi-aarch64.sh
* Intermittent networking issues with 'partial' file downloads.
+
 
 +
{{admon/note|Note: | You must have 'sudo' access in order to run this script. The script assumes the foundation model is in:
 +
    ~/aarch64/Foundation_v8pkg
 +
Adjust as necessary for your environment.}}
 +
 
 +
To connect to the serial console, telnet to the provided ports as it boots, for example:
 +
 
 +
telnet 192.168.1.1 5000    # note this is the IP of the model gateway and not the model
 +
 
 +
{{admon/note|Note: |  Connecting using telnet will also close the xterm popup window. | If your connection is not successful using port 5000, try 5001, 5002, or 5003.}}
 +
 
 +
This is an example log of the model starting, and using telnet to access the console:
 +
 
 +
<pre>
 +
terminal_0: Listening for serial connection on port 5000
 +
terminal_1: Listening for serial connection on port 5001
 +
terminal_2: Listening for serial connection on port 5002
 +
terminal_3: Listening for serial connection on port 5003
 +
Visualization web server started on port 2001
 +
Simulation is started
 +
sh: xterm: command not found
 +
 +
telnet 192.168.1.1 5000
 +
 
 +
 
 +
$ telnet 192.168.1.1 5000
 +
Trying 192.168.1.1...
 +
Connected to 192.168.1.1.
 +
Escape character is '^]'.
 +
</pre>
 +
 
 +
The model will then start the first stage bootloader (tianocore), which will launch grub2, which will in turn boot the selected kernel, for example:
 +
{{admon/note|Note: | To navigate the menu use '<ctrl>n' - next and '<ctrl>p' - previous.}}
 +
<pre>
 +
Secure firmware (version  built at 13:07:46 on Apr  7 2014)
 +
PROGRESS CODE: V3020003 I0
 +
PROGRESS CODE: V3020002 I0
 +
PROGRESS CODE: V3020003 I0
 +
PROGRESS CODE: V3021001 I0
 +
 
 +
+---------------------------------------------------------------------------+
 +
|                                                                          |
 +
|    ARM64, with Linux 3.14.0-0.rc8.git1.1.0.1.fc21.aarch64                |
 +
|    ARM64, with Linux 0-rescue-79e714035d9e46cbbecc55e70a3b10a1          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|                                                                          |
 +
|  The selected entry will be started automatically in 1s.                |
 +
|  Press 'e' to edit the selected item, or 'c' for a command prompt.      |
 +
+---------------------------------------------------------------------------+
 +
 
 +
EFI stub: Booting Linux Kernel...
 +
:
 +
</pre>
 +
 
 +
You should be able to ssh to the model once it has fully booted.
 +
 
 +
{{admon/note|Note: | It may take several minutes for the model to be fully booted.}}
 +
 
 +
* For ssh login:
 +
ssh root@192.168.1.5        # note this is the IP address of the model
 +
 
 +
 
 +
'''Notes:'''
 +
* Verify that the system date/time are correct.
 +
* To avoid image or filesystem corruption it is important to shutdown the model properly.
 +
  shutdown -h now
 +
* After shutting down, ensure the Foundation Model process has been stopped before restarting.
 +
  sudo kill -TERM <PID for the Foundation Model process>
 +
* The '''root password is 'fedora''''.
 +
 
 +
= Fixing build failures =
 +
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.

Revision as of 21:51, 24 July 2014

Shortcut:
Arch:ARM
Warning (medium size).png
IMPORTANT
This is pre-release software and not intended for general use.

Contents

Aarch64 Quickstart Guide

This page will help those new to aarch64 (ARMv8) get started with the Foundation Model provided by ARM. The F21-20140628-foundation-v8 Remix tarball provides an F21-based disk image, which boots the kernel from the image using UEFI(Tianocore) and Grub2, and a sample script for starting the model. This Fedora Remix uses a look aside repository for the kernel package, which includes patches that are headed upstream, but not yet added to Fedora.

Download the Foundation Model

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

Note.png
Note: It is important to use the latest Foundation Model, if you encounter any issues check to see that you have the most recent version.
Warning (medium size).png
IMPORTANT: The Fast Models are not currently supported.

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-52rel06.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/F21-20140628-foundation-v8.tar.xz
tar xvf F21-20140628-foundation-v8.tar.xz 

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).

Starting the Model

The kernel supports virtio, so the kernel image and initramfs included on the image will be used in the boot process. This image boots using UEFI (tianocore) and Grub2.

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`/${IMAGE} \
  --network=bridged \
  --network-bridge=ARM1 &
sleep 5
sudo ifconfig ARM1 192.168.1.1 netmask 255.255.255.0
Note.png
Note:
Depending on your environment you may need to change the IP addressing used.

To start the model, change to the image subdirectory and run the script:

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

To connect to the serial console, telnet to the provided ports as it boots, for example:

telnet 192.168.1.1 5000     # note this is the IP of the model gateway and not the model
Note.png
Note:
Connecting using telnet will also close the xterm popup window.

This is an example log of the model starting, and using telnet to access the console:

terminal_0: Listening for serial connection on port 5000
terminal_1: Listening for serial connection on port 5001
terminal_2: Listening for serial connection on port 5002
terminal_3: Listening for serial connection on port 5003
Visualization web server started on port 2001
Simulation is started
sh: xterm: command not found
 
telnet 192.168.1.1 5000


$ telnet 192.168.1.1 5000
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.

The model will then start the first stage bootloader (tianocore), which will launch grub2, which will in turn boot the selected kernel, for example:

Note.png
Note:
To navigate the menu use '<ctrl>n' - next and '<ctrl>p' - previous.
Secure firmware (version  built at 13:07:46 on Apr  7 2014)
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3021001 I0

+---------------------------------------------------------------------------+
|                                                                           |
|     ARM64, with Linux 3.14.0-0.rc8.git1.1.0.1.fc21.aarch64                |
|     ARM64, with Linux 0-rescue-79e714035d9e46cbbecc55e70a3b10a1           |
|                                                                           |
|                                                                           |
|                                                                           |
|                                                                           |
|                                                                           |
|                                                                           |
|                                                                           |
|                                                                           |
|                                                                           |
|                                                                           |
|   The selected entry will be started automatically in 1s.                 |
|   Press 'e' to edit the selected item, or 'c' for a command prompt.       |
+---------------------------------------------------------------------------+

EFI stub: Booting Linux Kernel...
	:

You should be able to ssh to the model once it has fully booted.

Note.png
Note:
It may take several minutes for the model to be fully booted.
  • For ssh login:
ssh root@192.168.1.5        # note this is the IP address of the model


Notes:

  • Verify that the system date/time are correct.
  • To avoid image or filesystem corruption it is important to shutdown the model properly.
 shutdown -h now
  • After shutting down, ensure the Foundation Model process has been stopped before restarting.
 sudo kill -TERM <PID for the Foundation Model process>
  • The root password is 'fedora'.

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.