[Bug 192359] emulators/virtualbox-ose-additions 11.0-CURRENT VBoxService doesn't start
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Dec 2 09:45:06 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192359
Michael Grünewald <michipili at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michipili at gmail.com
--- Comment #2 from Michael Grünewald <michipili at gmail.com> ---
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 at 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.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-emulation
mailing list