Hello together, my first post on a OpenBSD list. I'm using an OpenBSD Box as a router for my small personal homesetup for some years.
I used a Qotom Box with 1G Interfaces 8G Ram and i5 8th generation for some years, but recently i changed due to various reasons from hardware to a qemu-vm (ArchLinux Host) on another host. The OpenBSD Box/VM also routes / pf between some internal vlans. Everything seems to work great and reasonably fast, as i'm used from OpenBSD. But i think i hit a small bug or perhaps a known limit (i did not find anything in the man pages though): I'm doing the vlan-tagging on the VM-Host-Side, so i have 9 interfaces that connects to a bridge on the qemu host, and one interface for the Internet-Uplink which connects also via a hostbridge, so 10 interfaces alltogether. If i add more than 9 vio Interfaces to the qemu-vm-config, OpenBSD boots only to "fd0 at fdc0 drive 1: density unknown". I'm using stable. As a workaround, i added the last interface as a intel-nic, and everything works fine again. dmesg with added ifconfig from a working config: https://me.zediria.de/logs/dmesg-working.txt serial-boot-output from a failure config (stable): https://me.zediria.de/logs/dmesg-working.txt I can reproduce this on a different machines with the same qemu options / version. The qemu-version is 9.2.0 (Package-Version Archlinux: 9.2.0-2) Here is how i fire up the OpenBSD vm using QEMU: https://me.zediria.de/logs/qemu.txt I tried the same configuration with a Linux Guest, no problems. It is completly irrelevant if i configure the interfaces in OpenBSD or not (i think the boot stops long before the network scripts) I tried upgrading to a the latest snapshot, but the bsd.upgrade kernel is not finding the storage device, so i stopped trying that. (Error: "vioblk0 at virtio9virtio9: Feature negotiation failed") Best regards Jan -- Jan <li...@zediria.de>
