Am 20.11.2013 18:42 schrieb "Photo stuff" <w-in...@xs4all.nl>: > > The following reply was made to PR ports/183085; it has been noted by GNATS. > > From: Photo stuff <w-in...@xs4all.nl> > To: bug-follo...@freebsd.org, gosha-n...@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.
It is really strange that this only seems to affect FreeBSD 10 and I have no clue why. To my knowledge this code that creates the xml file has not changed for quite a while and worked fine up to now. _______________________________________________ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"