[vbox-dev] Framebuffer implementation cannot power up a vm (VERR_VM_DRIVER_NOT_ACCESSIBLE) with VirtualBox 5

Klaus Espenlaub klaus.espenlaub at oracle.com
Mon May 9 18:02:32 UTC 2016

Hi Rūdolfs,

On 09.05.2016 12:29, Rūdolfs Bundulis wrote:
> Hi,
> after looking at the permissions of the VirtualBox binaries do I
> understand correctly that I need to do chown root:root <my binary> and
> chmod +s <my binary> for this to work (will test this when I get back to
> that machine)?

Correct. If you look closely you'll actually notice that the suid root 
binaries in our case are pretty small stubs and load the corresponding 
.so file which contain the actual code. This is part of the hardening 
which makes implementing your own VM executables more tricky (would need 
to check which whitelist you would need to add yourself to).

You know that you can trust your code, but VirtualBox in general is 
rather paranoid these days.


More information about the vbox-dev mailing list