Date: Tue, 31 Mar 2015 21:13:12 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Yuri <yuri@rawbw.com> Cc: freebsd-emulation@freebsd.org Subject: Re: VirtualBox (sometimes) not starting/hanging after recent openssl updates Message-ID: <alpine.BSF.2.20.1503312102290.6848@wonkity.com> In-Reply-To: <551B1EDD.4010909@rawbw.com> References: <20150329182732.GA1415@elch.exwg.net> <5519AF03.1030808@kit.bg> <551B1EDD.4010909@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 31 Mar 2015, Yuri wrote: > On 03/30/2015 13:16, Ivo Karabojkov wrote: >> I've explained my tests already to the thread you mention. Here is my >> ldd output from a working system: >> # ldd /usr/local/lib/virtualbox/VBoxRT.so > > I am nor sure if you still have issues with VirtualBox, but mix of openssl > libraries from base and port was the cause for me. This mix was introduced by > latest curl update. > To fix this run (cd /usr/ports/ftp/curl && make config) and select GSSAPI to > be *not* from base. I chose 'heimdal' option. Then force rebuild/upgrade of > curl, and VirtualBox will likely work. Rebuilding ftp/curl set to GSSAPI_NONE rather than GSSAPI_BASE worked! Both the Qt GUI and the CLI versions work again, and the VMs run. Apparently there are a lot of different symptoms from this one problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1503312102290.6848>