Re: [oi-dev] Virtualbox crash

[Carsten Grzemba via oi-dev]

Am 15.09.2023 08:58 schrieb Stephan Althaus :Hello Carsten!





I have seen your new PR to VirtualBox.



I don't understand why it is a good idea to compile packges with GCC-12 

instead of GCC-10.



Shoudn't we stay with GCC-10 not to break further more things with an 

additional ABI incompatibility in the line GCC-7 - GCC-10 - GCC-12 ?



What will be the next standard-compiler (after GCCC-10) for illumos/OI, 

GCC-12 or GCC-13 ?





Would you be so kind and explain it in short, or maybe present a link 

for further reading?



Thanks!



Stephan







___

oi-dev mailing list

oi-dev@openindiana.org

https://openindiana.org/mailman/listinfo/oi-dev


Vbox builds with gcc10 or gcc11 always crash in c++ excepion handling. Only gcc7 or gcc12 builds survived.That's the reason.

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox crash

[Marcel Telka]

On Fri, Sep 15, 2023 at 10:29:20AM +0300, Toomas Soome via oi-dev wrote:
> we are planning gcc 13 (C23 features),

This one? https://github.com/illumos/gcc/tree/il-13_1_0

> unfortunately oi does not provide it yet, does it?

Yep, OI does not have gcc-13 yet.

-- 
+---+
| Marcel Telka   e-mail:   mar...@telka.sk  |
|homepage: http://telka.sk/ |
+---+

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox crash

[Toomas Soome via oi-dev]

> On 15. Sep 2023, at 09:58, Stephan Althaus  
> wrote:
> 
> Hello Carsten!
> 
> 
> I have seen your new PR to VirtualBox.
> 
> I don't understand why it is a good idea to compile packges with GCC-12 
> instead of GCC-10.
> 
> Shoudn't we stay with GCC-10 not to break further more things with an 
> additional ABI incompatibility in the line GCC-7 - GCC-10 - GCC-12 ?
> 
> What will be the next standard-compiler (after GCCC-10) for illumos/OI, 
> GCC-12 or GCC-13 ?
> 
> 
> Would you be so kind and explain it in short, or maybe present a link for 
> further reading?
> 
> Thanks!
> 
> Stephan
> 


we are planning gcc 13 (C23 features), unfortunately oi does not provide it 
yet, does it?

rgds,
toomas
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox crash

[Stephan Althaus]

Hello Carsten!


I have seen your new PR to VirtualBox.

I don't understand why it is a good idea to compile packges with GCC-12 
instead of GCC-10.


Shoudn't we stay with GCC-10 not to break further more things with an 
additional ABI incompatibility in the line GCC-7 - GCC-10 - GCC-12 ?


What will be the next standard-compiler (after GCCC-10) for illumos/OI, 
GCC-12 or GCC-13 ?



Would you be so kind and explain it in short, or maybe present a link 
for further reading?


Thanks!

Stephan



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox crash

[Carsten Grzemba via oi-dev]

Am 28.08.23 13:27 schrieb "Carsten Grzemba"  : 
> 
> 
> 
> Am 28.08.23 12:38 schrieb Toomas Soome  : 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > 
> > > On 28. Aug 2023, at 13:32, Carsten Grzemba via oi-dev 
> > >  wrote:
> > > 
> > > 
> > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > 
> > > > > #11 0x007b1eb5 in Medium::i_queryInfo 
> > > > > (this=this@entry=0xe004c0, fSetImageId=fSetImageId@entry=false,
> > > > >  fSetParentId=fSetParentId@entry=false, autoCaller=...)
> > > > >  at 
> > > > > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:7176
> > > > > #12 0x007b2dc5 in Medium::refreshState (this=0xe004c0, 
> > > > > autoCaller=..., aState=0xe0b1a0)
> > > > >  at 
> > > > > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:2180
> > > > > #13 0x009acf71 in MediumWrap::RefreshState (this=0xe004c0, 
> > > > > aState=0xe0b1a0)
> > > > >  at 
> > > > > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/out/solaris.amd64/debug/obj/VBoxAPIWrap/MediumWrap.cpp:1344
> > > > > 
> > > > 
> > > > 
> > > >  
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> > Those are bits you want to look into, as you get throw from:
> > 
> > 
> > Medium::i_queryInfo+0x2ae() 
> > 
> > 
> >  
> > 
> > rgds, 
> > 
> > toomas 
> > 
> > 
> >  
> > 
>  try 
>  {
>  /* skip accessibility checks for host drives */
>  if (m->hostDrive)
>  { 
>  success = true; 
>  --->> throw S_OK; 
>  } 
> 
> 
> ...8<..
> 
> 
>  }
>  catch (HRESULT aRC)
>  {
>  rc = aRC;
>  }
> 
> 
> Which is a very impressive application of C++-Exception ...
>  
> 
>  
> 
> -- 
> Carsten 
> 

A little bit confusing, the working binary compiled with gcc7:

$ gdb /opt/VirtualBox/amd64/VBoxSVC 
GNU gdb (GDB) 13.2

...

(gdb) b Medium::i_queryInfo
warning: could not convert 'Medium::i_queryInfo' from the host encoding 
(ISO-8859-1) to UTF-32.
This normally should not happen, please file a bug report.
Breakpoint 1 at 0x75f0c0: file 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp,
 line 7054.

and the not working compiled with gcc10


$ gdb /opt/VirtualBox/amd64/VBoxSVC 
GNU gdb (GDB) 13.2

...

(gdb) b Medium::i_queryInfo
warning: could not convert 'Medium::i_queryInfo' from the host encoding 
(ISO-8859-1) to UTF-32.
This normally should not happen, please file a bug report.
Breakpoint 1 at 0x7bb2a0: file 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/include/VBox/com/AutoLock.h,
 line 266.


the symbol Medium::i_queryInfo is mapped different.

-- 
Carsten
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox crash

[Carsten Grzemba via oi-dev]

Am 28.08.23 12:38 schrieb Toomas Soome  : 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> > 
> > On 28. Aug 2023, at 13:32, Carsten Grzemba via oi-dev 
> >  wrote:
> > 
> > 
> > 
> > > 
> > > 
> > > 
> > > 
> > > > 
> > > > #11 0x007b1eb5 in Medium::i_queryInfo 
> > > > (this=this@entry=0xe004c0, fSetImageId=fSetImageId@entry=false,  
> > > >  fSetParentId=fSetParentId@entry=false, autoCaller=...)
> > > >  at 
> > > > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:7176
> > > > #12 0x007b2dc5 in Medium::refreshState (this=0xe004c0, 
> > > > autoCaller=..., aState=0xe0b1a0)
> > > >  at 
> > > > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:2180
> > > > #13 0x009acf71 in MediumWrap::RefreshState (this=0xe004c0, 
> > > > aState=0xe0b1a0)
> > > >  at 
> > > > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/out/solaris.amd64/debug/obj/VBoxAPIWrap/MediumWrap.cpp:1344
> > > > 
> > > 
> > > 
> > >  
> > > 
> > 
> > 
> 
> 
> 
> 
> Those are bits you want to look into, as you get throw from:
> 
> 
> Medium::i_queryInfo+0x2ae() 
> 
> 
>  
> 
> rgds, 
> 
> toomas 
> 
> 
>  
> 
 try 
 {
 /* skip accessibility checks for host drives */
 if (m->hostDrive)
 { 
 success = true; 
 --->> throw S_OK; 
 } 


...8<..


 }
 catch (HRESULT aRC)
 {
 rc = aRC;
 }


Which is a very impressive application of C++-Exception ...
 

 

-- 
Carsten
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox crash

[Toomas Soome via oi-dev]

> On 28. Aug 2023, at 13:32, Carsten Grzemba via oi-dev 
>  wrote:
> 
>> 
>>> #11 0x007b1eb5 in Medium::i_queryInfo (this=this@entry=0xe004c0, 
>>> fSetImageId=fSetImageId@entry=false, 
>>> fSetParentId=fSetParentId@entry=false, autoCaller=...)
>>> at 
>>> /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:7176
>>> #12 0x007b2dc5 in Medium::refreshState (this=0xe004c0, 
>>> autoCaller=..., aState=0xe0b1a0)
>>> at 
>>> /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:2180
>>> #13 0x009acf71 in MediumWrap::RefreshState (this=0xe004c0, 
>>> aState=0xe0b1a0)
>>> at 
>>> /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/out/solaris.amd64/debug/obj/VBoxAPIWrap/MediumWrap.cpp:1344


Those are bits you want to look into, as you get throw from:

Medium::i_queryInfo+0x2ae()

rgds,
toomas___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox crash

[Udo Grabowski (IMK)]

Isn't that the same gcc-7/10 mixup again ? Somewhere hidden by indirect loading?
That gxx_personality_v0/Unwind_RaiseException_Phase2 stuff looks like its that
signature ... Set LD_DEBUG to 'files' or 'libs' and start it from that
commandline.

On 28/08/2023 11:30, Carsten Grzemba via oi-dev wrote:

Currently the G++10 compiled Virtualbox crashs in exception handling. The stack
looks similar to the problem with libexiv2 in 
https://www.illumos.org/issues/13824
but it seems the correct libs are loaded in the correct sequence.

(gdb) bt
#0  0x7fffaf4091ca in _lwp_kill () from /lib/64/libc.so.1
#1  0x7fffaf3ffa9a in thr_kill () from /lib/64/libc.so.1
#2  0x7fffaf39b762 in raise () from /lib/64/libc.so.1
#3  0x7fffaf374fa8 in abort () from /lib/64/libc.so.1
#4  0x7fffa67fa42d in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#5  0x7fffa67f7249 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#6  0x7fffa67f6099 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#7  0x7fffa67f6a8c in __gxx_personality_v0 () from
/usr/gcc/10/lib/amd64/libstdc++.so.6
#8  0x7fffa8235716 in _Unwind_RaiseException_Phase2 (exc=exc@entry=0xe5c410,
context=context@entry=0x7fffadfce5a0,
frames_p=frames_p@entry=0x7fffadfce690)
at
/jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:64
#9  0x7fffa8235dc1 in _Unwind_RaiseException (exc=0xe5c410)
at
/jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:136
#10 0x7fffa67f7570 in __cxa_throw () from 
/usr/gcc/10/lib/amd64/libstdc++.so.6
#11 0x007b1eb5 in Medium::i_queryInfo (this=this@entry=0xe004c0,
fSetImageId=fSetImageId@entry=false,
fSetParentId=fSetParentId@entry=false, autoCaller=...)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:7176
#12 0x007b2dc5 in Medium::refreshState (this=0xe004c0, autoCaller=...,
aState=0xe0b1a0)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:2180
#13 0x009acf71 in MediumWrap::RefreshState (this=0xe004c0, 
aState=0xe0b1a0)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/out/solaris.amd64/debug/obj/VBoxAPIWrap/MediumWrap.cpp:1344
#14 0x7fff8d47a040 in XPTC_InvokeByIndex (that=0xe00530, methodIndex=41,
paramCount=1, params=0xe0b1a0)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/reflect/xptcall/src/md/unix/xptcinvoke_x86_64_linux.cpp:221
#15 0x7fff8f7b53f9 in ipcDConnectService::OnInvoke (this=0xcf6c40, peer=2,
invoke=0xe0b170, opLen=18)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:4076
#16 0x7fff8f7b3f5d in ipcDConnectService::OnIncomingRequest (this=0xcf6c40,
peer=2, op=0xe0b170, opLen=18)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3706
#17 0x7fff8f7b1afb in DConnectWorker::Run (this=0xe0b650)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2979
#18 0x7fff8d4637bc in nsThread::Main (arg=0xd9a100)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118
#19 0x7fff8d4afdc1 in _pt_root (arg=0xe97870)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
#20 0x7fff8d4aff0a in _pt_iprt_root (Thread=0xe2cbb0, pvUser=0xe97870)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#21 0x7fff8d7d6563 in rtThreadMain (pThread=pThread@entry=0xe2cbb0,
NativeThread=NativeThread@entry=11,
pszThreadName=pszThreadName@entry=0xe2d488 "nspr-3")
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/common/misc/thread.cpp:727
#22 0x7fff8d8de1d3 in rtThreadNativeMain (pvArgs=0xe2cbb0)
at
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/r3/posix/thread-posix.cpp:386
#23 0x7fffaf401de7 in _thrp_setup () from /lib/64/libc.so.1
#24 0x7fffaf402130 in ?? () from /lib/64/libc.so.1

or the mdb view:

$C

7fffae33c0e0 libc.so.1`_lwp_kill+0xa()
7fffae33c110 libc.so.1`raise+0x22(6)
7fffae33c160 libc.so.1`abort+0x58()
7fffae33c1a0 
libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()
7fffae33c1c0 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9()
7fffae33c1e0 0x7fffa67f6099()
7fffae33c2d0 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc()
7fffae33c4a0 

Re: [oi-dev] Virtualbox crash

[Carsten Grzemba via oi-dev]

Am 28.08.23 12:22 schrieb Stephan Althaus  : 
> 
> 
>   
> 
> 
> 
>  
> 
> On 8/28/23 11:30, Carsten Grzemba via oi-dev wrote:
>  
>  
> >   
> > Currently the G++10 compiled Virtualbox crashs in exception handling. The 
> > stack looks similar to the problem with libexiv2 in 
> > https://www.illumos.org/issues/13824
> >  
> > but it seems the correct libs are loaded in the correct sequence.   
> >  
> > 
> >  
> >  
> > (gdb) bt
> >  #0 0x7fffaf4091ca in _lwp_kill () from /lib/64/libc.so.1
> >  #1 0x7fffaf3ffa9a in thr_kill () from /lib/64/libc.so.1
> >  #2 0x7fffaf39b762 in raise () from /lib/64/libc.so.1
> >  #3 0x7fffaf374fa8 in abort () from /lib/64/libc.so.1
> >  #4 0x7fffa67fa42d in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
> >  #5 0x7fffa67f7249 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
> >  #6 0x7fffa67f6099 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
> >  #7 0x7fffa67f6a8c in __gxx_personality_v0 () from 
> > /usr/gcc/10/lib/amd64/libstdc++.so.6
> >  #8 0x7fffa8235716 in _Unwind_RaiseException_Phase2 
> > (exc=exc@entry=0xe5c410, context=context@entry=0x7fffadfce5a0, 
> >  frames_p=frames_p@entry=0x7fffadfce690)
> >  at
> > /jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:64
> >  #9 0x7fffa8235dc1 in _Unwind_RaiseException (exc=0xe5c410)
> >  at
> > /jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:136
> >  #10 0x7fffa67f7570 in __cxa_throw () from 
> > /usr/gcc/10/lib/amd64/libstdc++.so.6
> >  #11 0x007b1eb5 in Medium::i_queryInfo (this=this@entry=0xe004c0, 
> > fSetImageId=fSetImageId@entry=false, 
> >  fSetParentId=fSetParentId@entry=false, autoCaller=...)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:7176
> >  #12 0x007b2dc5 in Medium::refreshState (this=0xe004c0, 
> > autoCaller=..., aState=0xe0b1a0)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:2180
> >  #13 0x009acf71 in MediumWrap::RefreshState (this=0xe004c0, 
> > aState=0xe0b1a0)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/out/solaris.amd64/debug/obj/VBoxAPIWrap/MediumWrap.cpp:1344
> >  #14 0x7fff8d47a040 in XPTC_InvokeByIndex (that=0xe00530, 
> > methodIndex=41, paramCount=1, params=0xe0b1a0)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/reflect/xptcall/src/md/unix/xptcinvoke_x86_64_linux.cpp:221
> >  #15 0x7fff8f7b53f9 in ipcDConnectService::OnInvoke (this=0xcf6c40, 
> > peer=2, invoke=0xe0b170, opLen=18)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:4076
> >  #16 0x7fff8f7b3f5d in ipcDConnectService::OnIncomingRequest 
> > (this=0xcf6c40, peer=2, op=0xe0b170, opLen=18)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3706
> >  #17 0x7fff8f7b1afb in DConnectWorker::Run (this=0xe0b650)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2979
> >  #18 0x7fff8d4637bc in nsThread::Main (arg=0xd9a100)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118
> >  #19 0x7fff8d4afdc1 in _pt_root (arg=0xe97870)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
> >  #20 0x7fff8d4aff0a in _pt_iprt_root (Thread=0xe2cbb0, pvUser=0xe97870)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
> >  #21 0x7fff8d7d6563 in rtThreadMain (pThread=pThread@entry=0xe2cbb0, 
> > NativeThread=NativeThread@entry=11, 
> >  pszThreadName=pszThreadName@entry=0xe2d488 "nspr-3")
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/common/misc/thread.cpp:727
> >  #22 0x7fff8d8de1d3 in rtThreadNativeMain (pvArgs=0xe2cbb0)
> >  at
> > /code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/r3/posix/thread-posix.cpp:386
> >  
> > #23 0x7fffaf401de7 in _thrp_setup () from /lib/64/libc.so.1
> >  #24 0x7fffaf402130 in ?? () from /lib/64/libc.so.1
> >  
> >  
> > 
> >  
> >  
> > or the mdb view:
> >  
> > > $C
> >  7fffae33c0e0 libc.so.1`_lwp_kill+0xa()
> >  7fffae33c110 libc.so.1`raise+0x22(6)
> >  7fffae33c160 libc.so.1`abort+0x58()
> >  7fffae33c1a0 
> > libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()
> >  7fffae33c1c0 

Re: [oi-dev] Virtualbox crash

[Stephan Althaus]

On 8/28/23 11:30, Carsten Grzemba via oi-dev wrote:
Currently the G++10 compiled Virtualbox crashs in exception handling. 
The stack looks similar to the problem with libexiv2 in 
https://www.illumos.org/issues/13824

but it seems the correct libs are loaded in the correct sequence.

(gdb) bt
#0  0x7fffaf4091ca in _lwp_kill () from /lib/64/libc.so.1
#1  0x7fffaf3ffa9a in thr_kill () from /lib/64/libc.so.1
#2  0x7fffaf39b762 in raise () from /lib/64/libc.so.1
#3  0x7fffaf374fa8 in abort () from /lib/64/libc.so.1
#4  0x7fffa67fa42d in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#5  0x7fffa67f7249 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#6  0x7fffa67f6099 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#7  0x7fffa67f6a8c in __gxx_personality_v0 () from 
/usr/gcc/10/lib/amd64/libstdc++.so.6
#8  0x7fffa8235716 in _Unwind_RaiseException_Phase2 
(exc=exc@entry=0xe5c410, context=context@entry=0x7fffadfce5a0,

    frames_p=frames_p@entry=0x7fffadfce690)
    at 
/jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:64

#9  0x7fffa8235dc1 in _Unwind_RaiseException (exc=0xe5c410)
    at 
/jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:136
#10 0x7fffa67f7570 in __cxa_throw () from 
/usr/gcc/10/lib/amd64/libstdc++.so.6
#11 0x007b1eb5 in Medium::i_queryInfo 
(this=this@entry=0xe004c0, fSetImageId=fSetImageId@entry=false,

    fSetParentId=fSetParentId@entry=false, autoCaller=...)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:7176
#12 0x007b2dc5 in Medium::refreshState (this=0xe004c0, 
autoCaller=..., aState=0xe0b1a0)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:2180
#13 0x009acf71 in MediumWrap::RefreshState (this=0xe004c0, 
aState=0xe0b1a0)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/out/solaris.amd64/debug/obj/VBoxAPIWrap/MediumWrap.cpp:1344
#14 0x7fff8d47a040 in XPTC_InvokeByIndex (that=0xe00530, 
methodIndex=41, paramCount=1, params=0xe0b1a0)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/reflect/xptcall/src/md/unix/xptcinvoke_x86_64_linux.cpp:221
#15 0x7fff8f7b53f9 in ipcDConnectService::OnInvoke (this=0xcf6c40, 
peer=2, invoke=0xe0b170, opLen=18)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:4076
#16 0x7fff8f7b3f5d in ipcDConnectService::OnIncomingRequest 
(this=0xcf6c40, peer=2, op=0xe0b170, opLen=18)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3706

#17 0x7fff8f7b1afb in DConnectWorker::Run (this=0xe0b650)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2979

#18 0x7fff8d4637bc in nsThread::Main (arg=0xd9a100)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118

#19 0x7fff8d4afdc1 in _pt_root (arg=0xe97870)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224

#20 0x7fff8d4aff0a in _pt_iprt_root (Thread=0xe2cbb0, pvUser=0xe97870)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#21 0x7fff8d7d6563 in rtThreadMain 
(pThread=pThread@entry=0xe2cbb0, NativeThread=NativeThread@entry=11,

    pszThreadName=pszThreadName@entry=0xe2d488 "nspr-3")
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/common/misc/thread.cpp:727

#22 0x7fff8d8de1d3 in rtThreadNativeMain (pvArgs=0xe2cbb0)
    at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/r3/posix/thread-posix.cpp:386

#23 0x7fffaf401de7 in _thrp_setup () from /lib/64/libc.so.1
#24 0x7fffaf402130 in ?? () from /lib/64/libc.so.1

or the mdb view:
> $C
7fffae33c0e0 libc.so.1`_lwp_kill+0xa()
7fffae33c110 libc.so.1`raise+0x22(6)
7fffae33c160 libc.so.1`abort+0x58()
7fffae33c1a0 
libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()

7fffae33c1c0 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9()
7fffae33c1e0 0x7fffa67f6099()
7fffae33c2d0 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc()
7fffae33c4a0 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
7fffae33c850 libgcc_s.so.1`_Unwind_RaiseException+0x331()
7fffae33c880 libstdc++.so.6.0.28`__cxa_throw+0x40()
7fffae33ca70 Medium::i_queryInfo+0x2ae()
7fffae33cab0 Medium::refreshState+0xa5()

[oi-dev] Virtualbox crash

[Carsten Grzemba via oi-dev]

Currently the G++10 compiled Virtualbox crashs in exception handling. The stack 
looks similar to the problem with libexiv2 in 
https://www.illumos.org/issues/13824
but it seems the correct libs are loaded in the correct sequence.   

(gdb) bt
#0 0x7fffaf4091ca in _lwp_kill () from /lib/64/libc.so.1
#1 0x7fffaf3ffa9a in thr_kill () from /lib/64/libc.so.1
#2 0x7fffaf39b762 in raise () from /lib/64/libc.so.1
#3 0x7fffaf374fa8 in abort () from /lib/64/libc.so.1
#4 0x7fffa67fa42d in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#5 0x7fffa67f7249 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#6 0x7fffa67f6099 in ?? () from /usr/gcc/10/lib/amd64/libstdc++.so.6
#7 0x7fffa67f6a8c in __gxx_personality_v0 () from 
/usr/gcc/10/lib/amd64/libstdc++.so.6
#8 0x7fffa8235716 in _Unwind_RaiseException_Phase2 (exc=exc@entry=0xe5c410, 
context=context@entry=0x7fffadfce5a0, 
 frames_p=frames_p@entry=0x7fffadfce690)
 at 
/jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:64
#9 0x7fffa8235dc1 in _Unwind_RaiseException (exc=0xe5c410)
 at 
/jenkins/jobs/oi-userland/workspace/components/developer/gcc-10/gcc-releases-gcc-10.5.0/libgcc/unwind.inc:136
#10 0x7fffa67f7570 in __cxa_throw () from 
/usr/gcc/10/lib/amd64/libstdc++.so.6
#11 0x007b1eb5 in Medium::i_queryInfo (this=this@entry=0xe004c0, 
fSetImageId=fSetImageId@entry=false, 
 fSetParentId=fSetParentId@entry=false, autoCaller=...)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:7176
#12 0x007b2dc5 in Medium::refreshState (this=0xe004c0, autoCaller=..., 
aState=0xe0b1a0)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Main/src-server/MediumImpl.cpp:2180
#13 0x009acf71 in MediumWrap::RefreshState (this=0xe004c0, 
aState=0xe0b1a0)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/out/solaris.amd64/debug/obj/VBoxAPIWrap/MediumWrap.cpp:1344
#14 0x7fff8d47a040 in XPTC_InvokeByIndex (that=0xe00530, methodIndex=41, 
paramCount=1, params=0xe0b1a0)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/reflect/xptcall/src/md/unix/xptcinvoke_x86_64_linux.cpp:221
#15 0x7fff8f7b53f9 in ipcDConnectService::OnInvoke (this=0xcf6c40, peer=2, 
invoke=0xe0b170, opLen=18)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:4076
#16 0x7fff8f7b3f5d in ipcDConnectService::OnIncomingRequest (this=0xcf6c40, 
peer=2, op=0xe0b170, opLen=18)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3706
#17 0x7fff8f7b1afb in DConnectWorker::Run (this=0xe0b650)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:2979
#18 0x7fff8d4637bc in nsThread::Main (arg=0xd9a100)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/xpcom/threads/nsThread.cpp:118
#19 0x7fff8d4afdc1 in _pt_root (arg=0xe97870)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:224
#20 0x7fff8d4aff0a in _pt_iprt_root (Thread=0xe2cbb0, pvUser=0xe97870)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/libs/xpcom18a4/nsprpub/pr/src/pthreads/ptthread.c:272
#21 0x7fff8d7d6563 in rtThreadMain (pThread=pThread@entry=0xe2cbb0, 
NativeThread=NativeThread@entry=11, 
 pszThreadName=pszThreadName@entry=0xe2d488 "nspr-3")
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/common/misc/thread.cpp:727
#22 0x7fff8d8de1d3 in rtThreadNativeMain (pvArgs=0xe2cbb0)
 at 
/code/github/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Runtime/r3/posix/thread-posix.cpp:386
#23 0x7fffaf401de7 in _thrp_setup () from /lib/64/libc.so.1
#24 0x7fffaf402130 in ?? () from /lib/64/libc.so.1


or the mdb view:
> $C
7fffae33c0e0 libc.so.1`_lwp_kill+0xa()
7fffae33c110 libc.so.1`raise+0x22(6)
7fffae33c160 libc.so.1`abort+0x58()
7fffae33c1a0 
libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()
7fffae33c1c0 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9()
7fffae33c1e0 0x7fffa67f6099()
7fffae33c2d0 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc()
7fffae33c4a0 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
7fffae33c850 libgcc_s.so.1`_Unwind_RaiseException+0x331()
7fffae33c880 libstdc++.so.6.0.28`__cxa_throw+0x40()
7fffae33ca70 Medium::i_queryInfo+0x2ae()
7fffae33cab0 Medium::refreshState+0xa5()
7fffae33cb00 MediumWrap::RefreshState+0x121()
7fffae33cbd0 VBoxXPCOM.so`XPTC_InvokeByIndex+0x1c7()
7fffae33cdd0 

Re: [oi-dev] virtualbox 6.1.26 ?

[Till Wegmueller]

They are in the progress to rewrite it to golang. I saw the code some 
time ago on their Github. But they are fighting to keep the ruby codes 
somehow available. Interested how they end up doing the rewrite.


In Any case a vagrant package would be nice.

Good luck packaging.

-Till

On 12.09.21 14:15, s...@pandora.be wrote:


As far as I can see vagrant works fine.

OpenIndiana is an excellent platform for vagrant with provider VirtualBox.

Vagrant also supports other providers such as VMware but obviously I use 
VirtualBox as provider.

Vagrant currently requires ruby and bsdtar (libarchive.de).
The Vagrant README file encourages you to compile your own ruby version which 
makes some sense.

Vagrant 2.2.19dev installs on top of ruby 2.7.4 fine.  It also works with the 
system provided ruby-26.

Vagrant is installing additional 'gems' and vagrant script/executable.

However on the Hashicorp (makers of vagrant) community list I've been warned 
that they are redesigning vagrant (supposedly) not to use ruby any longer (they 
may switch language - somebody said there).

I could give it a try ruby-27 and ruby-30 and see how far I get.

Regards,
David Stes

- Op 12 sep 2021 om 18:17 schreef Till Wegmueller toaster...@gmail.com:


Hello

Last time I checked vagrant did not build but good to know it now does
:) Any package would be welcome. Want to do an update to virtualbox and
vagrant/ruby?

-Till

On 12.09.21 07:05, s...@pandora.be wrote:



As I have stated before: We need more people helping with OI Hipster. We
lack contributions in almost every area:
creating/updating packages, testing and documentation. Things don't
happen magically. Efforts and engagement by volunteers is needed.
The companies involved in illumos seem only be interested in its server
use. So, the complex part of creating a desktop is up to the community...


This is true, I've already contributed docs under
http://docs.openindiana.org/handbook/community/ for Smalltalk-80 and TexLive
2021.

But of course there's an enormeous amount of other work to be done ...

Also keeping the docs up to date is a lot of work, I just noticed that the
TexLive docs still refer to TL 2020 not to the current TL 2021 ...  Same thing
for Squeak / Smalltalk the docs should be updated as well.

Regards,
David Stes


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] virtualbox 6.1.26 ?

[s...@pandora.be]

As far as I can see vagrant works fine.

OpenIndiana is an excellent platform for vagrant with provider VirtualBox.

Vagrant also supports other providers such as VMware but obviously I use 
VirtualBox as provider.

Vagrant currently requires ruby and bsdtar (libarchive.de).
The Vagrant README file encourages you to compile your own ruby version which 
makes some sense.

Vagrant 2.2.19dev installs on top of ruby 2.7.4 fine.  It also works with the 
system provided ruby-26.

Vagrant is installing additional 'gems' and vagrant script/executable.

However on the Hashicorp (makers of vagrant) community list I've been warned 
that they are redesigning vagrant (supposedly) not to use ruby any longer (they 
may switch language - somebody said there).

I could give it a try ruby-27 and ruby-30 and see how far I get.

Regards,
David Stes

- Op 12 sep 2021 om 18:17 schreef Till Wegmueller toaster...@gmail.com:

> Hello
> 
> Last time I checked vagrant did not build but good to know it now does
> :) Any package would be welcome. Want to do an update to virtualbox and
> vagrant/ruby?
> 
> -Till
> 
> On 12.09.21 07:05, s...@pandora.be wrote:
>> 
>>> As I have stated before: We need more people helping with OI Hipster. We
>>> lack contributions in almost every area:
>>> creating/updating packages, testing and documentation. Things don't
>>> happen magically. Efforts and engagement by volunteers is needed.
>>> The companies involved in illumos seem only be interested in its server
>>> use. So, the complex part of creating a desktop is up to the community...
>> 
>> This is true, I've already contributed docs under
>> http://docs.openindiana.org/handbook/community/ for Smalltalk-80 and TexLive
>> 2021.
>> 
>> But of course there's an enormeous amount of other work to be done ...
>> 
>> Also keeping the docs up to date is a lot of work, I just noticed that the
>> TexLive docs still refer to TL 2020 not to the current TL 2021 ...  Same 
>> thing
>> for Squeak / Smalltalk the docs should be updated as well.
>> 
>> Regards,
>> David Stes
>> 
>> 
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>> 
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] virtualbox 6.1.26 ?

[Till Wegmueller]

Hello

Last time I checked vagrant did not build but good to know it now does 
:) Any package would be welcome. Want to do an update to virtualbox and 
vagrant/ruby?


-Till

On 12.09.21 07:05, s...@pandora.be wrote:



As I have stated before: We need more people helping with OI Hipster. We
lack contributions in almost every area:
creating/updating packages, testing and documentation. Things don't
happen magically. Efforts and engagement by volunteers is needed.
The companies involved in illumos seem only be interested in its server
use. So, the complex part of creating a desktop is up to the community...


This is true, I've already contributed docs under 
http://docs.openindiana.org/handbook/community/ for Smalltalk-80 and TexLive 
2021.

But of course there's an enormeous amount of other work to be done ...

Also keeping the docs up to date is a lot of work, I just noticed that the 
TexLive docs still refer to TL 2020 not to the current TL 2021 ...  Same thing 
for Squeak / Smalltalk the docs should be updated as well.

Regards,
David Stes


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] virtualbox 6.1.26 ?

[s...@pandora.be]

> As I have stated before: We need more people helping with OI Hipster. We
> lack contributions in almost every area:
> creating/updating packages, testing and documentation. Things don't
> happen magically. Efforts and engagement by volunteers is needed.
> The companies involved in illumos seem only be interested in its server
> use. So, the complex part of creating a desktop is up to the community...

This is true, I've already contributed docs under 
http://docs.openindiana.org/handbook/community/ for Smalltalk-80 and TexLive 
2021.

But of course there's an enormeous amount of other work to be done ...

Also keeping the docs up to date is a lot of work, I just noticed that the 
TexLive docs still refer to TL 2020 not to the current TL 2021 ...  Same thing 
for Squeak / Smalltalk the docs should be updated as well.

Regards,
David Stes


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] virtualbox 6.1.26 ?

[Andreas Wacknitz]

Am 9/12/21 um 11:51 AM schrieb s...@pandora.be:

Are there plans to update the OI virtualbox package ?

OI Hipster is a community project. Anybody can update packages locally
and create PR's to get it integrated into OI.

Yes correct of course.

VirtualBox 6.1.22 is working fine ...

I am using it with "vagrant" (with VirtualBox as "vagrant provider") and ruby 
2.7.3

$  vagrant --version
Vagrant 2.2.19.dev

$ ruby --version
ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [i386-solaris2.11]

The ruby is compiled from source as Hashicorp recommends (they  recommend not 
to use system provided ruby).

An IPS vagrant package for OI would be nice (has anyone already made one ?)

For ruby upgrade to 2.7.4 is also possible. But ruby 3.0.2 seems not to compile 
on OpenIndiana for the moment.

David Stes

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



As I have stated before: We need more people helping with OI Hipster. We
lack contributions in almost every area:
creating/updating packages, testing and documentation. Things don't
happen magically. Efforts and engagement by volunteers is needed.
The companies involved in illumos seem only be interested in its server
use. So, the complex part of creating a desktop is up to the community...

Andreas


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] virtualbox 6.1.26 ?

[s...@pandora.be]

>>
>> Are there plans to update the OI virtualbox package ?
> 
> OI Hipster is a community project. Anybody can update packages locally
> and create PR's to get it integrated into OI.

Yes correct of course.

VirtualBox 6.1.22 is working fine ...

I am using it with "vagrant" (with VirtualBox as "vagrant provider") and ruby 
2.7.3

$  vagrant --version   
Vagrant 2.2.19.dev

$ ruby --version   
ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [i386-solaris2.11]

The ruby is compiled from source as Hashicorp recommends (they  recommend not 
to use system provided ruby).

An IPS vagrant package for OI would be nice (has anyone already made one ?)

For ruby upgrade to 2.7.4 is also possible. But ruby 3.0.2 seems not to compile 
on OpenIndiana for the moment.

David Stes

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] virtualbox 6.1.26 ?

[Andreas Wacknitz]

Am 9/12/21 um 10:56 AM schrieb s...@pandora.be:

Hi,

I just updated succesfully to the latest OpenIndiana/Hipster on my system

$ pkg list userland-incorporation
NAME (PUBLISHER)  VERSIONIFO
consolidation/userland/userland-incorporation 0.5.11-2020.0.1.14424  i--

This is the userland package from :

Packaging Date: Sat Sep 11 16:42:38 2021

It has the Smalltalk-80 language package that I maintain :

$ pkg list cog-spur
NAME (PUBLISHER)  VERSIONIFO
runtime/smalltalk/cog-spur5.0.3066-2020.0.1.0i--

However it still has VirtualBox 6.1.22 :

$ pkg list virtualbox
NAME (PUBLISHER)  VERSIONIFO
system/virtualbox 6.1.22-2020.0.1.2  i--

The virtualbox package is provided by and part of userland-incorporation:

$ pkg contents -m userland-incorporation | grep virtualbox
depend facet.version-lock.system/virtualbox=true 
fmri=system/virtualbox@6.1.22-2020.0.1.2 type=incorporate
depend facet.version-lock.system/virtualbox/virtualbox-additions=true 
fmri=system/virtualbox/virtualbox-additions@6.1.22-2020.0.1.2 type=incorporate

The current version since July is 6.1.26

https://www.virtualbox.org/wiki/Downloads

which is VirtualBox-6.1.26-145957-Solaris.p5p

(from Innotek/Oracle)

Are there plans to update the OI virtualbox package ?


OI Hipster is a community project. Anybody can update packages locally
and create PR's to get it integrated into OI.

Regards,
Andreas

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] virtualbox 6.1.26 ?

[s...@pandora.be]

Hi,

I just updated succesfully to the latest OpenIndiana/Hipster on my system

$ pkg list userland-incorporation  
NAME (PUBLISHER)  VERSIONIFO
consolidation/userland/userland-incorporation 0.5.11-2020.0.1.14424  i--

This is the userland package from :

   Packaging Date: Sat Sep 11 16:42:38 2021

It has the Smalltalk-80 language package that I maintain :

$ pkg list cog-spur  
NAME (PUBLISHER)  VERSIONIFO
runtime/smalltalk/cog-spur5.0.3066-2020.0.1.0i--

However it still has VirtualBox 6.1.22 :

$ pkg list virtualbox
NAME (PUBLISHER)  VERSIONIFO
system/virtualbox 6.1.22-2020.0.1.2  i--

The virtualbox package is provided by and part of userland-incorporation:

$ pkg contents -m userland-incorporation | grep virtualbox 
depend facet.version-lock.system/virtualbox=true 
fmri=system/virtualbox@6.1.22-2020.0.1.2 type=incorporate
depend facet.version-lock.system/virtualbox/virtualbox-additions=true 
fmri=system/virtualbox/virtualbox-additions@6.1.22-2020.0.1.2 type=incorporate

The current version since July is 6.1.26

https://www.virtualbox.org/wiki/Downloads

which is VirtualBox-6.1.26-145957-Solaris.p5p

(from Innotek/Oracle)

Are there plans to update the OI virtualbox package ?

Thanks,
David Stes

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Virtualbox additions

[Alexander Pyhalov via oi-dev]

Hello.
I'm asking for some kind of review and testing.

I've created several PRs:
https://github.com/OpenIndiana/oi-userland/pull/4637 - Adds virtualbox additions
https://github.com/OpenIndiana/oi-userland/pull/4660 - Allows using swrast with 
virtualbox-provided libGL
https://github.com/OpenIndiana/oi-userland/pull/4664 - Facilitates testing 
virtualbox GL libraries, as they are  64-bit only

Long story short.

VirtualBox guest additions (especially, swrast acceleration)  have always 
worked on OI by chance (or due to some series of bugs).
First of all, /lib/opengl/ogl_vendor_select tried to create links in wrong 
directory /system/volatile/opengl , so script efficiently didn't work.
If we fix this, we find out that Mesa swrast driver is not loaded due to 
missing link to libglapi, which was earlier taken from mesa libGL.so (now it's 
replaced with VirtualBox).

Later, if we fix Mesa and link dri drivers to libglapi, mesa libGL will not 
work , as our build system will consider libGL.so->libglapi.so link 
unnecessary, so we should avoid -Bdirect -z ignore.

Now, we have more-or-less working VirtualBox GL libraries for 64-bit apps, but 
we don't ship 32-bit guest additions, so we use Mesa libraries for 32-bit apps. 
GLXgears seems to be happy with 64-bit libGL from VirtualBox (to test it I had 
to add 64-bit glxgears version), but compiz is not, as virtualbox libraries 
don't set GLX visuals for depth 32 (don't know why)).
So, I've decided to avoid enabling virtualbox GL libraries by default. User can 
explicitly enable them by setting ogl-select service options/vendor property to 
"vbox". 

Happy testing.


Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] VirtualBox and recent illumos-gate

[Alexander Pyhalov via oi-dev]

Recent illumos-gate changes have broken KVM and VirtualBox. 
Issue: https://www.illumos.org/issues/9761. 

Note, that we've never delivered VirtualBox for OI and Solaris binaries just 
worked. Now it's no longer a case, and VirtualBox kernel modules should be 
patched. Well, I don't have enough skills (and perhaps even more important - 
free time) to do this, so any help would be appreciated...

Best regards, 
Alexander Pyhalov, 
system administrator of Southern Federal University IT department


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Virtualbox Xorg video driver compatible with 1.19.5

[Aurélien Larcher]

Hi,
as the current Guest Additions do not support Xorg 1.19 for Solaris,
Virtualbox users can install the Guest Additions as usual, then the package:

pkg://userland/x11/server/xorg/driver/xorg-video-vboxvideo@1.0.1
,5.11-2017.0.0.0:20171110T233520Z

from:

http://pkg.openindiana.org/xorg-testing

Assuming software installation rights (with pfexec or sudo):

pkg install -g http://pkg.openindiana.org/xorg-testing
pkg://userland/x11/server/xorg/driver/xorg-video-vboxvideo@1.0.1
,5.11-2017.0.0.0:20171110T233520Z

Thanks go to Michael Thayer who created the repository at
https://cgit.freedesktop.org/xorg/driver/xf86-video-vbox
and as usual to Alan and Niveditha for their kind help.

Kind regards

Aurelien

-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

Jim Klimov  writes:

[...]

Harry wrote:

>>   Installation of  partially failed.
>>Do you see anything like that?

Jim K replied:
> No, I think I did not install this release yet. If you re-install with
> the patched vboxconfig.sh also including a `set -x` line early on
> (edit the patched script with `vi` and note that packaging metadata
> like size and cksum will differ from examples), you can get a more
> detailed output that can glean the cause of non-zero (unsuccessful)
> return code.
>
> I am not sure I'll very soon have time to inspect this myself, but as
> long as the result appears to work - it may be ok to the first order
> of approximation ;)

I was actually directing my comment to G B who started the thread, but
he seems to have moved on. I thought since he edited the docu in short
order that he might have tried your patches too, and wanted to know If
I was the lone ranger.

Thanks again for your good work on the patches... and as you say, at least
it DOES work.



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Al Slater]

On 31/05/2017 14:13, Peter Tribble wrote:
> 
> 
> On Mon, May 29, 2017 at 8:10 PM, Harry Putnam  > wrote:
> 
> Far as I understood things... anything above 5.0.X, that is, any of
> the 5.1.x series will not install due to requiring gt5 I think it was.
> 
> 
> It includes its own private copy of Qt, rather than requiring the
> OS to have one (which in the case of Solaris it usually won't).
> 
> Actually, I suspect the problem is more likely to be
> 
> https://www.illumos.org/issues/5709
> 
> If you run VirtualBox with LD_DEBUG=versions you'll see (you have to do
> this as root otherwise setuid gets in the way)
> 
> ...
> 19254: 1: version needed processing:
> file=/opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5
> 19254: 1: fileversion
> 19254: 1: libc.so.1   SUNW_1.22.7
> 19254: 1:
> 19254: 1:
> 19254: 1: ld.so.1: VirtualBox: fatal: libc.so.1: version 'SUNW_1.22.7'
> not found (required by file /opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5)
> ...

Could be fixed by integrating the fix at
https://www.illumos.org/issues/5709 ?


-- 
Al Slater



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

Peter Tribble  writes:

> On Mon, May 29, 2017 at 8:10 PM, Harry Putnam  wrote:
>
>> Far as I understood things... anything above 5.0.X, that is, any of
>> the 5.1.x series will not install due to requiring gt5 I think it was.
>>
>
> It includes its own private copy of Qt, rather than requiring the
> OS to have one (which in the case of Solaris it usually won't).
>
> Actually, I suspect the problem is more likely to be
>
> https://www.illumos.org/issues/5709
>
> If you run VirtualBox with LD_DEBUG=versions you'll see (you have to do
> this as root otherwise setuid gets in the way)
>
> ...
> 19254: 1: version needed processing:
> file=/opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5
> 19254: 1: fileversion
> 19254: 1: libc.so.1   SUNW_1.22.7
> 19254: 1:
> 19254: 1:
> 19254: 1: ld.so.1: VirtualBox: fatal: libc.so.1: version 'SUNW_1.22.7' not
> found (required by file /opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5)
> ...
>
> A quick look at why it wants that version of libc using pvs
>
> pvs -vs libQt5XcbQpaVBox.so.5
> ...
> libc.so.1 (SUNW_1.22.7):
> asprintf;

Can you say what version of Vbox this output is from.  I do not see
any indication of its version.


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Igor Kozhukhov]

> On May 31, 2017, at 4:19 PM, Alexander Pyhalov  wrote:
> 
> On 05/31/17 04:13 PM, Peter Tribble wrote:
>> On Mon, May 29, 2017 at 8:10 PM, Harry Putnam  wrote:
>>> Far as I understood things... anything above 5.0.X, that is, any of
>>> the 5.1.x series will not install due to requiring gt5 I think it was.
>>> 
>> It includes its own private copy of Qt, rather than requiring the
>> OS to have one (which in the case of Solaris it usually won't).
>> Actually, I suspect the problem is more likely to be
>> https://www.illumos.org/issues/5709
>> If you run VirtualBox with LD_DEBUG=versions you'll see (you have to do
>> this as root otherwise setuid gets in the way)
>> ...
>> 19254: 1: version needed processing:
>> file=/opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5
>> 19254: 1: fileversion
>> 19254: 1: libc.so.1   SUNW_1.22.7
>> 19254: 1:
>> 19254: 1:
>> 19254: 1: ld.so.1: VirtualBox: fatal: libc.so.1: version 'SUNW_1.22.7' not
>> found (required by file /opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5)
>> ...
>> A quick look at why it wants that version of libc using pvs
>> pvs -vs libQt5XcbQpaVBox.so.5
>> ...
>> libc.so.1 (SUNW_1.22.7):
>> asprintf;
> 
> Time to think about compiling own VirtualBox version? :)

time to fork illumos to your own and fix it :)
it will be more easy fix it on illumos side and use binaries as is :)

-Igor

> -- 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org 
> https://openindiana.org/mailman/listinfo/oi-dev 
> 
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Alexander Pyhalov]

On 05/31/17 04:13 PM, Peter Tribble wrote:

On Mon, May 29, 2017 at 8:10 PM, Harry Putnam  wrote:


Far as I understood things... anything above 5.0.X, that is, any of
the 5.1.x series will not install due to requiring gt5 I think it was.



It includes its own private copy of Qt, rather than requiring the
OS to have one (which in the case of Solaris it usually won't).

Actually, I suspect the problem is more likely to be

https://www.illumos.org/issues/5709

If you run VirtualBox with LD_DEBUG=versions you'll see (you have to do
this as root otherwise setuid gets in the way)

...
19254: 1: version needed processing:
file=/opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5
19254: 1: fileversion
19254: 1: libc.so.1   SUNW_1.22.7
19254: 1:
19254: 1:
19254: 1: ld.so.1: VirtualBox: fatal: libc.so.1: version 'SUNW_1.22.7' not
found (required by file /opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5)
...

A quick look at why it wants that version of libc using pvs

pvs -vs libQt5XcbQpaVBox.so.5
...
 libc.so.1 (SUNW_1.22.7):
 asprintf;



Time to think about compiling own VirtualBox version? :)

--
С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Peter Tribble]

On Mon, May 29, 2017 at 8:10 PM, Harry Putnam  wrote:

> Far as I understood things... anything above 5.0.X, that is, any of
> the 5.1.x series will not install due to requiring gt5 I think it was.
>

It includes its own private copy of Qt, rather than requiring the
OS to have one (which in the case of Solaris it usually won't).

Actually, I suspect the problem is more likely to be

https://www.illumos.org/issues/5709

If you run VirtualBox with LD_DEBUG=versions you'll see (you have to do
this as root otherwise setuid gets in the way)

...
19254: 1: version needed processing:
file=/opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5
19254: 1: fileversion
19254: 1: libc.so.1   SUNW_1.22.7
19254: 1:
19254: 1:
19254: 1: ld.so.1: VirtualBox: fatal: libc.so.1: version 'SUNW_1.22.7' not
found (required by file /opt/VirtualBox/amd64/libQt5XcbQpaVBox.so.5)
...

A quick look at why it wants that version of libc using pvs

pvs -vs libQt5XcbQpaVBox.so.5
...
libc.so.1 (SUNW_1.22.7):
asprintf;

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

Aurélien Larcher  writes:

> On Tue, May 30, 2017 at 10:12 PM, Harry Putnam  wrote:
>
>> Aurélien Larcher  writes:
>>
>> > We have qt5 :)
>>
>> Please excuse my ill-informedness.
>>
>> Can you say when that happened off the top of your head... no need for
>> exactness.
>>
>
> I provided a first build end of last year based on the beta, we upstreamed
> a few patches then we merged the pull-request to add the stable 5.8 on
> April 5.

Thank you sir; for the full report


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Aurélien Larcher]

On Tue, May 30, 2017 at 10:12 PM, Harry Putnam  wrote:

> Aurélien Larcher  writes:
>
> > We have qt5 :)
>
> Please excuse my ill-informedness.
>
> Can you say when that happened off the top of your head... no need for
> exactness.
>

I provided a first build end of last year based on the beta, we upstreamed
a few patches then we merged the pull-request to add the stable 5.8 on
April 5.


>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

Jim Klimov  writes:

> I am not sure I'll very soon have time to inspect this myself, but as
> long as the result appears to work - it may be ok to the first order
> of approximation ;)

You've done quite a lot and been very helpful... already.


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

Aurélien Larcher  writes:

> We have qt5 :)

Please excuse my ill-informedness.

Can you say when that happened off the top of your head... no need for
exactness. 


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Aurélien Larcher]

On Mon, May 29, 2017 at 9:10 PM, Harry Putnam  wrote:

> Harry Putnam  writes:
>
> > G B via oi-dev  writes:
> >
> >> I added documentation to the VirtualBox page on the wiki:
> >> https://wiki.openindiana.org/oi/7.2+VirtualBox
> >
> > I might just be blind, but not seeing whatever was added there.
> > Can you mention a page search term that will lead me to your additions?
>
> Please ignore... yes I am blind.
>
> I'd like to know if you were able to get a clean install of lastest
> vbox following those directions?
>
> Far as I understood things... anything above 5.0.X, that is, any of
> the 5.1.x series will not install due to requiring gt5 I think it was.
>

We have qt5 :)


>
> I was able to install 5.0.40 following JimKs' README and using his
> patches.
>
> I get it installed but have a curious error at the end:
> `Installation of  partially failed.'
>
> The error does NOT prevent using the installed Vbox-5.0.40
>
>   [...]
>
>   Detected an opensource Solaris descendant, assuming snv_151 compatibility
>   Detected Solaris 11 Version 151
>Loading VirtualBox kernel modules...
>   - Loaded: Host module
>   - Loaded: NetAdapter module
>   - Loaded: NetFilter (STREAMS) module
>   - Loaded: USBMonitor module
>   - Loaded: USB module
>Configuring services...
>   - Enabled: Zone access service
>Installing MIME types and icons...
>Installing Python bindings...
>   - Installed: Bindings for Python 2.7
>Updating the boot archive...
>
>Installation of  partially failed.
>
> Do you see anything like that?
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

Harry Putnam  writes:


> Far as I understood things... anything above 5.0.X, that is, any of
> the 5.1.x series will not install due to requiring gt5 I think it was.
 ^^^
 qt5



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Jim Klimov]

On May 29, 2017 9:10:46 PM GMT+02:00, Harry Putnam  wrote:
>Harry Putnam  writes:
>
>> G B via oi-dev  writes:
>>
>>> I added documentation to the VirtualBox page on the wiki:
>>> https://wiki.openindiana.org/oi/7.2+VirtualBox
>>
>> I might just be blind, but not seeing whatever was added there.
>> Can you mention a page search term that will lead me to your
>additions?
>
>Please ignore... yes I am blind.
>
>I'd like to know if you were able to get a clean install of lastest
>vbox following those directions?
>
>Far as I understood things... anything above 5.0.X, that is, any of
>the 5.1.x series will not install due to requiring gt5 I think it was.
>
>I was able to install 5.0.40 following JimKs' README and using his
>patches.
>
>I get it installed but have a curious error at the end:
>`Installation of  partially failed.'   
>
>The error does NOT prevent using the installed Vbox-5.0.40
>
>  [...]
>  
>Detected an opensource Solaris descendant, assuming snv_151
>compatibility
>  Detected Solaris 11 Version 151
>   Loading VirtualBox kernel modules...
>  - Loaded: Host module
>  - Loaded: NetAdapter module
>  - Loaded: NetFilter (STREAMS) module
>  - Loaded: USBMonitor module
>  - Loaded: USB module
>   Configuring services...
>  - Enabled: Zone access service
>   Installing MIME types and icons...
>   Installing Python bindings...
>  - Installed: Bindings for Python 2.7
>   Updating the boot archive...
>   
>   Installation of  partially failed.
>
>Do you see anything like that?
>
>
>
>___
>oi-dev mailing list
>oi-dev@openindiana.org
>https://openindiana.org/mailman/listinfo/oi-dev

No, I think I did not install this release yet. If you re-install with the 
patched vboxconfig.sh also including a `set -x` line early on (edit the patched 
script with `vi` and note that packaging metadata like size and cksum will 
differ from examples), you can get a more detailed output that can glean the 
cause of non-zero (unsuccessful) return code.

I am not sure I'll very soon have time to inspect this myself, but as long as 
the result appears to work - it may be ok to the first order of approximation  
;)

Jim
--
Typos courtesy of K-9 Mail on my Redmi Android

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

Harry Putnam  writes:

> G B via oi-dev  writes:
>
>> I added documentation to the VirtualBox page on the wiki:
>> https://wiki.openindiana.org/oi/7.2+VirtualBox
>
> I might just be blind, but not seeing whatever was added there.
> Can you mention a page search term that will lead me to your additions?

Please ignore... yes I am blind.

I'd like to know if you were able to get a clean install of lastest
vbox following those directions?

Far as I understood things... anything above 5.0.X, that is, any of
the 5.1.x series will not install due to requiring gt5 I think it was.

I was able to install 5.0.40 following JimKs' README and using his
patches.

I get it installed but have a curious error at the end:
`Installation of  partially failed.'   

The error does NOT prevent using the installed Vbox-5.0.40

  [...]
  
  Detected an opensource Solaris descendant, assuming snv_151 compatibility
  Detected Solaris 11 Version 151
   Loading VirtualBox kernel modules...
  - Loaded: Host module
  - Loaded: NetAdapter module
  - Loaded: NetFilter (STREAMS) module
  - Loaded: USBMonitor module
  - Loaded: USB module
   Configuring services...
  - Enabled: Zone access service
   Installing MIME types and icons...
   Installing Python bindings...
  - Installed: Bindings for Python 2.7
   Updating the boot archive...
   
   Installation of  partially failed.

Do you see anything like that?



___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Harry Putnam]

G B via oi-dev  writes:

> I added documentation to the VirtualBox page on the wiki:
> https://wiki.openindiana.org/oi/7.2+VirtualBox

I might just be blind, but not seeing whatever was added there.
Can you mention a page search term that will lead me to your additions?


___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Aurélien Larcher]

On Mon, May 29, 2017 at 12:42 AM, G B  wrote:

> I added documentation to the VirtualBox page on the wiki:
>
> https://wiki.openindiana.org/oi/7.2+VirtualBox
>

Thank you, very much appreciated! :)


>
>
>
> On Sunday, May 28, 2017 4:34 PM, G B via oi-dev 
> wrote:
>
>
> Thank you
>
>
> On Sunday, May 28, 2017 4:11 PM, Aurélien Larcher <
> aurelien.larc...@gmail.com> wrote:
>
>
>
>
> On Sun, May 28, 2017 at 10:57 PM, G B via oi-dev 
> wrote:
>
> Today I downloaded the latest Hipster release and subsequently attempted
> to install Virtualbox 5.1.22, 5.0.40, and 4.3.40.  All of them failed.
>
> For 5.1.22:
> Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
> Oracle Corporation
> ## Executing checkinstall script.
> Checking package dependencies...
> ## Missing packages:
> ## IPS :  system/library/gcc/gcc-c++- runtime or
> system/library/gcc-45-runtime system/library/gcc/gcc-c- runtime or
> system/library/gcc-45-runtime
> ## SVr4:  SUNWPython SUNWPython-devel
> ##
> ## Please install either the IPS or SVr4 packages before installing
> VirtualBox.
> pkgadd: ERROR: checkinstall script did not complete successfully
>
> Installation of  failed.
> No changes were made to the system.
>
> For 5.0.40:
> Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
> Oracle Corporation
> ## Executing checkinstall script.
> Checking package dependencies...
> ## Missing packages:
> ## IPS :  system/library/gcc/gcc-c++- runtime or
> system/library/gcc-45-runtime system/library/gcc/gcc-c- runtime or
> system/library/gcc-45-runtime
> ## SVr4:  SUNWPython SUNWPython-devel
> ##
> ## Please install either the IPS or SVr4 packages before installing
> VirtualBox.
> pkgadd: ERROR: checkinstall script did not complete successfully
>
> Installation of  failed.
> No changes were made to the system.
>
> For 4.3.40:
> Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
> Oracle Corporation
> ## Executing checkinstall script.
> Checking package dependencies...
> ## Missing packages:
> ## IPS :  system/library/gcc/gcc-c++- runtime or
> system/library/gcc-45-runtime system/library/gcc/gcc-c- runtime or
> system/library/gcc-45-runtime
> ## SVr4:  SUNWPython SUNWPython-devel
> ##
> ## Please install either the IPS or SVr4 packages before installing
> VirtualBox.
> pkgadd: ERROR: checkinstall script did not complete successfully
>
> Installation of  failed.
> No changes were made to the system.
>
> Virtualbox used to install on the old OpenSolaris.  It is kind of ironic
> that Sun created Virtualbox and Oracle still releases a package for
> Solaris, but none of them will install.  Why and how do I get Virtualbox
> installed, or is it not worth the effort?  If I can't run Virtualbox then
> Hipster is useless to me.
>
>
> This has been discussed several times before on the MLs.
> The error is that the pre-install script checks that 'gcc-45-runtime' is
> installed but this package does not exist on Hipster, only on Solaris.
>
> You can look at Jim's scripts to work around the issue:
>
> https://github.com/jimklimov/vboxconfig_sh
>
> Now if there was a page on the Wiki about Virtualbox, maybe we would not
> need to answer the same question every month :)
>
>
>
>
>
> __ _
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/ mailman/listinfo/oi-dev
> 
>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
>
>


-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[G B via oi-dev]

I added documentation to the VirtualBox page on the wiki:
https://wiki.openindiana.org/oi/7.2+VirtualBox
 

On Sunday, May 28, 2017 4:34 PM, G B via oi-dev  
wrote:
 

 Thank you
 

On Sunday, May 28, 2017 4:11 PM, Aurélien Larcher 
 wrote:
 

 

On Sun, May 28, 2017 at 10:57 PM, G B via oi-dev  wrote:

Today I downloaded the latest Hipster release and subsequently attempted to 
install Virtualbox 5.1.22, 5.0.40, and 4.3.40.  All of them failed.  

For 5.1.22:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++- runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c- runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

For 5.0.40:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++- runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c- runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

For 4.3.40:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++- runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c- runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

Virtualbox used to install on the old OpenSolaris.  It is kind of ironic that 
Sun created Virtualbox and Oracle still releases a package for Solaris, but 
none of them will install.  Why and how do I get Virtualbox installed, or is it 
not worth the effort?  If I can't run Virtualbox then Hipster is useless to me.


This has been discussed several times before on the MLs.
The error is that the pre-install script checks that 'gcc-45-runtime' is 
installed but this package does not exist on Hipster, only on Solaris.

You can look at Jim's scripts to work around the issue:

https://github.com/jimklimov/vboxconfig_sh

Now if there was a page on the Wiki about Virtualbox, maybe we would not need 
to answer the same question every month :)

 


__ _
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/ mailman/listinfo/oi-dev




-- 
---
Praise the Caffeine embeddings


   ___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

   ___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[G B via oi-dev]

Thank you
 

On Sunday, May 28, 2017 4:11 PM, Aurélien Larcher 
 wrote:
 

 

On Sun, May 28, 2017 at 10:57 PM, G B via oi-dev  wrote:

Today I downloaded the latest Hipster release and subsequently attempted to 
install Virtualbox 5.1.22, 5.0.40, and 4.3.40.  All of them failed.  

For 5.1.22:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++- runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c- runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

For 5.0.40:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++- runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c- runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

For 4.3.40:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36. 115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++- runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c- runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

Virtualbox used to install on the old OpenSolaris.  It is kind of ironic that 
Sun created Virtualbox and Oracle still releases a package for Solaris, but 
none of them will install.  Why and how do I get Virtualbox installed, or is it 
not worth the effort?  If I can't run Virtualbox then Hipster is useless to me.


This has been discussed several times before on the MLs.
The error is that the pre-install script checks that 'gcc-45-runtime' is 
installed but this package does not exist on Hipster, only on Solaris.

You can look at Jim's scripts to work around the issue:

https://github.com/jimklimov/vboxconfig_sh

Now if there was a page on the Wiki about Virtualbox, maybe we would not need 
to answer the same question every month :)

 


__ _
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/ mailman/listinfo/oi-dev




-- 
---
Praise the Caffeine embeddings


   ___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Virtualbox

[Aurélien Larcher]

On Sun, May 28, 2017 at 10:57 PM, G B via oi-dev 
wrote:

> Today I downloaded the latest Hipster release and subsequently attempted
> to install Virtualbox 5.1.22, 5.0.40, and 4.3.40.  All of them failed.
>
> For 5.1.22:
> Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36.115126
> Oracle Corporation
> ## Executing checkinstall script.
> Checking package dependencies...
> ## Missing packages:
> ## IPS :  system/library/gcc/gcc-c++-runtime or
> system/library/gcc-45-runtime system/library/gcc/gcc-c-runtime or
> system/library/gcc-45-runtime
> ## SVr4:  SUNWPython SUNWPython-devel
> ##
> ## Please install either the IPS or SVr4 packages before installing
> VirtualBox.
> pkgadd: ERROR: checkinstall script did not complete successfully
>
> Installation of  failed.
> No changes were made to the system.
>
> For 5.0.40:
> Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36.115126
> Oracle Corporation
> ## Executing checkinstall script.
> Checking package dependencies...
> ## Missing packages:
> ## IPS :  system/library/gcc/gcc-c++-runtime or
> system/library/gcc-45-runtime system/library/gcc/gcc-c-runtime or
> system/library/gcc-45-runtime
> ## SVr4:  SUNWPython SUNWPython-devel
> ##
> ## Please install either the IPS or SVr4 packages before installing
> VirtualBox.
> pkgadd: ERROR: checkinstall script did not complete successfully
>
> Installation of  failed.
> No changes were made to the system.
>
> For 4.3.40:
> Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36.115126
> Oracle Corporation
> ## Executing checkinstall script.
> Checking package dependencies...
> ## Missing packages:
> ## IPS :  system/library/gcc/gcc-c++-runtime or
> system/library/gcc-45-runtime system/library/gcc/gcc-c-runtime or
> system/library/gcc-45-runtime
> ## SVr4:  SUNWPython SUNWPython-devel
> ##
> ## Please install either the IPS or SVr4 packages before installing
> VirtualBox.
> pkgadd: ERROR: checkinstall script did not complete successfully
>
> Installation of  failed.
> No changes were made to the system.
>
> Virtualbox used to install on the old OpenSolaris.  It is kind of ironic
> that Sun created Virtualbox and Oracle still releases a package for
> Solaris, but none of them will install.  Why and how do I get Virtualbox
> installed, or is it not worth the effort?  If I can't run Virtualbox then
> Hipster is useless to me.
>

This has been discussed several times before on the MLs.
The error is that the pre-install script checks that 'gcc-45-runtime' is
installed but this package does not exist on Hipster, only on Solaris.

You can look at Jim's scripts to work around the issue:

https://github.com/jimklimov/vboxconfig_sh

Now if there was a page on the Wiki about Virtualbox, maybe we would not
need to answer the same question every month :)



>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] Virtualbox

[G B via oi-dev]

Today I downloaded the latest Hipster release and subsequently attempted to 
install Virtualbox 5.1.22, 5.0.40, and 4.3.40.  All of them failed.  

For 5.1.22:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36.115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++-runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c-runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

For 5.0.40:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36.115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++-runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c-runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

For 4.3.40:Oracle VM VirtualBox(i386) 5.1.22,REV=2017.04.28.17.36.115126
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
## Missing packages: 
## IPS :  system/library/gcc/gcc-c++-runtime or system/library/gcc-45-runtime 
system/library/gcc/gcc-c-runtime or system/library/gcc-45-runtime
## SVr4:  SUNWPython SUNWPython-devel
## 
## Please install either the IPS or SVr4 packages before installing VirtualBox.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of  failed.
No changes were made to the system.

Virtualbox used to install on the old OpenSolaris.  It is kind of ironic that 
Sun created Virtualbox and Oracle still releases a package for Solaris, but 
none of them will install.  Why and how do I get Virtualbox installed, or is it 
not worth the effort?  If I can't run Virtualbox then Hipster is useless to me.

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] VirtualBox-5.1.6 on self-built Qt5.5 bins uploaded (built on Hipster 2015 illumos-f83b46b)

[Мартин Бохниг via oi-dev]

Hello Aurelien and Hipster community,


as promised I'm absolutely open to using Qt5 rather than Qt4.8, as long as this 
Qt5.x in question A) builds here on old Hipster 2015 and B) works together with 
VirtualBox5.x.

The Qt5.5 build process functions much better than 5.8alpha on my 2015 based 
setup with gcc4.9 and the most important thing: Without -std-gnu++11 (otherwise 
vbox won't build).
A hack in the middle would be possible (to build Qt5.6++ with -std-gnu++11 
(Qt5.6++ *requires* -std-gnu++11)  and run Vbox5.x's ./configure with the same 
CFLAGS/CXXFLAGS (otherwise Qt5 detection tests FAIL), then killing make/kmk and 
actually building Vbox5.x without -std-gnu++11.
If that sounds like dirty crap, I agree with you. Also there are 100 more 
problems with 5.8alpha on my build machine.

Hence - if we really want Qt5.x for Vbox5.x, then me should stick to Qt5.5.
The build works as said much better, but still quits at various places.
However - enough was built in my tests with some hacks and -k to get Vbox 
linked against Qt5.5.


BENEFITS of Qt5.5 over Qt4.8:

{A}
Now the only stderr messages when starting /opt/VirtualBox/VirtualBox are:

$ vbox
Qt WARNING: QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
Qt WARNING: QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
Qt WARNING: QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"


compare this to the old ones with Qt4.8:

$ /opt/VirtualBox/VirtualBox
Qt WARNING: Object::connect: No such signal QApplication::screenAdded(QScreen *)
Qt WARNING: Object::connect:  (sender name:   'VirtualBox')
Qt WARNING: Object::connect: No such signal QApplication::screenRemoved(QScreen 
*)
Qt WARNING: Object::connect:  (sender name:   'VirtualBox')
Qt WARNING: Object::disconnect: No such signal 
QApplication::screenAdded(QScreen *)
Qt WARNING: Object::disconnect:  (sender name:   'VirtualBox')
Qt WARNING: Object::disconnect: No such signal 
QApplication::screenRemoved(QScreen *)
Qt WARNING: Object::disconnect:  (sender name:   'VirtualBox')


{B}
Now you can run /opt/VirtualBox/VirtualBox as root or as su to root without 
Christian Meier's X11 tunnelling trick.

You need to run Vbox as root for USB device detection and also for Non-USB 
optical media passthrough (with some MS-Win software needed to pass the 
security checks required for installation, while reading out hidden data from 
physical (!!!) optical media.
See 
https://openindiana.org/pipermail/openindiana-discuss/2016-September/019561.html
suid doesn't work, nor would it help to make the corresponding devices 
user-writable.
It is a known Vbox mystery and that's not my thing to get this solved. If you 
run it as root, then it works. And the good news is, that now you can run also 
Vbox5.x as root again without the X11 forwarding/tunneling trick.
BTW: Oracle's official Vbox5.0.x and 5.1.x packages had the same off issue as 
root (complete hang of the Vbox GUI, no text readable).
Now a thing of the past :)



{C}
It looks brighter and smoother now with Qt5.5

{D}
Aurelien and all Qt5.x enthusiasts are (hopefully) happy now.



Here are the new bins (not sure if this self-compiled Qt5.5 works as well for 
you as the previous test-package did) :


@@@Screenshots:

http://opensxce.org/virtualbox5_qt5.5/testbins_perhaps_instable/Screenshots/Screenshot-163.png
http://opensxce.org/virtualbox5_qt5.5/testbins_perhaps_instable/Screenshots/Screenshot-164.png
http://opensxce.org/virtualbox5_qt5.5/testbins_perhaps_instable/Screenshots/Screenshot-165.png
   (with USB devices when running as root)


@@@Updated Install instructions:

http://opensxce.org/virtualbox5_qt5.5/testbins_perhaps_instable/INSTALL.txt

The new part is mostly: 

-0.5) Install instable Qt5.5 64bit /usr/lib/qt/5.5

$ su

# cd /usr/lib/qt/.

# wget wget 
http://opensxce.org/virtualbox5_qt5.5/testbins_perhaps_instable/usr_lib_qt_5.5__64BITbins.tar.bz2

# bzcat ./usr_lib_qt_5.5__64BITbins.tar.bz2|tar xvf -

# rm usr_lib_qt_5.5__64BITbins.tar.bz2




@@@Qt5.5 64bit:

(to be extracted in /usr/lib/qt/.)
http://opensxce.org/virtualbox5_qt5.5/testbins_perhaps_instable/usr_lib_qt_5.5__64BITbins.tar.bz2


@@@ New SVR4 Vbox package:

http://opensxce.org/virtualbox5_qt5.5/testbins_perhaps_instable/VirtualBox-5.1.6-SunOS-amd64-r110634.pkg


This Qt5.5 build is still instable and perhaps won't work everywhere (mind the 
dependencies, and watch out if you are missing any bits)
I share it with you in the hope that some may find it useful (as a preliminary 
preview).

Because getting Qt5.5 more stable will consume another 1 or 2 days on this slow 
Celeron G530.



That's it for today,
happy testing and regards,

%martin










-- 
Мартин Бохниг___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev