[OpenIndiana-discuss] VirtualBox 7.1.4 error

[Carsten Grzemba]

Am 10.11.24 10:09 schrieb russell  <stream at willows7.myzen.co.uk>: 
> 
> Hi
> 
> Noticed when starting VirtualBox 7.1.4 getting the following error when 
> starting via the GUI
> 
> Failed to acquire the VirtualBox COM object.
> 
> The application will now terminate.
> 
> Details
> 
> Callee RC:
> 
> 	
> 
> NS_ERROR_FAILURE (0x80004005)
> 
> And now the VirtualBox GUI does not appear when using the GUI to start 
> VirtualBox Manager
> 
> If I use the cli to run VirtualBox then the VirtualBox Manager then it 
> starts but I am unable to start a VM as I get the error below.
> 
> Attempting to start the VM via the cli
> 
> $ /opt/VirtualBox/amd64/VirtualBoxVM --startvm "vbvm01" Qt WARNING: 
> Session DBus not running. Qt WARNING: Application will not react to 
> setting changes. Check your DBus installation. Segmentation Fault
> 
> $ /opt/VirtualBox/amd64/VBoxHeadless -startvm "vbvm01" Oracle VirtualBox 
> Headless Interface 7.1.4 Copyright (C) 2008-2024 Oracle and/or its 
> affiliates Segmentation Fault
> 
> Using the previous BE from the previous Saturday and then everything is 
> fine.
> 
> Russell
> 
> On 2024-11-09 13:16, russell wrote:
> >
> > Hi,
> >
> > Upgraded to the latest OI Hipster release illumos-b62492765b and 
> > found when I start VirtualBox 7.1.4 the following error appears
> >
> > The virtual machine 'vbvm01' has terminated unexpectedly during 
> > startup because of signal 11.
> >
> > Result Code:
> >
> > 
> >
> > NS_ERROR_FAILURE (0x80004005)
> >
> > Component:
> >
> > 
> >
> > MachineWrap
> >
> > Interface:
> >
> > 
> >
> > IMachine {e36a5081-a82a-40bd-9e4e-42a44d6ce50f}
> >
> > I am getting the same error for all my VB vms. I gogled the Result 
> > Code and found an article in the VirtualBox forums from 2018 
> > suggesting discarding the saved state, tried on one VM and found it 
> > did not work.
> >
> > Any thoughts on how to resolve the problem.
> >
> > TIA
> >
> > Russell
> >
> 

Before you start VirtualBox or "VBoxManage startvm", please start in terminal:
<signatureafterquotedtext>
</signatureafterquotedtext>
$ /opt/VirtualBox/amd64/VBoxSVC


and look for messages. If there same related to the startup abort, please share.



-- 

Carsten