VBox works fine for me, currently I am on Daedalus/kernel 6.5 with 7.0.12 from virtualbox.org's repository. Every now and then there are teething problems with new kernels or graphics, but I would claim its perfect for my production use, i.e. pass through of USB devices and shared folders.

I started using VBox with Squeeze if I remember correctly, and I haven't got any issues with "disk full" or access problems to USB drives.

Well, I have always avoided the default of using my home drive to store the VMs. From the beginning I have had a separate partition or drive for them. Its easy to configure in the options of the Virtualbox Manager.

Yes. The user needs to be in the vboxusers group. This normally is established during installation of the main package.

And attention to the extension package. Its version has to match the main packages version.

Can't tell you how exactly the Debian build works, I'm not using it. In any case under depends there is a reference to virtualbox-dkms or similar, I think this might do the job in the background.

Its enough to install the Virtualbox package. Mostly everything required is installed automagically. Exception: you will need build-essential, dkms and headers to build the VBox modules, and you have to add 3 lines to /etc/modules.

You are right, there are VBox scripts in /etc/init.d. In my long experience I never had to fool with these scripts in any way.

Updated my Ventoj to 1.0.96 and also tried the server and the desktop iso, all the same.

That is not correct. I am using VBox now for so many years, I can't really tell how long. And I have always used the package supplied by https://www.virtualbox.org/wiki/Downloads. On Devuan no issues with systemd all along from ASCII to Excalibur.

May I add a few lines (on Ventoj 1.0.94 from July this year):

What snork describes is what happens with legacy boot of Ventoj/Devuan.

All in efi mode, netinstalls:
5.0.0 normal mode I just get an _ and have to use the Reset button.
5.0.0 grub mode: no bootfile found for efi

5.0.1 normal mode: the first menu comes up ok, can select expert install, end in the mount cdrom scenario described before.
5.0.1 grub mode: have to repeat the test, can't decipher my scribbling no bootfile found for efi

Strangely enough grub mode produces an efi error.

An old preview dated 220523 in normal mode boots to the Choose Language screen, same as older releases. Same for Debian 12.1. Others like gparted life 1.5.0-1, mint 21.1 ... work fine.

Edith: added the 5.0.1 grub mode test

I am using Cinnamon with Lighdm, no other DE installed. Then the default is Cinnamon. Haven't changed or configured anything. Is so by installation.

Nope, you have to enable os-prober past the first boot of the installed Devuan. And there is no need to hope, it will work as a charm when enabled. It simply works when enabled.

BTW to set the mind right: Devuan is a Debian w/o systemd. You may find a list of banned packages on the Devuan webpage. Where appropriate or required, the Devuan team has developed replacements. All the rest is Debian.

Edith: forgot to mention, the decision to disable os-prober per default was a Debian decision.

I guess you may have to look into the difference between using su and su - for getting root access. This is a feature that was inherited from Debian a while ago.

You may need to use su -.

On my Daedalus amd64 workstation:

# apt-cache rdepends wireless-regdb
wireless-regdb
Reverse Depends:
  linux-image-6.1.0-10-amd64
  linux-image-6.1.0-9-amd64
  linux-image-6.1.0-7-amd64
  linux-image-6.1.0-6-amd64
  linux-image-6.1.0-5-amd64
  linux-image-6.1.0-3-amd64
  linux-image-6.1.0-2-amd64
  linux-image-6.1.0-1-amd64
  linux-image-6.0.0-6-amd64
  linux-image-6.0.0-5-amd64
  linux-image-6.0.0-4-amd64
  linux-image-5.17.0-1-amd64
  linux-image-6.4.0-0.deb12.2-rt-amd64-unsigned
  linux-image-6.4.0-0.deb12.2-rt-amd64
  linux-image-6.4.0-0.deb12.2-cloud-amd64-unsigned
  linux-image-6.4.0-0.deb12.2-cloud-amd64
  linux-image-6.4.0-0.deb12.2-amd64-unsigned
  linux-image-6.4.0-0.deb12.2-amd64
  linux-image-6.1.0-12-rt-amd64-unsigned
  linux-image-6.1.0-12-rt-amd64
  linux-image-6.1.0-12-cloud-amd64-unsigned
  linux-image-6.1.0-12-cloud-amd64
  linux-image-6.1.0-12-amd64-unsigned
  linux-image-6.1.0-12-amd64
  linux-image-6.1.0-11-rt-amd64-unsigned
  linux-image-6.1.0-11-rt-amd64
  linux-image-6.1.0-11-cloud-amd64-unsigned
  linux-image-6.1.0-11-cloud-amd64
  linux-image-6.1.0-11-amd64-unsigned
  linux-image-6.1.0-11-amd64
  network-manager
  linux-image-6.1.0-13-rt-amd64-unsigned
  linux-image-6.1.0-13-rt-amd64
  linux-image-6.1.0-13-cloud-amd64-unsigned
  linux-image-6.1.0-13-cloud-amd64
  linux-image-6.1.0-13-amd64-unsigned
  linux-image-6.1.0-13-amd64
  linux-image-6.1.0-10-rt-amd64-unsigned
  linux-image-6.1.0-10-rt-amd64
  linux-image-6.1.0-10-cloud-amd64-unsigned
  linux-image-6.1.0-10-cloud-amd64
  linux-image-6.1.0-10-amd64-unsigned
  iw
  iwd

A Ventoj stick can boot both legacy and efi and displays its mode on the splash screen.