vbox VirtualBox stopped working after upgrade to 15.1

Yampress · 2026-09-28T16:56:15+0100

vm-bhyve - until a graphical manager for controlling bhyve virtual machines is created

Now I have peace of mind. I don't get annoyed after every update when the VirtualBox module is incompatible with the kernel and VirtualBox versions—and stops working.

siladi · 2026-09-28T17:01:07+0100

Checkout also https://sylve.io/ . Have not used it yet, I like vm-bhyve.

rmomota · 2026-09-28T17:02:47+0100

Do you run a graphic OS with bhyve? Like Ubuntu or a Windows with performance?

Yampress · 2026-09-28T17:07:09+0100

In the past, I used VMware, then VirtualBox.
Right now I'm using vm-behyve. At least until they create a fully functional graphical manager for managing machines for bhyve. Now I don’t get frustrated anymore when VirtualBox stops working after an update because the module version is incompatible with the kernel and VirtualBox versions. And I don’t have to recompile the module again, as long as it’s still compatible with the version in the ports.
Now everything is fine.

Code:

root@freebsd /home/yampress # vm list
NAME       DATASTORE  LOADER  CPU  MEMORY           VNC           AUTO  STATE
debian     default     uefi      2     5G      0.0.0.0:5900        No    Running (67034)
fedorakde  default     uefi      2     5G               -          No    Stopped
root@freebsd /home/yampress #

both in graphic mode:
fedora - kde
debian - xfce

bhyve/vmm on FreeBSD is better than virtualbox
qemu/kvm on linux is better than virtualbox

rmomota · 2026-09-28T17:43:29+0100

Yampress said:
In the past, I used VMware, then VirtualBox.
Right now I'm using vm-behyve. At least until they create a fully functional graphical manager for managing machines for bhyve. Now I don’t get frustrated anymore when VirtualBox stops working after an update because the module version is incompatible with the kernel and VirtualBox versions. And I don’t have to recompile the module again, as long as it’s still compatible with the version in the ports.
Now everything is fine.

Code:

root@freebsd /home/yampress # vm list NAME DATASTORE LOADER CPU MEMORY VNC AUTO STATE debian default uefi 2 5G 0.0.0.0:5900 No Running (67034) fedorakde default uefi 2 5G - No Stopped root@freebsd /home/yampress #

both in graphic mode:
fedora - kde
debian - xfce

bhyve/vmm on FreeBSD is better than virtualbox
qemu/kvm on linux is better than virtualbox

not if you need direct rendering but I agree that in most cases we don't really need that if we are only using tools and not playing heavy rendering games.
How do you manage to connect a USB device in bhyve?
I've got a Boss Katana combo and the software only runs in windows OS and I need to connect the USB to it.
I was wondering if it will work with bhyve.

EDIT:
Yes true it happend to me VBox kms need to be recompiled to get it working again.
That's a Ports general problem. I also need to recompile gvfs if I want FUSE enabled because the Port maintainer decided no one needs that enabled by default.

Yampress · 2026-09-28T19:39:14+0100

USB redirect -
"
- **PCI passthrough** -- assign physical devices directly to guests.
"
Bhyve supports PCI passthrough, which lets you assign a physical GPU (or any PCI device) directly to a guest. This is useful for running GPU-accelerated workloads inside VMs.
"

rmomota · 2026-09-28T23:20:12+0100

Yampress said:
USB redirect -
"
- **PCI passthrough** -- assign physical devices directly to guests.
"
Bhyve supports PCI passthrough, which lets you assign a physical GPU (or any PCI device) directly to a guest. This is useful for running GPU-accelerated workloads inside VMs.
"

That is if your hardware has 2 cards, something like a onboard chip and another pci connected card

Selin · 2026-09-29T03:49:06+0100

Yampress said:
try bhyve

I tried. And used it until they removed uefi-csm loader/firmware support.
I need to run Windows 2008 R2 and Windows 7, and even XP for some cases. In my cases it is almost impossible to switch to a newer system that supports bare UEFI. (custom proprietary soft simply doesn't run on a newer system).
So, I rolled back to VirtualBox that supports all the legacy systems. Updating via ports works for now, so will proceed with VB until (if) bhyve (re)implements legacy uefi-csm loader/firmware. Or will try to switch to ProxMox otherwise, regardless me dislike Linux-based systems.

Selin · 2026-09-29T03:57:38+0100

siladi said:
Checkout also https://sylve.io/

Tried this one. Looks promising, but I rejected it for now as found usability not good for me here and there. Also, no CLI option - only web-UI, which is a no-go for me.

Tried BVCP as well. Looks better as for me, but it is not opensource.

But since both are bhyve-based, they have the same limitation - only uefi/grub loader/firmware. No options for legacy Windows systems.