There are currently a couple of known issues.
Your VM is a clean install of OpenBSD 7.0-release + errata. You can ssh into it:
vm03$ ssh username@XXX.XXX.XXX.XXX OpenBSD 7.0 (GENERIC) #224: Thu Sep 30 14:13:34 MDT 2021 ... vm03$
Get the password from ~/.ssh/authorized_keys and switch to root.
vm03$ awk '{print$NF}' .ssh/authorized_keys
XXXXXXXXXXXXXXXXXXXXXXXXXX
vm03$ su -
Password:
vm03#
Add your username to /etc/doas.conf:
# echo 'permit username' > /etc/doas.conf # echo 'permit nopass keepenv root as root' >> /etc/doas.conf #
All errate should be applied, but you can check 7.0 errata and apply available patches.
vm03# syspatch ... Relinking to create unique kernel... done; reboot to load the new kernel Errata can be reviewed under /var/syspatch vm03# reboot Connection to XXX.XXX.XXX.XXX closed by remote host.
To get connected to the console you need to have access to the host your VM is running on. The same username and public SSH key, as provided for the VM, are used to create a local user on the host.
All SSH fingerprints (SSHFP) records of all the hosts are added to DNS. You can verify the SSH fingerprint by adding “-o VerifyHostKeyDNS=yes” to the ssh command.
$ ssh -o VerifyHostKeyDNS=yes server10.openbsd.amsterdam The authenticity of host '[server10.openbsd.amsterdam]' can't be established. ECDSA key fingerprint is SHA256:KzeKaYVJDsr+pfNT46sz/3W9YdGhq/tWFclrOnaYigU. Matching host key fingerprint found in DNS. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes ... server10$
You can also use mosh to connect to the host. We added a short write-up on how to use mosh on your own VM.
When this is done you can use vmctl(8) to manage your VM.
The options you have are:
server10$ vmctl console vm server10$ vmctl start [-c] id server10$ vmctl stop [-fw] id
-f Forcefully stop the VM without attempting a graceful shutdown.
-w Wait until the VM has been terminated.
-c Automatically connect to the VM console.
Note: id can also be your VM name.