Changes: https://www.virtualbox.org/wiki/Changelog-6.0#v0

Does 3D Accel work again with this version of VBox? Does anyone know?

I've tested this PR on my machine, after upgrading to 6.0.4 bendlas@1a73f8b

It doesn't seem to find its extension pack (installed in libexec due to a non-hardened build)

It does work on linux 4.20, though, which is an improvement over vbox 5 ;)

I removed the WIP status, but I couldn't get the tests to work.
Most likely it's because nested virtualization stopped working (tests run VirtualBox guest inside of QEMU host).

Everything else should work, including 3D accel.

What's blocking this?

I tried it, it works on my side. @infinisil I'd like to merge this if it's alright with you.

Please merge #55596 before or with this merge as that PR implies that this would break vagrant since the current version in unstable doesn't support virtualbox 6.

@wkral thank you for letting me know, I will merge #55596 after this one.

@flokli Let's wait to hear from @infinisil in this case!

@flokli As far I can tell, hardening and extension pack work.

I wasn't able to get the NixOS tests to run and fixing them is beyond my abilities.

@aszlig do you have time to dig into the virtualbox tests?

I'm happy to test this on macOS, although I'm a bit new to Nix. Can someone guide me on the appropriate process to check this out, and test it?

I've created a Darwin specific package, here what-the-functor@d0d87fc

@tonylotts I don't think virtualbox 6.0.4 completly broken for linux, it's just that the nixos vm tests don't work anymore (maybe due to the nested virtualization happening here) so we don't spot things suddenly breaking, which is why I'm hesitant to bump it without fixing the tests too…

Note the darwin-specific virtualbox6 derivation you proposed doesn't build VirtualBox, but simply unpacks a .dmg.

@flokli, yes I've purposely used the pre-built binary; although I acknowledge that the community preference is to build from source. As I understand it, pre-built binaries are cached. In the case that VirtualBox is already available in pre-built form, can/should that be cached?

Got it.

It turns out that the macOS version of VirtualBox provides kernel extensions. A macOS derivation for VirtualBox would require nix-darwin, and support for kernel extensions LnL7/nix-darwin#91.

@tonylotts so no matter what variant we use, the darwin version depends on LnL7/nix-darwin#91 or a successor to be merged?

6.0.6 has been released. Not that it matters that much, I guess, right now.

@flokli, yes

@devhell I tried bumping to 6.0.6, but it seems some patches need to be adjusted. Did you do that already somewhere?

The release notes mention some nested (AMD) virtualization fixes - I guess we still should see if things have improved.

@flokli I've not been able to, no. Sorry. :/

@ptrhlm could you get to that?

@flokli I've removed unnecessary kernel module patches. Also, I've moved patching of kernel module sources to the main package, so now unaligned patch will fail earlier.

Tests still fail on my Intel machine.

@ptrhlm thanks for the cleanup! I gave the tests a try on an AMD machine too, unfortunately, they fail there, too:

nix log /nix/store/pnbnmxz36kxdd33b8mj9v6qh2i7hmiws-vm-test-run-virtualbox-headless.drv looks most scary:

machine# !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
machine# !!
machine# !!         VCPU0: Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)
machine# !!
machine# !! TRAP=0e ERRCD=0000000000000010 CR2=00000000a082bf60 EIP=a082bf60 Type=0 cbInstr=ff
machine# !! EIP is not in any code known to VMM!
machine# !!
machine# !!
machine# !!

closed in favour of #60943.