Date: Thu, 28 Dec 2017 15:44:37 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 192359] emulators/virtualbox-ose-additions 11.0-CURRENT VBoxService doesn't start Message-ID: <bug-192359-26505-rjdizr4518@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192359-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-192359-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192359 Mikhail Teterin <mi@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mi@FreeBSD.org Assignee|vbox@FreeBSD.org |jkim@FreeBSD.org --- Comment #3 from Mikhail Teterin <mi@FreeBSD.org> --- (In reply to Michael Gr=C3=BCnewald 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 po= rt 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... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192359-26505-rjdizr4518>