VirtualBox crashes on start with Tunnelblick

[jknep]

Hi, I hadn't seen this issue at all before, but suddenly I started seeing these errors. I tried uninstalling and re-installing, as well as removing directories here and there that were a part of the old installations. Nonetheless, the same error crops up each time. I am on OSX El Capitan, and attempting to install the VB v5.0 image from the site. Any help appreciated! Thanks!

PS I have docker machine installed on this Mac, but no created VMs.


VirtualBox XPCOM Server 5.0.16 r105871 darwin.amd64 (Mar 4 2016 17:45:44) release log
00:00:00.000706 main Log opened 2016-03-08T23:18:03.850933000Z
00:00:00.000707 main Build Type: release
00:00:00.000717 main OS Product: Darwin
00:00:00.000722 main OS Release: 15.3.0
00:00:00.000727 main OS Version: Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 PST 2015; root:xnu-3248.30.4~1/RELEASE_X86_64
00:00:00.000817 main DMI Product Name: MacBookPro11,4
00:00:00.000856 main DMI Product Version: 1.0
00:00:00.000868 main Host RAM: 16384MB total, 6578MB available
00:00:00.000872 main Executable: /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC
00:00:00.000872 main Process ID: 4922
00:00:00.000872 main Package type: DARWIN_64BITS_GENERIC
00:00:00.107349 nspr-2 Home directory: '/Users/jknepper/Library/VirtualBox'
00:00:00.139102 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={Unknown exception
00:00:00.139111 nspr-2 /Users/vbox/tinderbox/5.0-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp[534] (nsresult VirtualBox::init())}, preserve=false aResultDetail=0

[lribinik]

I'm having the same issue, did you manage to solve it?

[lribinik]

I've narrowed this issue down to VPN being on (Tunnelblick), don't know why this happens yet, though

[pixelworlds]

I'm getting the same issue when trying to run VB while using openconnect - anyone have a resolution?

[zembunia]

Hello,

I have a similar problem.
When connected to a VPN with Tunnelblick (3.7.0) the running VirtualBox (5.1.16) fails as shown in

Screen Shot 2017-03-09 at 3.35.08 PM.png (60.07 KiB) Viewed 2527 times

Trying to start the VirtualBox results in

Screen Shot 2017-03-09 at 3.38.14 PM.png (75.38 KiB) Viewed 2527 times

When I quit Tunnelblick I can start the VirtualBox again.
I am using macOS Sierra 10.12.3 and the VBoxSVC.log is attached.

[andrewsharpe79]

Confirming this is still an issue.

VirtualBox 5.1.22 r115126 (Qt5.6.2)
Tunnelblick 3.6.8 (build 4625)
OSX El Capitan (10.11.6)

I have also tried "restarting" virtualbox with

Code: Select all

sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

with the VPN connected and disconnected, to no avail. For me the issues only arise after my host has resumed from sleep.

[andrewsharpe79]

Thanks heaps to @lribinik for isolating Tunnelblick, most helpful

Potential lead: https://superuser.com/questions/1132223 ... vpn-server

[socratis]

Changed the title to something more appropriate. Quoting the solution/workaround from SuperUser.com:

In my OpenVPNAS server, I deleted the value on "Configuration > VPN Settings > Default Domain Suffix (optional)", and VirtualBox worked again:

Default Domain Suffix (optional)
Setting a default suffix here will enable Windows clients to resolve host names to FQDN names. This is especially usefual if your organization uses a Windows Domain or Active Directory. Only one default suffix can be defined here.

Can affected people verify the solution please?

[andrewsharpe79]

The solution from superuser.com is not for tunnelblick, I mentioned it as a lead

[socratis]

I'm sorry, what? You mentioned that you have Tunnelblick, you mentioned an additional condition (sleep) and then you point to the person that posted the solution about Tunnelblick. How is this not Tunnelblick?

And connected/not connected doesn't count. Installed/completely uninstalled is what counts (for Tunnelblick).