The recording of the April 23rd, 2026 #bhyve Production User Call is up:
We discussed EDK II issues and maintenance, root-on-p9fs, a TPM issue that is misreported as a Windows instruction emulation issue, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
Using The New Bridges of FreeBSD 15
https://blog.feld.me/posts/2026/02/using-new-bridges-freebsd-15/
FreeBSD 15 comes with a new bridging implementation which has native support for VLANs. They have also soft-deprecated the ability to have any layer 3 addresses on member interfaces which makes it behave like a real hardware switch. The net.link.bridge.member_ifaddrs sysctl controls this behavior and it will …
It’s bigger on the inside.
Successfully trapped a Bhyve hypervisor 
inside a VNET Jail on FreeBSD 15.0-RELEASE 
Host -> Jail (named 'tardis') -> Hypervisor -> Virtual Machine.
Complete with working dual-stack IPv4/IPv6 routed via pf on the host. Why? Because I needed to isolate the VMs from the host's network, and I apparently enjoy fighting deep-nested devfs rulesets on a Friday night.
From the "That only took 36 years" department:
With #FreeBSD jail, #OpenZFS, 'makefs -t zfs', root on p9fs, packaged base, and #bhyve/ARM64 in place, let's pull them all together:
https://github.com/michaeldexter/occambsd#imagine-and-propagate-scenarios
That is, generate a 15.0 installer image, push that hardware, push that further to VMs, and then further to STABLE and CURRENT boot environments.
All updatable with pkg(8)
This may contain bugs, but it's forcing me to exercise it.
Okay, so I got the converted Windows 10 VM running under #Bhyve without issue, everything is working as it should.
But for some reason, all VMs on this host can only be started once, after a VM is stopped, the host has to be rebooted to get them running again.
There are no errors, no logs, no .lock files, no stale tap interfaces, no zombie processes, just nothing at all. When I issue "vm start windows10", there is a short spike in CPU usage, then nothing happens, and the VM remains " Stopped".
Has someone ran into such a problem before with #FreeBSD 15.0? All other hosts I have used so far ran the VMs perfectly fine... 🤔
The recording of the April 9th, 2026 #bhyve Production User Call is up:
We discussed VirtIO reviews, Windows 11 VM stability, guest tools, documenting functions and variables in code, #FreeBSD VT console behavior, ReBarUEFI, running the OpenZFS test suite in a VM, PXE booting VMs, masking the Windows hypervisor discovery bit, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
Just migrated from a bhyve VM running Pi-hole to a Jail running Adguard Home.
Few of my 20 (!) clients are lagging behind but a proper rdr rule in pf does the trick.
It’s working great so far but the web GUI is lacking many info. Anyway it’s a win: same service quality (so far), easier maintenance, lower resources, and a Linux VM shut down.
The recording of the April 2nd, 2026 #bhyve Production User Call is up:
We discussed major #EDK2 updates, the long-awaited Sylve port, a #Sylve forum proposal, migrating from #TrueNAS to Sylve, a bhyve to the rescue story, Sylve Packet Filter integration and networking, Sylve use cases, and more!
"Don't forget to slam those Like and Subscribe buttons."
You can support all Call For Testing efforts via BSD Fund: https://bsdfund.org
Michael Dexter
Ricardo Martín 
Larvitz
subnetspider
Jason Tubnor 🇦🇺
patpro
Marcel Stritzelberger