Just for fun/oddity ...

Linux host (Fatdog), booted as OpenBSD doesn't support my laptop wifi.

Within that kvm/qemu boot OpenBSD install iso and install that to a qcow2 vHDD.

kvm/qemu boot that vHDD once installed and configure things within OpenBSD as you like (cwm, Xdefaults ...etc.).

Shut that down and boot again using a backing file, where the main vHDD is read only, all changes are recorded in the disposable backing file, so starting with a new backing file at each such boot and it boots into a 'clean/pristine' version each time (or leave the backing file in place and your next reboot resumes as it was last left).

Within OpenBSD install tigervnc, ditto in the Linux host. Set the Linux host as the vncserver, use vncviewer within OpenBSD to connect to that via 10.0.0.2:1 (the kvm/qemu's standard guest to host ssh IP). I set the host sshd_config with pretty open settings, not sure what may or not be required in that respect - haven't given it that much thought so far.

~/.vnc/xstartup for the vncserver is set to just open a terminal from which I open/start chrome.

Works very well on my oldish 4GB ram 2 core laptop system chrome playing youtubes 'within' OpenBSD look and sound good, very responsive, and when OpenBSD kvm/qemu is full-screened its all 'integral' to that, like running a regular pure OpenBSD desktop but with a chrome browser that is very responsive/usable. Install libreoffice ... etc alongside that within OpenBSD and you have a more rounded desktop environment. Cheating as chrome is actually being run within Linux, only the display is being displayed within OpenBSD via the vnc connection.

OpenBSD running within the Linux kernels virtual machine (kvm), with instant access to both Linux and OpenBSD, no having to reboot one and then the other as per a 'normal/conventional' dual boot setup.

On my subsequent reboot I opted to run jwm within the vnc/linux, which helped with clearer separation/identification, but I guess also running cwm instead would make it a more consistent look-n-feel.