296 VMs deployed 🐡

Known issues


Make sure you run the latest syspatch.


It's possible the clock to drift at some point. When this becomes severe run rdate(8) from cron:

*/15 * * * * /usr/sbin/rdate -s pool.ntp.org


We have seen some connectivity drops from time to time, some lasting longer than others. This might be related to the way vmm(4)/vmd(8) handles interupts. As a workaround run ping from cron:

*/5 * * * * /sbin/ping -c3 <your gateway> > /dev/null

Alternative is to run ping in tmux with something like:

ping -i5 <your gateway>

You can do this automatically at reboot in cron with:

@reboot /usr/bin/tmux new -d 'while true; do ping -i5 <your gateway>; done' \;

High CPU interrupts

VMs have a constant high intr CPU state:

CPU states: 0.0% user, 0.0% nice, 0.1% sys, 0.0% spin, 98.0% intr, 1.9% idle

This is an accounting error.

Unresponsive VM

It happens every so often a VM hangs, and the only motiviation which works is a "kill -9". Since all VMs are running as root this is not possible as a normal user, we are now using pkill in doas(1) so you can.

The doas.conf(5) entry we are using is:

permit nopass vm-owner as root cmd pkill args -9 -f vm-name

The command you need to issue is something like:

doas pkill -9 -f vm03