VBoxManage CLI does not works any more ?

Vladimir Grebenschikov vova at fbsd.ru
Thu Apr 22 13:08:32 UTC 2010


Hi 

Looks like you are right, png involved here.

$ VBoxManage start XP
Sun VirtualBox Command Line Management Interface Version 3.1.6_OSE
(C) 2005-2010 Sun Microsystems, Inc.
All rights reserved.

Type Manifest File: /home/vova/.VirtualBox/xpti.dat
nsNativeComponentLoader: autoregistering begins.
*** Registering VirtualBox_Server_Module components (all right -- a generic module!)
pr_LoadLibraryByPathname(): Failed to load '/usr/local/lib/virtualbox/components/VBoxC.so'
nsNativeComponentLoader: SelfRegisterDll(VBoxC.so) Load FAILED with error: /usr/local/lib/virtualbox/components/VBoxC.so: Undefined symbol "png_set_longjmp_fn"
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)
pr_LoadLibraryByPathname(): Failed to load '/usr/local/lib/virtualbox/components/VBoxC.so'
nsNativeComponentLoader: GetFactory(VBoxC.so) Load FAILED with error: /usr/local/lib/virtualbox/components/VBoxC.so: Undefined symbol "png_set_longjmp_fn"
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.
ipcDConnectService Stats
 => number of worker threads: 1
nsStringStats
 => mAllocCount:             70
 => mReallocCount:           15
 => mFreeCount:              70
 => mShareCount:            108
 => mAdoptCount:             13
 => mAdoptFreeCount:         13
$


-----Original Message-----
From: Bernhard Froehlich <decke at bluelife.at>
To: vova at fbsd.ru
Cc: freebsd-emulation at freebsd.org
Subject: Re: VBoxManage CLI does not works any more ?
Date: Thu, 22 Apr 2010 09:27:58 +0200

On Thu, 22 Apr 2010 08:48:57 +0400, Vladimir Grebenschikov <vova at 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.


-- 
Vladimir B. Grebenschikov
vova at fbsd.ru


More information about the freebsd-emulation mailing list