From owner-freebsd-emulation@FreeBSD.ORG Thu Apr 22 07:27:59 2010 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7635106564A for ; Thu, 22 Apr 2010 07:27:59 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail.itac.at (mail.itac.at [91.205.172.9]) by mx1.freebsd.org (Postfix) with ESMTP id 5978F8FC0C for ; Thu, 22 Apr 2010 07:27:59 +0000 (UTC) Received: from [91.205.172.21] (helo=webmail.bluelife.at) by mail.itac.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1O4qpJ-0000bf-I9; Thu, 22 Apr 2010 09:27:57 +0200 MIME-Version: 1.0 Date: Thu, 22 Apr 2010 09:27:58 +0200 From: Bernhard Froehlich To: In-Reply-To: <1271911737.2639.62.camel@localhost> References: <1271848624.4068.6.camel@localhost> <6e74840f54319f7b98129e686bddf445@bluelife.at> <1271911737.2639.62.camel@localhost> Message-ID: X-Sender: decke@bluelife.at User-Agent: RoundCube Webmail/0.3.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-Spam-Score: 2.6 (++) X-Spam-Report: Spam detection software, running on the system "mail.itac.at", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Thu, 22 Apr 2010 08:48:57 +0400, Vladimir Grebenschikov wrote: > Hi > > It does not fail: > > $ VBoxSVC > > Sun VirtualBox XPCOM Server Version 3.1.6_OSE > (C) 2008-2010 Sun Microsystems, Inc. > All rights reserved. > > Starting event loop.... > [press Ctrl-C to quit] > ^CTerminated event loop. > XPCOM server has shutdown. > $ [...] Content analysis details: (2.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 3.4 FH_DATE_PAST_20XX The date is grossly in the future. 2.4 DNS_FROM_OPENWHOIS RBL: Envelope sender listed in bl.open-whois.org. -1.7 AWL AWL: From: address is in the auto white-list Cc: freebsd-emulation@freebsd.org Subject: Re: VBoxManage CLI does not works any more ? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2010 07:28:00 -0000 On Thu, 22 Apr 2010 08:48:57 +0400, Vladimir Grebenschikov wrote: > Hi > > It does not fail: > > $ VBoxSVC > ********************************************* > Sun VirtualBox XPCOM Server Version 3.1.6_OSE > (C) 2008-2010 Sun Microsystems, Inc. > All rights reserved. > > Starting event loop.... > [press Ctrl-C to quit] > ^CTerminated event loop. > XPCOM server has shutdown. > $ Hm okay. I did not expect that. What happens if you compile vbox with DEBUG enabled and then call VBoxManage? This should also give you a more verbose output of what is failing. -- Bernhard Fröhlich http://www.bluelife.at/ > -----Original Message----- > From: Bernhard Froehlich > To: vova@fbsd.ru > Cc: freebsd-emulation@freebsd.org > Subject: Re: VBoxManage CLI does not works any more ? > Date: Wed, 21 Apr 2010 14:09:26 +0200 > > On Wed, 21 Apr 2010 15:17:04 +0400, Vladimir Grebenschikov > wrote: >> Hi >> >> It worked for me before, but on recent version of port: >> >> $ VBoxManage start XP >> Sun VirtualBox Command Line Management Interface Version 3.1.6_OSE >> (C) 2005-2010 Sun Microsystems, Inc. >> All rights reserved. >> >> ERROR: failed to create a session object! >> ERROR: code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not >> registered (extended info not available) >> Most likely, the VirtualBox COM server is not running or failed to > start. >> $ >> >> Under VirtualBox UI it works as expected. > > Is this happening with virtualbox-ose-3.1.6_3? It sounds very much like > the png problem that was fixed 3 days ago in the port. > > To get a better error description you could start VBoxSVC on the shell and > see if it fails. If this does hot help then recompile with the DEBUG option > enabled and try again to start VBoxSVC.