Solved a weird issue i have had for a while, today.
Have started to look into NetBSD and they dont, yet, have the niceitys that is FreeBSD Jails (yes i know about Cells)
Did not for some reason get NetBSD to boot in bhyve, so used Qemu instead. Was fairly simple to get going.
That worked quite fine, but had noticed that sometimes updating packages or downloading more than a little data, it would Stall the download. Huh?

Did not bother at first, but got more and more frustrating. Also have created an install and upgrade script USE AT OWN RISK!!!!!
The solution seems to be to use a unique macaddress for each Qemu vm

#!/bin/sh
n1=`printf '%02d' "$(( RANDOM % 100 ))"`
n2=`printf '%02d' "$(( RANDOM % 100 ))"`
n3=`printf '%02d' "$(( RANDOM % 100 ))"`
n4=`printf '%02d' "$(( RANDOM % 100 ))"`
macaddr="52:54:$n1:$n2:$n3:$n4"
/usr/pkg/bin/qemu-system-x86_64 -netdev tap,id=tap0,ifname=tap0,script=no\
 -device virtio-net-pci,netdev=tap0,mac=$macaddr -cdrom NetBSD-10.0-amd64.iso\
 -drive if=virtio,file=.vm/netbsd.qcow2,format=qcow2 -usbdevice tablet\
 -display none -accel nvmm -m 6G -smp 4 -vnc :1  

I Like that NetBSD uses GCC as default instead of clang. Maby user error, but once you have wasted a week of debugging an issue that when shown all warnings was a simple fix, you get "frustrated"
Using the exact same compiler options gives way different output, makes no sense. And if i remember correctly, there was something in the clang code saying like "wont fix"
I also like that NetBSD has a more relaxed release schedule.
I already use their package manager on my Mac, so thats nice.

Time will tell, we need someting todo during the summer.

Speaking of macs, might look for a M1/M2 Macbook Pro to install Open/NetBSD on, not sure yet.
3 weeks until vacation!!!!