ports/183085: emulators/virtualbox-ose failed to work on FreeBSD 10-BETA1
Photo stuff
w-info2 at xs4all.nl
Wed Nov 20 17:00:02 UTC 2013
The following reply was made to PR ports/183085; it has been noted by GNATS.
From: Photo stuff <w-info2 at xs4all.nl>
To: bug-followup at FreeBSD.org, gosha-necr at yandex.ru
Cc:
Subject: Re: ports/183085: emulators/virtualbox-ose failed to work on FreeBSD
10-BETA1
Date: Wed, 20 Nov 2013 17:49:50 +0100
L.S.
I can report that on FreeBSD 10.0 Beta 2, Virtualbox
virtualbox-ose-4.2.18_1 fails with the same messages:
----
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted
(extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running
or failed to start.
---
Also, removing .Virtualbox directory which is mentioned in various
places on the web going back for a few years, does not work for me either.
Starting VBoxSVC in one xterm, then typing VirtualBox in another gives
the error message that it can't read the "VirtualBox.xml". Well, of
course if doesn't exist it can't be read.
So creating a minimal VirtualBox.xml in the .VirtualBox directory that
was created after the failed start, was what I tried and it worked. Even
the most minimal one such as what Bernhard Froehlich suggested (removing
the 2 times '3D' that I see on the bugreport via the web) works.
I then added a virtual image etc. VirtualBox seems to work fine when the
xml file is there.
Wouter
More information about the freebsd-emulation
mailing list