[Call for Testers] VirtualBox 4.3.0

Bernhard Fröhlich decke at bluelife.at
Sat Nov 9 07:00:05 UTC 2013


Am 04.11.2013 16:35 schrieb "Mike C." <miguelmclara at gmail.com>:
>
>
>
> On 11/04/13 09:21, Volodymyr Kostyrko wrote:
> > 02.11.2013 22:11, Mike C. wrote:
> >>> Weird. VirtualBox is working for me on 10-STABLE (BETA2 right now I
> >>> suppose). `VBoxManage list ostypes` yields a lengthy list of systems.
> >>>
> >>> Maybe this is something about build options? I'm building it only with
> >>> DBUS GUESTADDITIONS NLS QT4 X11. Can you share your list of build
> >>> options?
> >>>
> >>
> >> I used the same options to compile and it and the include change, I was
> >> able to compile and install, but I still get the same problem with
4.2...
> >> I need to run "VirtualBox" with root or sudo -u myuser...
> >
> > Have you added your user to vboxusers group? What kind of errors you
> > see? Is kernel module loaded?
> >
>
> the user in the vboxusers and kernel modules are loaded.
>
> Its a very weird behavior, because with sudo -u myuser I still using my
> regular user!
>
> What I guess is a segfault
> pid 2941 (VirtualBox), uid 1001: exited on signal 11
>
> gdb:
> Copying output to gdb.txt.
> (gdb) run
> Starting program: /usr/local/bin/VirtualBox
> (no debugging symbols found)...[New LWP 100371]
> VirtualBox: Error -10 in SUPR3HardenedMain!
> VirtualBox: Effective UID is not root (euid=1001 egid=1001 uid=1001
> gid=1001)

This is it! Please have a look at /usr/local/lib/virtualbox and
/usr/local/bin/VirtualBox and check that they are owned by root and the
suid bit is set. I don't know yet who is stripping that but it could be
that you are building the port as non-root or the ports staging does
something stupid.


More information about the freebsd-emulation mailing list