Date: Thu, 22 Apr 2010 09:27:58 +0200 From: Bernhard Froehlich <decke@bluelife.at> To: <vova@fbsd.ru> Cc: freebsd-emulation@freebsd.org Subject: Re: VBoxManage CLI does not works any more ? Message-ID: <f3c0c7894444f041ab3a87d8bf1abcf3@bluelife.at> In-Reply-To: <1271911737.2639.62.camel@localhost> References: <1271848624.4068.6.camel@localhost> <6e74840f54319f7b98129e686bddf445@bluelife.at> <1271911737.2639.62.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Apr 2010 08:48:57 +0400, Vladimir Grebenschikov <vova@fbsd.ru> 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 <decke@bluelife.at> > 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 <vova@fbsd.ru> > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f3c0c7894444f041ab3a87d8bf1abcf3>