Well, I don’t know about unstable but I can confirm that vb works on my “stable” system.
I didn’t install a Windows system from scratch on the TrueOS-VirtualBox though but just copied an existing vm (guest) from my Windows system and put it into the respective folder of my TrueOS user home folder.
It loaded/booted just fine.
I guess, all I did was installing those two virtualbox-ose packages (via AppCafe), the main one and think some package equivalent to the extention pack for Windows.
There was some “editing” necessary to get vb to start in the first place. I’m not on the TrueOS system now, so I can’t say for sure, but I’d say I took the advice from this page regarding the vboxdrv entries into the system to get it to work.
I’ll check the next time I’m on TrueOS and report back.
While I was typing apparently @RodMyers and @jmdavis already were done with their input. I think I had to add myself to the vboxuser group, too.
I just rebooted into TrueOS to check:
The 2 packages are: virtualbox-ose and virtualbox-ose-additions
Apparently I saved the post-installation output (of AppCafe / pkg install using terminal) into txt files (but apparently those can be found in respective info for every installed package in the AppCafe) for future reference:
It’s essentially what the FreeBSD link from above states, but after installing the additions package are some notes that are not covered by the link as far as I see right now.
So I’ll try to cover what I did when “editing”:virtualbox-ose
According to virtualbox-ose instructions:
- Add users to
According to virtualbox-ose-additions instructions:
- Add users to