Comment 1 John Marino 2014-08-03 18:12:48 UTC

over to maintainer team...

This is still an issue, I am not sure which precise set of functionalities
it impairs in VirtualBox.

I experience the same problem on a fresh 11.1-RELEASE install on amd64:

  $ uname -a
  FreeBSD llea 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017     root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64


The symptom is the same for me as reported by palik:

  $ sudo service vboxservice forcestart
  Starting vboxservice.
  VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND

It is possible to trace the error the condition to the VboxGuestR3Lib.cpp
file in the sources as a hint that the file VBOXGUEST_DEVICE_NAME cannot
be opened.  I believe this is the matching definition for FreeBSD

  include/VBox/VBoxGuest.h:# define VBOXGUEST_DEVICE_NAME          "/dev/vboxguest"

and I actually do not have a /dev/vboxguest file on my system, while the
kernel module with the same name is loaded.


The sources

  src/VBox/GuestHost/OpenGL/util/vboxhgsmi.c

also led me to think that this device might be created by the graphic
stack of VirtualBox.  I therefore rebuilt virtualbox-ose-additions
from the branch 2017Q4 of the ports tree, enabling the support for
OpenGL, but this did not change the situation in any visible way.

Comment 3 Mikhail Teterin 2017-12-28 15:44:37 UTC

(In reply to Michael Grünewald from comment #2)
The /dev/vboxguest entry is created by the vboxguest.ko module upon /successful/ loading.

The module may file to initialize itself, but will still load -- and stay there, uselessly. If you are have the vboxguest service enabled to start at boot, please, post output of `grep -i vbox /var/run/dmesg.boot`.

I had this problem because my guest is FreeBSD/i386 using PAE -- but the port is usually built without -DPAE, which makes the port-built kernel-modules subtly incompatible with the actual kernel. You are using 64-bit guests, so that should not be the problem -- but something else is...

(In reply to Mikhail Teterin from comment #3)

Unfortunately neither dmesg.boot nor messages do display a useful
information about what could cause the failure.

I restarted my system with verbose boot mode to obtain additional
details, which caused no more insight:

  # grep -i box /var/run/dmesg.boot
  Preloaded elf obj module "/boot/modules/vboxdrv.ko" at 0xffffffff82559220.

  # grep -i vbox /var/log/messages
  Jan  3 13:58:41 llea kernel: Preloaded elf obj module "/boot/modules/vboxdrv.ko" at 0xffffffff82559220.
  Jan  3 13:58:42 llea root: /etc/rc: WARNING: failed to start vboxservice

It's rather hard to figure out a meaningful next troubleshooting test!

After freebsd-update upgrade 11.2-RELEASE-p4 from Release 11.1.

I still encounter the same problem today with virtualbox-5.2.26_4 on FreeBSD 11.2-RELEASE-p8, no matter if I compile the port or install the package.
I suggest to change importance to "affects many users"

The error seems to be coming from /dev/vboxguest not present:

sigprocmask(SIG_SETMASK,{ SIGALRM },0x0)         = 0 (0x0)
openat(AT_FDCWD,"/dev/vboxguest",O_RDWR|O_CLOEXEC,00) ERR#2 'No such file or directory'
VBoxServicewrite(2,"VBoxService",11)                     = 11 (0xb)
: write(2,": ",2)                                        = 2 (0x2)
error: write(2,"error: ",7)                              = 7 (0x7)
VbglR3Init failed with rc=VERR_FILE_NOT_FOUNDwrite(2,"VbglR3Init failed with rc=VERR_F"...,45) = 45 (0x2d)

write(2,"\n",1)                                  = 1 (0x1)
exit(0x1)                                       
process exit, rval = 1

From what I have researched (and confirmed at https://www.freebsd.org/doc/handbook/virtualization-guest-virtualbox.html), the package virtualbox-ose-additions package is only necessary on FreeBSD guests (running in VirtualBox already). 

For VirtualBox running on a FreeBSD Host, I installed emulators/virtualbox-ose and loaded the vboxdrv module. Works fine.

Comment 8 Jung-uk Kim 2021-04-07 15:54:02 UTC

Does it work with 6.1.18?