OpenBSD kernel testing automation

README.md

This assumes you have:

• a development machine, here called "dev"
• a device under test, here called "dut"
• a serial console to dut
• network access from dut to dev
• the same arch dev and dut

You may need to change:

• GENERIC (in dev:.ssh/authorized_keys) to something else, e.g. maybe GENERIC.MP

The dut will boot your development kernel in single-user mode.

You can break to ddb with ddb.

You can run kernel-update to:

• (re)mount the appropriate file systems
• ssh to the dev machine and fetch the new kernel (which is forced server-side)
• reboot into it

dev.ssh.authorized_keys

restrict,command="curl -o- file:///usr/src/sys/arch/amd64/compile/GENERIC/obj/bsd" ssh-ed25519 AAAA... root@dut

dut.etc.boot.conf

stty com0 115200
set tty com0
/bsd.dev -s

dut.root.ssh.config

Host dev
HostName ...
User ...

dut.sbin.ddb

#!/bin/sh
sysctl ddb.console=1
sysctl ddb.trigger=1

dut.sbin.kernel-update

#!/bin/sh

set -e
set -x

# mount /usr for ssh
command -v ssh > /dev/null || mount -r /usr

# bring up network
sh /etc/netstart

# rw / so we can write the new kernel
mount -o rw /

# fetch new kernel, don't try to allocate TTY
ssh -T dev > /bsd.dev.incoming

# put in place atomically
ln -f /bsd.dev.incoming /bsd.dev
rm /bsd.dev.incoming

# reboot into it
reboot