[OpenIndiana-discuss] VirtualBox status?

Fri Aug 25 11:17:22 UTC 2023

On 8/25/23 12:58, Predrag Zečević via openindiana-discuss wrote:
>
> On 8/25/23 12:35, Carsten Grzemba via openindiana-discuss wrote:
>> Unfortunately starting the GUI VirtualBox still leads to crash 
>> VBoxSVC (SIGABRT) and no installed VM's listed in the GUI.
>>
>>> $C
>> 00007fffadf5e270 libc.so.1`_lwp_kill+0xa()
>> 00007fffadf5e2a0 libc.so.1`raise+0x22(6)
>> 00007fffadf5e2f0 libc.so.1`abort+0x58()
>> 00007fffadf5e330 
>> libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()
>> 00007fffadf5e350 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9()
>> 00007fffadf5e370 0x7fffa67f6099()
>> 00007fffadf5e460 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc()
>> 00007fffadf5e630 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
>> 00007fffadf5e9e0 libgcc_s.so.1`_Unwind_RaiseException+0x331()
>> 00007fffadf5ea10 libstdc++.so.6.0.28`__cxa_throw+0x40()
>> 00007fffadf5eb90 Medium::i_queryInfo+0x6a6()
>> 00007fffadf5ebd0 Medium::refreshState+0x8d()
>> 00007fffadf5ec20 MediumWrap::RefreshState+0xd1()
>> 00007fffadf5ecd0 VBoxXPCOM.so`XPTC_InvokeByIndex+0x13f()
>> 00007fffadf5eea0 VBoxXPCOMIPCC.so`ipcDConnectService::OnInvoke+0x3bc()
>> 00007fffadf5eeb0 
>> VBoxXPCOMIPCC.so`ipcDConnectService::OnIncomingRequest+0x28()
>> 00007fffadf5ef00 VBoxXPCOMIPCC.so`DConnectWorker::Run+0x137()
>> 00007fffadf5ef20 VBoxXPCOM.so`nsThread::Main+0x23()
>> 00007fffadf5ef40 VBoxXPCOM.so`_pt_root+0x86()
>> 00007fffadf5ef50 VBoxXPCOM.so`_pt_iprt_root+0xc()
>> 00007fffadf5ef70 VBoxRT.so`rtThreadMain+0x34()
>> 00007fffadf5efb0 VBoxRT.so`rtThreadNativeMain+0x43()
>> 00007fffadf5efe0 libc.so.1`_thrp_setup+0x77(7fffaeaa4a40)
>> 00007fffadf5eff0 libc.so.1`_lwp_start()
>>
>>
>> also VirtualBox crashes some time with SIGSEGV
>>
>>
>>> $C
>> 00007fffbfffe810 libQt5Widgets.so.5.15.4`QToolBar::toolButtonStyle()
>> 00007fffbfffe850 UIVirtualBoxManagerWidget::cleanup+0x12()
>> 00007fffbfffe870 
>> UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
>> 00007fffbfffe890 
>> UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()
>> 00007fffbfffe900 libQt5Core.so.5.15.4`QObject::event+0x40()
>> 00007fffbfffe930 
>> libQt5Widgets.so.5.15.4`QApplicationPrivate::notify_helper+0x82()
>> 00007fffbfffe9a0 
>> libQt5Core.so.5.15.4`QCoreApplication::notifyInternal2+0x111()
>> 00007fffbfffea40 
>> libQt5Core.so.5.15.4`QCoreApplicationPrivate::sendPostedEvents+0x170()
>> 00007fffbfffea60 libQt5Core.so.5.15.4`postEventSourceDispatch+0x1b()
>> 00007fffbfffeae0 libglib-2.0.so.0.7400.7`g_main_context_dispatch+0x23d()
>> 00007fffbfffeb40 
>> libglib-2.0.so.0.7400.7`g_main_context_iterate.constprop.0+0x1c8()
>> 00007fffbfffeb60 libglib-2.0.so.0.7400.7`g_main_context_iteration+0x30()
>> 00007fffbfffebb0 
>> libQt5Core.so.5.15.4`QEventDispatcherGlib::processEvents+0x64()
>> 00007fffbfffec30 libQt5Core.so.5.15.4`QEventLoop::exec+0x11b()
>> 00007fffbfffec80 UICommon.so`QIDialog::execute+0xd5()
>> 00007fffbfffed20 UICommon.so`UIMessageCenter::showMessageBox+0x33e()
>> 00007fffbfffedb0 UICommon.so`UIMessageCenter::message+0xff()
>> 00007fffbfffee20 UICommon.so`UIMessageCenter::error+0x3e()
>> 00007fffbfffeee0 UICommon.so`UIMessageCenter::cannotSetExtraData+0xe3()
>> 00007fffbffff130 
>> UICommon.so`UIExtraDataManager::setExtraDataString+0x546()
>> 00007fffbffff170 
>> UICommon.so`UIExtraDataManager::setSelectorWindowToolBarVisible+0x6a()
>> 00007fffbffff1b0 UIVirtualBoxManagerWidget::saveSettings+0x2f()
>> 00007fffbffff1f0 UIVirtualBoxManagerWidget::cleanup+0x12()
>> 00007fffbffff210 
>> UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
>> 00007fffbffff230 
>> UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()
>> 00007fffbffff250 UIVirtualBoxManager::cleanupWidgets+0x22()
>> 00007fffbffff270 UIVirtualBoxManager::cleanup+0x3a()
>> 00007fffbffff280 UIVirtualBoxManager::destroy+0x4b()
>> 00007fffbffff350 libQt5Core.so.5.15.4`void doActivate<false>+0x4d4()
>> 00007fffbffff380 
>> libQt5Core.so.5.15.4`QCoreApplication::aboutToQuit+0x2a()
>> 00007fffbffff3a0 
>> libQt5Core.so.5.15.4`QCoreApplicationPrivate::execCleanup+0x49()
>> 00007fffbffff3f0 libQt5Core.so.5.15.4`QCoreApplication::exec+0x9c()
>> 00007fffbffff4d0 TrustedMain+0x27c()
>> 00007fffbffff560 main+0x5f()
>> 00007fffbffff590 _start_crt+0x87()
>> 00007fffbffff5a0 _start+0x18()
>>
>>
>> Am 25.08.23 09:23 schrieb Stephan Althaus 
>> <Stephan.Althaus at Duedinghausen.eu>:
>>>
>>> On 8/25/23 08:46, Predrag Zečević via openindiana-discuss wrote:
>>>>
>>>>
>>>> On 8/25/23 07:25, Carl Brewer wrote:
>>>>> Hey everyone,
>>>>> Before I break a server .. Is VirtualBox running ok on current OI?
>>>>> Last I saw, Russell was having trouble with it in July.
>>>>>
>>>>> Thank you!
>>>>>
>>>>> Carl
>>>>>
>>>>
>>>> Hi Carl,
>>>>
>>>> I had to boot in BE created in June, since one from August is not 
>>>> working
>>>>
>>>> I guess we need to wait for fix...
>>>>
>>>> Check mailing list for "Problem with VirtualBox since upgrade today",
>>>> as some workaround is proposed there (I have decided to switch
>>>> complete BE back)
>>>>
>>>> Regards.
>>>>
>>>>> _______________________________________________
>>>>> openindiana-discuss mailing list
>>>>> openindiana-discuss at openindiana.org
>>>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>>
>>> Hello!
>>>
>>>
>>> I did a pkg update now on my server with one headless VB-vm:
>>>
>>>
>>> $ beadm list
>>> BE Active Mountpoint Space Policy Created
>>> openindiana-2022:11:16 - - 124.32M static 2022-11-16 18:00
>>> openindiana-2023:06:23-2 - - 81.33M static 2023-06-23 13:44
>>> openindiana-2023:08:25 NR / 105.67G static 2023-08-25 08:57
>>>
>>> $ VBoxManage startvm aLinux -type headless
>>> Waiting for VM "aLinux" to power on...
>>> VM "aLinux" has been successfully started.
>>>
>>> $ VBoxManage list vms
>>> "aLinux" {9019c57b-7dd4-4ef9-bc96-c20185674ed2}
>>>
>>> $ VBoxManage list runningvms
>>> "aLinux" {9019c57b-7dd4-4ef9-bc96-c20185674ed2}
>>>
>>> $ ssh applepie at projekte
>>> applepie at projekte's password:
>>> Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-156-generic x86_64)
>>>
>>>   * Documentation: https://help.ubuntu.com
>>>   * Management: https://landscape.canonical.com
>>>   * Support: https://ubuntu.com/advantage
>>>
>>>   System information disabled due to load higher than 2.0
>>>
>>>   * Strictly confined Kubernetes makes edge and IoT secure. Learn how
>>> MicroK8s
>>>   just raised the bar for easy, resilient and secure K8s cluster
>>> deployment.
>>>
>>>   https://ubuntu.com/engage/secure-kubernetes-at-the-edge
>>>
>>> Expanded Security Maintenance for Applications is not enabled.
>>>
>>> 22 updates can be applied immediately.
>>> To see these additional updates run: apt list --upgradable
>>>
>>> Enable ESM Apps to receive additional future security updates.
>>> See https://ubuntu.com/esm or run: sudo pro status
>>>
>>>
>>> Last login: Tue Jul 11 15:17:16 2023 from 192.168.2.63
>>>
>>>
>>> q... So my VM is running on today's OI.
>>>
>>>
>>> Regards,
>>> Stephan
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> openindiana-discuss mailing list
>>> openindiana-discuss at openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>
> I did updated Hipster 2 hours ago, and can lunch headless guest 
> (tested CentOS 8) and access its console via RDP (as I have set it in 
> configuration).
>
> Did *not* tested guest which start GUI yet...
>
> :; pkg list virtualbox
> NAME (PUBLISHER)                                  VERSION     IFO
> system/virtualbox 6.1.40-2023.0.0.1     i--
>
> :; uname -rosv
> SunOS 5.11 illumos-3a0fa64c0f illumos
>
> Regards.

Hello!

YES, the GUI still doesn't work, HEADLESS does.

Some (x11-)libs are not gcc-10 yet..

(i had at least one lib where 'gmake test' did have no positive tests :-/)

For those who need the gui, use 
pkg://openindiana.org/system/virtualbox@6.1.40-2022.0.0.0:20221108T082551Z

pfexec pkg install 
pkg://openindiana.org/system/virtualbox@6.1.40-2022.0.0.0:20221108T082551Z
pfexec pkg freeze virtualbox

Regards,
Stephan