Skip to content

Latest commit

 

History

History
316 lines (231 loc) · 9.76 KB

README.md

File metadata and controls

316 lines (231 loc) · 9.76 KB

Packer scripts for building HPC disk images

Table of Contents

1. Status

rv64gc arm64 arm64sve x86_64
stream ✔ ✔ ✔ ✔
gups ✔ ✔ ✔ ✔
spatter ✔ ✔ ✔ ✔
npb ✔ * ✔* ✔* ✔*
MemoryLatencyTest ✔ ✔ ✔ ✔
permutating-scatter ✔ ✔ ✔ ✔
permutating-gather ✔ ✔ ✔ ✔
gapbs ? ? ?** ?

*Compiling is.D.x resulted in compilation error. ** The SVE compilation flags have not been added to the Makefile's of GAPBS.

2. Downloading Packer

See https://developer.hashicorp.com/packer/downloads.

3. Dependencies

apt-get install cloud-image-utils qemu-efi-aarch64 qemu-system qemu-utils

4. Building the rv64gc Disk Image

4.1 Downloading the Pre-installed RISC-V Disk Image

We choose to work with this disk image because this disk image is known to work with QEMU.

See https://ubuntu.com/download/risc-v.

wget https://cdimage.ubuntu.com/releases/22.04.4/release/ubuntu-22.04.4-preinstalled-server-riscv64+unmatched.img.xz
xz -dk ubuntu-22.04.4-preinstalled-server-riscv64+unmatched.img.xz
mv ubuntu-22.04.4-preinstalled-server-riscv64+unmatched.img rv64gc-hpc-2204.img
qemu-img resize rv64gc-hpc-2204.img +60G

4.2 Launching a QEMU Instance

qemu-system-riscv64 -machine virt -nographic \
     -m 16384 -smp 8 \
     -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf \
     -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \
     -device virtio-net-device,netdev=eth0 \
     -netdev user,id=eth0,hostfwd=tcp::5555-:22 \
     -drive file=rv64gc-hpc-2204.img,format=raw,if=virtio

4.3 Changing the Default Password

Upon the first boot, when you try to login to the ubuntu account, the OS will ask you to change the password. The default password is ubuntu. The new password should be automato, which is specified in rv64gc-hpc.json.

Note: Before continuing the following step, please note that you should wait until the "OpenBSD Secure Shell server" (i.e., the SSH server) to be brought up before logging in to the guest machine. The SSH server bringing up might be slow, and it might be done after the login prompt appears on the guest system. If you tried to ssh to the guest before the SSH server is brought up, it will result in authentication error.

To login to the guest machine,

ssh -p 5555 ubuntu@localhost

4.4 Running the Packer Script

While the QEMU instance is running,

./packer build rv64gc-hpc.json

5. Building the arm64 Disk Image

5.1 Downloading the arm64 Cloud Disk Image

See https://cloud-images.ubuntu.com/.

wget https://cloud-images.ubuntu.com/releases/22.04/release-20230616/ubuntu-22.04-server-cloudimg-arm64.img
qemu-img convert ubuntu-22.04-server-cloudimg-arm64.img -O raw ./arm64-hpc-2204.img
qemu-img resize -f raw arm64-hpc-2204.img +60G

5.2 Setting up an SSH key pair

The default key path is ~/.ssh/id_rsa might overwrite a current key. You can change the key path, and make a corresponding change in arm64-hpc.json.

ssh-keygen -C "ubuntu@localhost"
ssh-add ~/.ssh/id_rsa

5.3 Making a Cloud Init Config Image

Typically a cloud image will use cloud-init to initialize a cloud instance. In this case, we will use cloud-init to set up an SSH key so that we can login to the guest QEMU instance. This is necessary as the downloaded cloud image does not contain any user. Setting up a cloud init config allows us to create a user on the first boot.

We will create a file called cloud.txt to store the cloud init configuration. Typically the configuration looks like,

#cloud-config
users:
  - name: ubuntu
    lock_passwd: false
    groups: sudo
    sudo: ['ALL=(ALL) NOPASSWD:ALL']
    shell: /bin/bash
    ssh-authorized-keys:
      - ssh-rsa AAAAJLKFJEWOIJRNJF... <- insert the public key here (e.g., the content of ~/.ssh/id_rsa.pub)

Then, we create a cloud init image that we can input to qemu later,

cloud-localds --disk-format qcow2 cloud.img cloud.txt

Note that this image is of the qcow2 format.

5.4 Launching a QEMU Instance

Without KVM,

dd if=/dev/zero of=flash0.img bs=1M count=64
dd if=/usr/share/qemu-efi-aarch64/QEMU_EFI.fd of=flash0.img conv=notrunc
dd if=/dev/zero of=flash1.img bs=1M count=64
qemu-system-aarch64 -m 16384 -smp 8 -cpu cortex-a57 -M virt \
    -nographic -pflash flash0.img -pflash flash1.img \
    -drive if=none,file=arm64-hpc-2204.img,id=hd0 -device virtio-blk-device,drive=hd0 \
    -drive if=none,id=cloud,file=cloud.img -device virtio-blk-device,drive=cloud \
    -netdev user,id=user0 -device virtio-net-device,netdev=eth0 \
    -netdev user,id=eth0,hostfwd=tcp::5555-:22

With KVM,

dd if=/dev/zero of=flash0.img bs=1M count=64
dd if=/usr/share/qemu-efi-aarch64/QEMU_EFI.fd of=flash0.img conv=notrunc
dd if=/dev/zero of=flash1.img bs=1M count=64
qemu-system-aarch64 -m 16384 -smp 8 -cpu host -M virt -M gic-version=3 --enable-kvm \
    -nographic -pflash flash0.img -pflash flash1.img \
    -drive if=none,file=arm64-hpc-2204.img,id=hd0 -device virtio-blk-device,drive=hd0 \
    -drive if=none,id=cloud,file=cloud.img -device virtio-blk-device,drive=cloud \
    -netdev user,id=user0 -device virtio-net-device,netdev=eth0 \
    -netdev user,id=eth0,hostfwd=tcp::5555-:22

5.5 Running the Packer Script

While the QEMU instance is running,

./packer build arm64-hpc.json

After packer finished the installation, the following commands will login to the QEMU instance and properly shutdown the machine. This is necessasry to make sure that the disk image is not corrupted.

ssh-add ~/.ssh/id_rsa
ssh -p 5555 ubuntu@localhost
[in guest] sudo poweroff

6. Building the arm64sve Disk Image

This is similar to building the arm disk image, except for the packer json file is now arm64sve-hpc.json.

7. Building the x86_64 Disk Image

7.1 Downloading the x86_64 Cloud Disk Image

See https://cloud-images.ubuntu.com/.

wget https://cloud-images.ubuntu.com/releases/22.04/release-20230616/ubuntu-22.04-server-cloudimg-amd64.img
qemu-img convert ubuntu-22.04-server-cloudimg-amd64.img -O raw ./x86_64-hpc-2204.img
qemu-img resize -f raw ./x86_64-hpc-2204.img +60G

7.2 Setting up an SSH key pair

The default key path is ~/.ssh/id_rsa might overwrite a current key. You can change the key path, and make a corresponding change in x86_64-hpc.json.

ssh-keygen -C "ubuntu@localhost"
ssh-add ~/.ssh/id_rsa

7.3 Making a Cloud Init Config Image

Typically a cloud image will use cloud-init to initialize a cloud instance. In this case, we will use cloud-init to set up an SSH key so that we can login to the guest QEMU instance. This is necessary as the downloaded cloud image does not contain any user. Setting up a cloud init config allows us to create a user on the first boot.

We will create a file called cloud.txt to store the cloud init configuration. Typically the configuration looks like,

#cloud-config
users:
  - name: ubuntu
    lock_passwd: false
    groups: sudo
    sudo: ['ALL=(ALL) NOPASSWD:ALL']
    shell: /bin/bash
    ssh-authorized-keys:
      - ssh-rsa AAAAJLKFJEWOIJRNJF... <- insert the public key here (e.g., the content of ~/.ssh/id_rsa.pub)

Then, we create a cloud init image that we can input to qemu later,

cloud-localds --disk-format qcow2 cloud.img cloud.txt

Note that this image is of the qcow2 format.

7.4 Launching a QEMU Instance

qemu-system-x86_64 \
     -nographic -m 16384 -smp 8 \
     -device virtio-net-pci,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::5555-:22 \
     -drive file=x86_64-hpc-2204.img,format=raw \
     -drive if=none,id=cloud,file=cloud.img -device virtio-blk-pci,drive=cloud

7.5 Running the Packer Script

While the QEMU instance is running,

./packer build x86_64-hpc.json

After packer finished the installation, the following commands will login to the QEMU instance and properly shutdown the machine. This is necessasry to make sure that the disk image is not corrupted.

ssh-add ~/.ssh/id_rsa
ssh -p 5555 ubuntu@localhost
[in guest] sudo poweroff

A. Troubleshooting

Problem with Packer waiting for SSH

We recommend the following steps,

  • Trying to ssh to the QEMU instance before calling packer.
ssh -p 5555 ubuntu@localhost

In case of errors, the following commands might be useful,

ssh-keygen -f "$HOME/.ssh/known_hosts" -R "[localhost]:5555" # remove old fingerprints of localhost:5555
eval `ssh-agent -s` # this is useful when PACKER complains about getting SSH config: "packer-builder-null plugin: [DEBUG] Error getting SSH config: SSH_AUTH_SOCK is not set"
ssh-add ~/.ssh/id_rsa # need to add the identity file again after setting up the SSH agent
  • Trying to use PACKER_LOG environment variable to see what is happening to the SSH connection, e.g.,
PACKER_LOG=1 ./packer build rv64gc-hpc.json