freebsd stable - Sep 2018 - [Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535

--- Comment #15 from Dennis Clarke <dclarke at blastwave.org> ---
(In reply to rkoberman from comment #12)

virtualbox-ose has been a real pain to deal with for the last few weeks
here.  At least for me and my team of sysadmins who are doing experiments
with FreeBSD RELEASE 11.2. I can report that I have seen the panic-on-boot
loop "feature" and it is fun. 

Well the package for virtualbox-ose is broken on the RELEASE version 
of 11.2 and so yes it is a problem and will remain a problem until some
future date. Near future we hope.  One may perform the experiment, as I
have, repeatedly, and see a kernel panic repeatedly.

One must build the virtualbox-ose-kmod bits from ports and then overwrite 
the existing pkg which was installed via dependencies for virtualbox-ose.

The entirely repeatable process :

1) install RELEASE 11.2 

2) at first boot you may su - and as root do very very few things :

# /usr/sbin/pkg query -e '%a = 0' '%o'
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly,
please wait...
Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done
Installing pkg-1.10.5_1...
Extracting pkg-1.10.5_1: 100%
ports-mgmt/pkg
# 

Get on with the process of an update to the ports data

# /usr/sbin/portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
Fetching snapshot tag from your-org.portsnap.freebsd.org... done.
.
.
.

Then do the portsnap extract.

3) Full stop right here and we have a fresh RELEASE 11.2 system with not much
on it : 

# /usr/sbin/pkg query -e '%a = 0' '%o'
ports-mgmt/pkg
# 

4)  install virtualbox-ose BEFORE attempting to build virtualbox-ose-kmod

# pkg install virtualbox-ose 
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 125 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        virtualbox-ose: 5.2.12_1
        qt5-x11extras: 5.10.1
        qt5-gui: 5.10.1
.
.
.  a lot of stuff gets dragged in and that includes broken virtualbox-ose-kmod:
5.2.12

.
.
.

5) manually build virtualbox-ose-kmod in ports to replace the broken 5.2.12 pkg 

# cd /usr/ports/emulators/virtualbox-ose-kmod/
# make install clean  

  a few items to watch for : 

       Be sure to select libsigsegv for GNU m4 
       Disable DTRACE Build with DTrace probes
       gmp-6.1.2  enable CPU optimizations 


6) at some point in the reasonably near future you will have
   two virtualbox-ose version pkgs thus : 

virtualbox-ose-5.2.12_1        General-purpose full virtualizer for x86
hardware
virtualbox-ose-kmod-5.2.18     VirtualBox kernel module for FreeBSD

Note the different versions. 

After a minor edit to /boot/loader.conf and /etc/rc.conf one may reboot and 
have a workable mixed version virtualbox-ose.  Sort of.  The kernel module
version
isn't really a perfect match but seems to work thus far.   I have attempted
to
build all of virtualbox-ose from ports, repeatedly, over and over there are
little
bugs in the process that stop the build.  One gets fixed and another pops up.

I don't think your average user or sysadmin out there will be able to easily
get
around this mess.  So when is the next big release ?  Because I don't see
how
this can be marked as "fixed".  At best there is a hack workaround.

-- 
You are receiving this mail because:
You are on the CC list for the bug.