From owner-freebsd-emulation@FreeBSD.ORG Wed Nov 20 17:00:02 2013 Return-Path: Delivered-To: vbox@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 07D04B7 for ; Wed, 20 Nov 2013 17:00:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EBDC0294A for ; Wed, 20 Nov 2013 17:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rAKH01hC089619 for ; Wed, 20 Nov 2013 17:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rAKH01cG089618; Wed, 20 Nov 2013 17:00:01 GMT (envelope-from gnats) Date: Wed, 20 Nov 2013 17:00:01 GMT Message-Id: <201311201700.rAKH01cG089618@freefall.freebsd.org> To: vbox@FreeBSD.org From: Photo stuff Subject: Re: ports/183085: emulators/virtualbox-ose failed to work on FreeBSD 10-BETA1 X-Mailman-Approved-At: Wed, 20 Nov 2013 17:42:38 +0000 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Photo stuff List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2013 17:00:02 -0000 The following reply was made to PR ports/183085; it has been noted by GNATS. From: Photo stuff To: bug-followup@FreeBSD.org, gosha-necr@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