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

[Predrag Zečević - Technical Support Analyst]

On 08/06/18 12:36, Predrag Zečević - Technical Support Analyst wrote:
> 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
> Hi all,
> 
> we have had similar case in the past, and workaround was found:
> * https://www.illumos.org/issues/6919#note-7
> * that was added to wiki too: 
> https://wiki.openindiana.org/oi/7.2+VirtualBox#id-72VirtualBox-Virtualizationfeatures 
> 
> 
> Not sure what to do with this new case (should be illumos issue opened 
> or not)?
> 
> In any case, I have updated /hipster today and it has crashed. Output 
> excerpt from mdb -k (::msgbuf) command:
> ---<snip>---
> pseudo-device: vboxusbmon0
> vboxusbmon0 is /pseudo/vboxusbmon at 0
> 
> panic[cpu0]/thread=ffffff03d96e0520:
> recursive rw_enter, lp=ffffff03e71be928 wwwh=ffffff03d96e0524 
> thread=ffffff03d96e0520
> 
> 
> ffffff000fcb5440 unix:rw_panic+54 ()
> ffffff000fcb54b0 unix:rw_enter_sleep+37a ()
> ffffff000fcb55a0 genunix:as_fault+1f1 ()
> ffffff000fcb5630 unix:pagefault+96 ()
> ffffff000fcb5730 unix:trap+d88 ()
> ffffff000fcb5740 unix:cmntrap+e6 ()
> ffffff000fcb5880 vboxdrv:rtR0SegVBoxSolCreate+91 ()
> ffffff000fcb5960 genunix:as_map_locked+1a4 ()
> ffffff000fcb59d0 genunix:as_map+58 ()
> ffffff000fcb5a70 vboxdrv:rtR0MemObjNativeMapUser+28f ()
> ffffff000fcb5ae0 vboxdrv:RTR0MemObjMapUserTag+154 ()
> ffffff000fcb5b80 vboxdrv:SUPR0GipMap+138 ()
> ffffff000fcb5c10 vboxdrv:supdrvIOCtl+2e7c ()
> ffffff000fcb5cc0 vboxdrv:VBoxDrvSolarisIOCtl+375 ()
> ffffff000fcb5d00 genunix:cdev_ioctl+39 ()
> ffffff000fcb5d50 specfs:spec_ioctl+60 ()
> ffffff000fcb5de0 genunix:fop_ioctl+55 ()
> ffffff000fcb5f00 genunix:ioctl+9b ()
> ffffff000fcb5f10 unix:brand_sys_syscall+1f2 ()
> 
> dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel
> ---</snip>---
> 
> Booting to older BE (with latest VBox package - 5.2.16) worked for me too.
> 
> Regards.
>>
>> _______________________________________________
>> openindiana-discuss mailing list
>> openindiana-discuss at openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
> 

Hi all,

Is there any workaround for this case?
It prevents me from OI /hipster upgrade (I need VBox for various reasons)...

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!