[OpenIndiana-discuss] VirtualBox 5.2.14 crashing when attempting to start VM

[Predrag Zečević - Technical Support Analyst]

On 07/25/18 22:02, Michal Nowak wrote:
> On 07/25/18 04:46 PM, russell wrote:
>> Hi,
>>
>> I have been VirtualBox 5.2.14 since it came out without any issues 
>> until I performed a pkg update on 22nd July.
>> Everytime I perform a pkg update I always specify a new boot 
>> environment, so last update which VirtualBox 5.2.14 worked on is the 
>> one I performed on the 12th July. I have made this BE activate so I do 
>> not have to remember to select it on boot.
>>
>> Regards
>>
>> Russell
> 
> I think it might be the "eager FPU" changes which landed in illumos-gate 
> on June 13th:
> 
> https://github.com/illumos/illumos-gate/commit/4c28a617e3922d92a58e813a5b955eb526b9c386 
> 
> https://github.com/illumos/illumos-gate/commit/a32a1f376ed9360264e4a374608fdcc5c4927d63 
> 
> 
> It's reported to the authors of those patches at 
> https://github.com/joyent/smartos-live/issues/792.
> 
> I don't know of a workaround apart from sticking to versions before the 
> change.
> 
> Michal
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

Hi all,

just quick update on this: there were some changes in illumos, back (in 
July, I presume) which have messed up run of VirualBox package (solaris 
one, from virtualbox.org site, which is still running on old BE from 
July 6th, 2018).

I have tried with OI /hipster update last time and as I have started 
VBox guest, system has crashed (I can provide core dump if required - I 
was reading it, but not sure what is causing problems).
BTW, almost latest VBox (5.2.16) is running fine on mentioned BE:
$ uname -rosv
SunOS 5.11 illumos-229852ddf2 illumos


I have tried to compile VBox from source and after some tweaks, managed 
to get it compiled w/o errors, but it simply does not start (did not 
have time to do deeper analysis):
$ LD_LIBRARY_PATH=/usr/lib/qt/5.8/lib/amd64 ./VirtualBox

caused error:
---<snip>---
Failed to create the VirtualBoxClient COM object.
The application will now terminate.

[Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)]
---</snip>---

Till Wegmüller asked if I can boot VBox guest in qemu - not investigated 
although it is an option - I would like to stay at VirtualBox!

Does anyone knows how to solve this problem (failure of VBox prevents me 
from OI upgrade).

With best regards.
Predrag Zečević

-- 
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

tel: +49 - 6196 - 95058 - 15
mob: +49 - 174 - 3109288
fax: +49 - 6196 - 95058 - 94
e-mail: predrag.zecevic at 2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 87, 65812 Bad Soden am 
Taunus, Germany
registration: Amtsgericht Koenigstein (Germany), HRB 7303
managing director: Phil Douglas

http://www.2e-systems.com/ - Making your business fly!