qemu-solo5-mirage-rpi3

An attempt to run a MirageOS unikernel, built with Solo5, running in Qemu, on a Raspberry Pi 3

Setup and tools

• A Docker environment and Solo5 Docker Image.
• A Mirage unikernel iso and img built with Solo5.
• A Raspberry Pi 3.
• RPi 3 Ubuntu Mate on microSD card.

Set up:

Insert the Pi's SD card, attach screen and keyboard. Then follow setup procedure.

Once you have completed setup and have a user account, connect the Pi to your network and the rest can be done over ssh.

Inside the Pi, get up-to-date and install qemu tools.

sudo apt-get update
sudo apt-get upgrade
# install tools
sudo apt-get -y install qemu-kvm qemu-system qemu-utils qemu-block-extra qemu-user git vim bridge-utils uml-utilities
mkdir code
cd code
git checkout https://github.com/rudenoise/qemu-solo5-mirage-rpi3.git
cd qemu-solo5-mirage-rpi3

Outside the Pi, copy the built iso and img from the container:

docker cp solo5-mirage:/home/solo5/solo5/kernel.iso ./
docker cp solo5-mirage:/home/solo5/solo5/disk.img ./

Copy the iso and img to the RPi.

scp ./disk.img {{user}}@{{rPi ip address}}:~/code/qemu-solo5-mirage-rpi3
scp ./kernel.iso {{user}}@{{rPi ip address}}:~/code/qemu-solo5-mirage-rpi3

Inside the Pi, run the unikernel and disk in qemu

cd code/qemu-solo5-mirage-rpi3
sudo qemu-system-x86_64 \
    -s -nographic \
    -name mirage \
    -m 256 \
    -cdrom kernel.iso \
    -net nic,model=virtio \
    -net tap,ifname=tap0,script=./tap-up.sh,downscript=tap-down.sh \
    -drive file=disk.img,format=raw,if=virtio \
    -boot d

Open another console on the Pi:

# try this now and then, eventually it might work!!!
ping 10.0.0.2

Expose the running unikernel to the outside world

Once the line

Listening on http://localhost/

appears, you can use port forwarding to expose it to the host's network.

sudo sysctl net.ipv4.ip_forward=1
sudo iptables -t nat -A PREROUTING -p tcp -d {{ your nw ip }} --dport 8080 -j DNAT --to-destination 10.0.0.2:80
sudo iptables -t nat -A POSTROUTING -j MASQUERADE

Results

The unikernel is running but haven't configured network, yet.

            |      ___|
  __|  _ \  |  _ \ __ \
\__ \ (   | | (   |  ) |
____/\___/ _|\___/____/
Found virtio network device with MAC: 52 54 00 12 34 56
host features: 71000ed4: 2 4 6 7 9 10 11 24 28 29 30
Found virtio block device with capacity: 2048 * 512 = 1048576
queue size is 128
DJW: new bindings
getenv(OCAMLRUNPARAM) -> null
getenv(CAMLRUNPARAM) -> null
getenv(PATH) -> null
Unsupported function lseek called in Mini-OS kernel
Unsupported function lseek called in Mini-OS kernel
Unsupported function lseek called in Mini-OS kernel
getenv(OCAMLRUNPARAM) -> null
getenv(CAMLRUNPARAM) -> null
getenv(TMPDIR) -> null
getenv(TEMP) -> null
getenv(DEBUG) -> null
getenv(OMD_DEBUG) -> null
getenv(OMD_FIX) -> null
lib/solo5_stubs.c: connect!!

lib/solo5_stubs.c: WARNING: returning hardcoded MAC
Netif: plugging into tap0 with mac 52:54:00:12:34:56
Netif: connect tap0
tap0 with mac 52:54:00:12:34:56
Attempt to open(/dev/urandom)!
Unsupported function getpid called in Mini-OS kernel
Unsupported function getppid called in Mini-OS kernel
Manager: connect
Manager: configuring
Manager: Interface to 10.0.0.2 nm 255.255.255.0 gw [10.0.0.1]

Manager: connect
Manager: configuring
Manager: Interface to 10.0.0.2 nm 255.255.255.0 gw [10.0.0.1]

ARP: sending gratuitous from 10.0.0.2
Manager: configuration done
Listening on http://localhost/

Wait some random period, look away, ping it again... and it'll be running.