Bug 183085 - emulators/virtualbox-ose failed to work on FreeBSD 10-BETA1
Summary: emulators/virtualbox-ose failed to work on FreeBSD 10-BETA1
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL:
Keywords:
Depends on:
Blocks: 245048
  Show dependency treegraph
 
Reported: 2013-10-18 16:20 UTC by George
Modified: 2020-03-30 21:51 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George 2013-10-18 16:20:00 UTC
When tryin to do any operation with VirtualBox on FreeBSD-10-BETA1, it gives an error:
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.

Any manipulations with temporary files (rm -rf /tmp/.vbox* ; rm -rf ~/.VirtualBox ) not helps

How-To-Repeat: Install FreeBSD 10-BETA1
cd /usr/ports/emulators/virtualbox-ose ; make install clean
Add needed options to /boot/loader.conf and /etc/rc.conf
After reboot try:
VBoxManage list ostypes
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-10-21 06:47:57 UTC
Responsible Changed
From-To: freebsd-ports-bugs->vbox

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Bernhard Froehlich 2013-11-13 13:09:37 UTC
It might be worth to try creating an default VirtualBox.xml file manually:

~/.VirtualBox/VirtualBox.xml

<VirtualBox xmlns=3D"http://www.innotek.de/VirtualBox-settings"
version=3D"1.12-freebsd">
</VirtualBox>

Some people have reported that it works for them but I don't know yet
why this only seems to affect FreeBSD 10 and worked fine in the past.

--=20
Bernhard Fr=F6hlich
http://www.bluelife.at/
Comment 3 George 2013-11-16 15:36:29 UTC
That not solves that issue. 
OS: FreeBSD BSD-VBOX 10.0-BETA3 FreeBSD 10.0-BETA3 #0: Wed Nov 13 01:16:17 MSK 2013     mike@BSD-VBOX:/usr/obj/usr/src/sys/BSDSERV  amd64

kldstat:
Id Refs Address            Size     Name
 1   13 0xffffffff80200000 87ca28   kernel
 2    1 0xffffffff80a7d000 20720    geom_mirror.ko
 3    3 0xffffffff80a9e000 57790    vboxdrv.ko
 4    2 0xffffffff80c12000 29c0     vboxnetflt.ko
 5    2 0xffffffff80c15000 8794     netgraph.ko
 6    1 0xffffffff80c1e000 1548     ng_ether.ko
 7    1 0xffffffff80c20000 3f30     vboxnetadp.ko

related packages list:
vde2-2.3.2                     User-mode virtual ethernet infrastructure
virtualbox-ose-4.3.2           A general-purpose full virtualizer for x86 hardware
virtualbox-ose-kmod-4.3.2      VirtualBox kernel module for FreeBSD
Comment 4 Oleg Ginzburg 2013-11-16 23:55:10 UTC
Same issue with VirtualBox 4.3.0 on my various systems :

- FreeBSD 10.0-BETA3, AMD Phenom(tm) 9650 Quad-Core Processor
- FreeBSD 11.0-CURRENT (r258212), AMD Phenom(tm) II X6 1090T Processor
- FreeBSD 11.0-CURRENT (r257892), Core(TM) i5-2430M CPU @ 2.40GHz

PS: Before FreeBSD 10-BETA stages VBOX worked perfectly.
Comment 5 W.Scholten 2013-11-20 16:49:50 UTC
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
Comment 6 dfilter service freebsd_committer freebsd_triage 2013-12-12 15:29:09 UTC
Author: decke
Date: Thu Dec 12 15:29:01 2013
New Revision: 336267
URL: http://svnweb.freebsd.org/changeset/ports/336267

Log:
  - Properly add $_GCC_RUNTIME to RPATH because that variable is evaluated
  after bsd.port.post.mk so it's hard to test for it.
  
  This fixes various issues that look like these ...
  
  VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
  VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed:
  /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required
  by /usr/local/lib/virtualbox/VBoxRT.so not found
  
  Type Manifest File: /root/.VirtualBox/xpti.dat
  nsNativeComponentLoader: autoregistering begins.
  nsNativeComponentLoader: autoregistering succeeded
  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.
  
  PR:		ports/182468
  PR:		ports/183085
  Submitted by:	bapt

Modified:
  head/emulators/virtualbox-ose/Makefile

Modified: head/emulators/virtualbox-ose/Makefile
==============================================================================
--- head/emulators/virtualbox-ose/Makefile	Thu Dec 12 15:24:47 2013	(r336266)
+++ head/emulators/virtualbox-ose/Makefile	Thu Dec 12 15:29:01 2013	(r336267)
@@ -3,6 +3,7 @@
 
 PORTNAME=	virtualbox-ose
 DISTVERSION=	4.2.20
+PORTREVISION=	1
 CATEGORIES=	emulators
 MASTER_SITES=	http://download.virtualbox.org/virtualbox/${DISTVERSION}/ \
 		http://tmp.chruetertee.ch/ \
@@ -46,7 +47,7 @@ HAS_CONFIGURE=	yes
 CONFIGURE_ARGS+=--with-gcc="${CC}" --with-g++="${CXX}" --passive-mesa
 USE_LDCONFIG=	${PREFIX}/lib/virtualbox
 
-CONFLICTS=	bcc-[0-9]* compat9x-*
+CONFLICTS=	bcc-[0-9]*
 CONFLICTS_INSTALL=	virtualbox-ose-devel-[3,4]* virtualbox-ose-legacy-[3,4]* virtualbox-ose-additions-[3,4]* virtualbox-ose-additions-devel-[3,4]*
 
 VBOXUSER?=	vboxusers
@@ -176,11 +177,7 @@ pre-everything::
 post-patch:
 	@${ECHO} 'VBOX_PATH_APP_PRIVATE_ARCH = ${PREFIX}/lib/virtualbox' > ${WRKSRC}/LocalConfig.kmk
 	@${ECHO} 'VBOX_PATH_SHARED_LIBS = ${PREFIX}/lib/virtualbox' >> ${WRKSRC}/LocalConfig.kmk
-.if defined(_GCC_RUNTIME)
-	@${ECHO} 'VBOX_WITH_RUNPATH = ${_GCC_RUNTIME}:${PREFIX}/lib/virtualbox' >> ${WRKSRC}/LocalConfig.kmk
-.else
-	@${ECHO} 'VBOX_WITH_RUNPATH = ${PREFIX}/lib/virtualbox' >> ${WRKSRC}/LocalConfig.kmk
-.endif
+	@var=${_GCC_RUNTIME}; ${ECHO} "VBOX_WITH_RUNPATH = $${var:+$${var}:}${PREFIX}/lib/virtualbox" >> ${WRKSRC}/LocalConfig.kmk
 	@${ECHO} 'VBOX_PATH_APP_PRIVATE = ${DATADIR}' >> ${WRKSRC}/LocalConfig.kmk
 	@${ECHO} 'VBOX_PATH_APP_DOCS = ${DOCSDIR}' >> ${WRKSRC}/LocalConfig.kmk
 	@${ECHO} 'VBOX_WITH_INSTALLER = 1' >> ${WRKSRC}/LocalConfig.kmk
_______________________________________________
svn-ports-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-ports-all
To unsubscribe, send any mail to "svn-ports-all-unsubscribe@freebsd.org"
Comment 7 Bernhard Froehlich freebsd_committer freebsd_triage 2013-12-12 15:29:57 UTC
State Changed
From-To: open->closed

A fix was committed. Thanks for the report!