VirtualBox Issue after upgrade

Had the same problem after the last upgrade as mentioned by other users in this thread and in the Bugzilla :

Code: 
# date ; uname -a
Mon  6 Apr 2020 09:45:46 -05
FreeBSD host-freebsd 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC  amd64

# pkg info | grep -i virtualbox-ose
virtualbox-ose-5.2.34_2
virtualbox-ose-kmod-5.2.34_2

VirtualBox GUI will segfault when starting :
Code: 
$ VirtualBox
Segmentation Fault
(but will work when started as "root")

As suggested by T-Daemon and sgunn , I have downgraded (using my last locally cached version) and it works again :
Code: 
# pkg remove virtualbox-ose-5.2.34_2 virtualbox-ose-kmod-5.2.34_2
# pkg add  /var/cache/pkg/virtualbox-ose-*5.2.32_1.txz
# reboot

Hope this could help someone !
 
Last edited by a moderator:
Upgrade your system, you're still on 12.0. Packages in the repositories are specifically built for 12.1 now. FreeBSD 12.0 is end-of-life.
 
The latest package on FreeBSD 12.1 p3 still crashes.
Code: 
Thread 1 received signal SIGSEGV, Segmentation fault.
0x0000000803fbba18 in vtable for __cxxabiv1::__si_class_type_info ()
from /lib/libcxxrt.so.1
(gdb) bt
#0 0x0000000803fbba18 in vtable for __cxxabiv1::__si_class_type_info ()
from /lib/libcxxrt.so.1
#1 0x000000080071f3e6 in __dynamic_cast ()
from /usr/local/lib/gcc9/libstdc++.so.6
#2 0x000000080cc8d2f9 in ?? () from /usr/local/lib/libKF5ConfigCore.so.5
#3 0x000000080cc86c4e in KConfigGroup::KConfigGroup(KConfigBase*, QString const
&) () from /usr/local/lib/libKF5ConfigCore.so.5
#4 0x000000080b369c20 in ?? ()
from /usr/local/lib/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#5 0x000000080b367c66 in ?? ()
from /usr/local/lib/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#6 0x000000080b363af1 in ?? ()
from /usr/local/lib/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#7 0x000000080b37b48b in ?? ()
from /usr/local/lib/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#8 0x000000080510ddd8 in QPlatformThemeFactory::create(QString const&, QString
const&) () from /usr/local/lib/qt5/libQt5Gui.so.5
#9 0x0000000805118d7b in QGuiApplicationPrivate::createPlatformIntegration()
() from /usr/local/lib/qt5/libQt5Gui.so.5
#10 0x0000000805119780 in QGuiApplicationPrivate::createEventDispatcher() ()
from /usr/local/lib/qt5/libQt5Gui.so.5
#11 0x0000000804e379fb in QCoreApplicationPrivate::init() ()
from /usr/local/lib/qt5/libQt5Core.so.5
--Type <RET> for more, q to quit, c to continue without paging--
#12 0x000000080511492a in QGuiApplicationPrivate::init() ()
from /usr/local/lib/qt5/libQt5Gui.so.5
#13 0x00000008058921ce in QApplicationPrivate::init() ()
from /usr/local/lib/qt5/libQt5Widgets.so.5
#14 0x0000000802714ead in TrustedMain (argc=<optimized out>,
argv=<optimized out>)
at /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/src/VB
ox/Frontends/VirtualBox/src/main.cpp:404
The Qt5 and KDE5 libs are all linked with libc++, but VirtualBox is linked with libstdc++.

For this to work it would require a Qt5 linked with libstdc++, at least.
 
I'm not sure is this somehow related to update to FreeBSD 12.1. No matter if I use the last version (built from Ports) or older version of emulators/virtualbox-ose-nox11 (5.2.32_1, found in packages) the system sporadically crashes with kernel panic - sleeping thread. The panic mostly occurs during system startup if VirtualBox starts at boot, up to 10 seconds after manual start or at shutdown.
 
Thx for the advice...
I've installed an older version from the repository:

Code: 
# pkg info | grep -i virtualbox-ose
virtualbox-ose-5.2.32_1        General-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-5.2.34     VirtualBox kernel module for FreeBSD

and the segmentation error went away...
 
Last edited by a moderator:
Not sure if this belongs here, since this isn't a seg fault, but may be related.

For me, the latest version (5.2.34_4) either as a package or port crashes the system when run as a non-root user. (Older 5.2.34 versions I tried did this too.) Installing a yet older package version (5.2.32_1) works but with no sound. By chance, I mixed emulators/virtualbox-ose-5.2.34_4 from ports with package emulators/virtualbox-ose-kmod-5.2.32_1 and it ran with working sound.


Code: 
% uname -a
FreeBSD Dad.local 12.1-RELEASE-p3 FreeBSD 12.1-RELEASE-p3 GENERIC  amd64
% pkg info -x virtualbox
virtualbox-ose-5.2.34_4
virtualbox-ose-kmod-5.2.32_1
%

The sequence I used to do this was

Code: 
# cd /usr/ports/emulators/virtualbox-ose
# make install clean
# cd ../virtualbox-ose-kmod
# make deinstall
# cd /var/cache/pkg
# fetch "http://pkg.freebsd.org:12:amd64/release_1/All/virtualbox-ose-kmod-5.2.32_1.txz"
# pkg add /var/cache/pkg/virtualbox-ose-kmod-5.2.32_1.txz
# shutdown -r now

Note: Attempting to use pkg to remove emulators/virtualbox-ose-kmod removes both.
 
One of my systems behaves absolutely strange. It is Supermicro X11DPL-I, runs FreeBSD 12.1-RELEASE-p3 and has one Intel(R) Xeon(R) Silver 4108 CPU with latest BIOS and sysutils/devcpu-data invoked from /boot/loader.conf
With earlier emulators/virtualbox-ose-nox11 5.2.34 the system crashed with sleeping thread kernel panic.
I built emulators/virtualbox-ose-nox11 5.2.34_4 from ports and it started without kernel panic - both running at startup or starting manually.
But when I built net/samba410 the nightmare of kernel panics returned. When both VirtualBox and Samba run at startup the system panics with sleeping thread during startup of VirtualBox. If I start one of these manually after boot the system works just fine.
It's really odd. I'm not sure when exactly this all started. I've updated the system BIOS, FreeBSD 12.0 to 12.1, rebuilt all ports and ran into this trouble.
 
SirDice said:
Upgrade your system, you're still on 12.0. Packages in the repositories are specifically built for 12.1 now. FreeBSD 12.0 is end-of-life.
Click to expand...

Thank you SirDice for your suggestion, I have upgraded from FreeBSD 12.0 to FreeBSD 12.1-p3.
VirtualBox is now working with the last version available by pkg (virtualbox-ose-kmod-5.2.34, virtualbox-ose-5.2.34_4).
 
You must log in or register to reply here.
Back
Top