Re: [OpenIndiana-discuss] VirtualBox status? -- please test 6.1.46

[Philip Kime]

I can confirm that the vbox webservice is now fixed with the Sept 2023 updates.

PK

--
Dr Phil. Philip Kime
BA (Hons) Msc (Dist) PhD

> On 20 Sep 2023, at 09:01, Stephan Althaus  
> wrote:
> 
> On 9/8/23 09:28, Carsten Grzemba via openindiana-discuss wrote:
>> I have uploaded a package 6.1.46 on http://pkg.toc.de/userland
>> 
>> which have passed my smoke tests.
>> 
>> Please test and report results.
>> 
> Hello Carsten!
> 
> Thanks for your efforts, virtualbox GUI is working.
> 
> I also had problems using the newest nvidia driver with virtualbox GUI
> and did stay with 515 until now,
> 535 is working with virtualbox today.
> 
> So everything is fine now.
> 
> 
> Thanks!!!
> 
> 
> Regards,
> 
> Stephan
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss



signature.asc
Description: OpenPGP digital signature
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] VirtualBox status? -- please test 6.1.46

[Carl Brewer]

On 20/09/2023 5:01 pm, Stephan Althaus wrote:

On 9/8/23 09:28, Carsten Grzemba via openindiana-discuss wrote:

I have uploaded a package 6.1.46 on http://pkg.toc.de/userland

which have passed my smoke tests.

Please test and report results.


Hello Carsten!

Thanks for your efforts, virtualbox GUI is working.

I also had problems using the newest nvidia driver with virtualbox GUI 
and did stay with 515 until now,

535 is working with virtualbox today.

So everything is fine now.


Great, I'll bump one of my servers and see how it goes!

Thank you

Carl



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

Re: [OpenIndiana-discuss] VirtualBox status? -- please test 6.1.46

[Stephan Althaus]

On 9/8/23 09:28, Carsten Grzemba via openindiana-discuss wrote:

I have uploaded a package 6.1.46 on http://pkg.toc.de/userland

which have passed my smoke tests.

Please test and report results.


Hello Carsten!

Thanks for your efforts, virtualbox GUI is working.

I also had problems using the newest nvidia driver with virtualbox GUI 
and did stay with 515 until now,

535 is working with virtualbox today.

So everything is fine now.


Thanks!!!


Regards,

Stephan



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

Re: [OpenIndiana-discuss] VirtualBox status? -- please test 6.1.46

[Carsten Grzemba via openindiana-discuss]

I have uploaded a package 6.1.46 on http://pkg.toc.de/userland

which have passed my smoke tests.

Please test and report results.

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

Re: [OpenIndiana-discuss] VirtualBox status?

[Stephan Althaus]

On 9/6/23 23:25, Carl Brewer wrote:


Is this now a "Wait for us to fix it" issue? I don't have the skill or 
resources (AFAIK) to be involved in recompiling/porting to gcc-10.



Hello!

I am not an expert either. May knowledge is sort of "if it builds with 
gcc-10 and gmake test is ok then i am happy - FAIL otherwise".


At the moment i don't find time to work through the gcc7-package-list 
(since 06.08.2023 now) and the new room for my little daughter (3) isn't 
ready yet..


We are only a few people that are using illumos-based distributions, and 
we all have to work together, everyone with the time and skill that is 
there.


Whilst being here i learn about how much work it is to keep a 
distribution on time, and sometimes how complicated it is to 'only' 
compile a packages with a different compiler :-/


I am interested in assisting and will do so when i find time again.


Regards,

Stephan



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

Re: [OpenIndiana-discuss] VirtualBox status?

[Stephan Althaus]

On 9/7/23 08:49, Aurélien Larcher wrote:

On Wed, Sep 6, 2023 at 11:25 PM Carl Brewer  wrote:


On 25/08/2023 9:17 pm, Stephan Althaus wrote:


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

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

Could make a list of the libs you found?




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

:-/)

Is this now a "Wait for us to fix it" issue? I don't have the skill or
resources (AFAIK) to be involved in recompiling/porting to gcc-10.



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

Would "freeze" break later updates?  VB is up to 7.0.10 now, so this
one's lagging a bit.

Thank you

Carl


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




Hello!

A first simple list of packages that are build with gcc-7
would contain the ones that are packaged before Dec-2022:

pkg list |grep 2020

Be aware these are only the installed ones.

On my Laptop this command finds 132 entries.


I had some scripts to build a list, with finding the compiler of a lib, 
then search the package for that lib,

but i don't find that scripts anymore, so below is my list as of 2023-08-6,
locally installed packages here, too..

I will search for the scripts that you can run it on your own..

P.S.

Maybe the timestamp of the Makefile in the source tree would be a hint, 
too - didn't thought of that before..


Regards,

Stephan

_

pkg:/audio/faad2@2.7-2022.0.0.3
pkg:/audio/twolame@0.3.13-2020.0.1.2
pkg:/audio/wavpack@5.6.0-2022.0.0.0
pkg:/codec/libtheora@1.1.1-2022.0.0.3
pkg:/database/berkeleydb-5@5.3.28-2022.0.0.1
pkg:/database/geoip@1.6.12-2022.0.0.1
pkg:/desktop/character-map/gucharmap@3.18.2-2022.0.0.2
pkg:/desktop/compiz@0.8.18-2020.0.1.1
pkg:/desktop/compiz/plugin/compiz-fusion-extra@0.8.18-2020.0.1.0
pkg:/desktop/mate/caja/caja-extensions@1.26.1-2022.0.0.0
pkg:/desktop/mate/control-center@1.26.0-2022.0.0.1
pkg:/desktop/window-manager/enlightenment@0.21.9-2020.0.1.0
pkg:/desktop/window-manager/notion-3@2015061300-2020.0.1.0
pkg:/developer/build/autogen@5.18.16-2022.0.0.3
pkg:/developer/check@0.15.2-2020.0.1.0
pkg:/developer/clang-13@13.0.1-2022.0.0.0
pkg:/developer/debug/mdb@0.5.11-2023.0.0.21760
pkg:/developer/ui-designer/glade@3.22.2-2022.0.0.0
pkg:/developer/versioning/mercurial-37@5.9.3-2022.0.0.1
pkg:/developer/versioning/mercurial-39@5.9.3-2022.0.0.1
pkg:/diagnostic/scanpci@0.14-2020.0.1.1
pkg:/driver/graphics/drm@0.5.11-2022.0.0.73
pkg:/gnome/accessibility/at-spi2-atk@2.24.1-2022.0.0.0
pkg:/gnome/accessibility/at-spi2-core@2.24.1-2022.0.0.2
pkg:/gnome/config/dconf@0.24.0-2022.0.0.2
pkg:/gnome/help-viewer/yelp@3.20.1-2022.0.0.1
pkg:/gnome/theme/gtk2-engines-murrine@0.98.2-2022.0.0.0
pkg:/gnome/theme/gtk2-engines@2.20.2-2022.0.0.1
pkg:/gnome/theme/nimbus@1.0-2020.0.1.4
pkg:/image/library/sdl-image@1.2.12-2020.0.1.0
pkg:/library/audio/libcdio@2.1.0-2022.0.0.0
pkg:/library/audio/libdca@0.0.7-2022.0.0.1
pkg:/library/audio/libgsm@1.0.22-2022.0.0.0
pkg:/library/audio/libmpcdec@1.2.6-2022.0.0.1
pkg:/library/c++/libetonyek@0.1.10-2022.0.0.0
pkg:/library/c++/libodfgen@0.1.8-2020.0.1.0
pkg:/library/c++/libpagemaker@0.0.4-2022.0.0.2
pkg:/library/c++/libstaroffice@0.0.7-2022.0.0.1
pkg:/library/desktop/geocode-glib@3.24.0-2022.0.0.2
pkg:/library/desktop/gtk3/gtk3-nocsd@3-2020.0.1.3
pkg:/library/desktop/gtkspell@2.0.16-2022.0.0.2
pkg:/library/desktop/gtkspell3@3.0.10-2022.0.0.0
pkg:/library/desktop/json-glib@1.6.6-2022.0.0.2
pkg:/library/desktop/libbonoboui@2.24.5-2022.0.0.2
pkg:/library/desktop/libgdata@0.18.1-2022.0.0.0
pkg:/library/desktop/libgksu@2.0.12-2022.0.0.6
pkg:/library/desktop/libglade@2.6.4-2022.0.0.3
pkg:/library/desktop/libgnome@2.32.1-2022.0.0.3
pkg:/library/desktop/libgnomecanvas@2.30.3-2022.0.0.2
pkg:/library/desktop/libgnomeui@2.24.5-2022.0.0.4
pkg:/library/desktop/libpeas@1.20.0-2022.0.0.4
pkg:/library/desktop/libpeas/libpeas-python3loader@1.20.0-2022.0.0.4
pkg:/library/desktop/libsexy@0.1.11-2020.0.1.3
pkg:/library/desktop/libvisual@0.4.0-2020.0.1.0
pkg:/library/desktop/libvisual/plugins@0.4.0-2020.0.1.2
pkg:/library/desktop/libwnck3@3.32.0-2022.0.0.0
pkg:/library/desktop/libxklavier@5.4-2020.0.1.1
pkg:/library/desktop/mate/libmatemixer@1.26.0-2022.0.0.1
pkg:/library/desktop/pangox-compat@0.0.2-2022.0.0.2
pkg:/library/desktop/ptlib@2.10.11-2020.0.1.4
pkg:/library/desktop/startup-notification@0.12-2020.0.1.0
pkg:/library/desktop/vte@0.28.2-2022.0.0.6
pkg:/library/desktop/xdg/libcanberra@0.26-2022.0.0.4
pkg:/library/freetds@1.0.94-2020.0.1.0
pkg:/library/glib-networking@2.42.0-2022.0.0.4
pkg:/library/gnome/gnome-keyring@2.32.0-2022.0.0.1

Re: [OpenIndiana-discuss] VirtualBox status?

[Carsten Grzemba via openindiana-discuss]

Am 07.09.23 08:49 schrieb Aurélien Larcher  : 
> 
> On Wed, Sep 6, 2023 at 11:25 PM Carl Brewer  wrote:
> 
> > On 25/08/2023 9:17 pm, Stephan Althaus wrote:
> >
> > >
> > > YES, the GUI still doesn't work, HEADLESS does.
> > >
> > > Some (x11-)libs are not gcc-10 yet..
> >
> 
> Could make a list of the libs you found?
> 
> 
> 
> > >
> > > (i had at least one lib where 'gmake test' did have no positive tests
> > :-/)
> >
> > Is this now a "Wait for us to fix it" issue? I don't have the skill or
> > resources (AFAIK) to be involved in recompiling/porting to gcc-10.
> >
> >
> > >
> > > 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
> >
> > Would "freeze" break later updates? VB is up to 7.0.10 now, so this
> > one's lagging a bit.
> >
> > Thank you
> >
> > Carl
> >
> 

I did some effort in the last days and the current status is

GCC10 builds always crash in C++ exception handling on 'throw S_OK' 

(Cheers to the C++ programmers, it - then - else is boring ;))
   

Well aware of the problem with the libstdc++ and libgcc_s mixup I tried to 
build with GCC12.
   
Builds with GCC12 I have the two issues:
- on one testenv I get the problem described in: 
https://www.virtualbox.org/ticket/18134
- the hosts system crashes in vboxdrv on startup a guest

> $C
fe00191c6a70 0xf43b8cb2()
fe00191c6b20 0xf43906e3()
fe00191c6b50 0xf4390804()
fe00191c6c00 supdrvIOCtl+0x15f2()
fe00191c6cc0 VBoxDrvSolarisIOCtl+0x187(260002, c0185687, 7fffaaa7ed10, 
202003, fe11bf29da68, fe00191c6e18)
fe00191c6d00 cdev_ioctl+0x3f(260002, c0185687, 7fffaaa7ed10, 202003, 
fe11bf29da68, fe00191c6e18)
fe00191c6d50 spec_ioctl+0x55(fe119e9db700, c0185687, 7fffaaa7ed10, 
202003, fe11bf29da68, fe00191c6e18, 0)
fe00191c6de0 fop_ioctl+0x40(fe119e9db700, c0185687, 7fffaaa7ed10, 
202003, fe11bf29da68, fe00191c6e18, 0)
fe00191c6f00 ioctl+0x144(b, c0185687, 7fffaaa7ed10)
fe00191c6f10 sys_syscall+0x17d()

This is similar described here:
https://illumos.topicbox.com/groups/omnios-discuss/T2c1cc2017f4a8d96-M634438a6a4d1b61d3ace014f/virtualbox-is-core-dumping

Set disable_smap=1 makes no difference.

Any hints?

If someone like to test the Virtualbox package 6.1.46 and the GCC12 runtilme is 
available here:
http://pkg.toc.de/userland


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

Re: [OpenIndiana-discuss] VirtualBox status?

[Aurélien Larcher]

On Wed, Sep 6, 2023 at 11:25 PM Carl Brewer  wrote:

> On 25/08/2023 9:17 pm, Stephan Althaus wrote:
>
> >
> > YES, the GUI still doesn't work, HEADLESS does.
> >
> > Some (x11-)libs are not gcc-10 yet..
>

Could make a list of the libs you found?



> >
> > (i had at least one lib where 'gmake test' did have no positive tests
> :-/)
>
> Is this now a "Wait for us to fix it" issue? I don't have the skill or
> resources (AFAIK) to be involved in recompiling/porting to gcc-10.
>
>
> >
> > 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
>
> Would "freeze" break later updates?  VB is up to 7.0.10 now, so this
> one's lagging a bit.
>
> Thank you
>
> Carl
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>


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

Re: [OpenIndiana-discuss] VirtualBox status?

[Carl Brewer]

On 25/08/2023 9:17 pm, Stephan Althaus wrote:



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 :-/)


Is this now a "Wait for us to fix it" issue? I don't have the skill or 
resources (AFAIK) to be involved in recompiling/porting to gcc-10.





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


Would "freeze" break later updates?  VB is up to 7.0.10 now, so this 
one's lagging a bit.


Thank you

Carl


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

Re: [OpenIndiana-discuss] VirtualBox status?

[Stephan Althaus]

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

7fffadf5e270 libc.so.1`_lwp_kill+0xa()
7fffadf5e2a0 libc.so.1`raise+0x22(6)
7fffadf5e2f0 libc.so.1`abort+0x58()
7fffadf5e330 
libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()

7fffadf5e350 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9()
7fffadf5e370 0x7fffa67f6099()
7fffadf5e460 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc()
7fffadf5e630 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
7fffadf5e9e0 libgcc_s.so.1`_Unwind_RaiseException+0x331()
7fffadf5ea10 libstdc++.so.6.0.28`__cxa_throw+0x40()
7fffadf5eb90 Medium::i_queryInfo+0x6a6()
7fffadf5ebd0 Medium::refreshState+0x8d()
7fffadf5ec20 MediumWrap::RefreshState+0xd1()
7fffadf5ecd0 VBoxXPCOM.so`XPTC_InvokeByIndex+0x13f()
7fffadf5eea0 VBoxXPCOMIPCC.so`ipcDConnectService::OnInvoke+0x3bc()
7fffadf5eeb0 
VBoxXPCOMIPCC.so`ipcDConnectService::OnIncomingRequest+0x28()

7fffadf5ef00 VBoxXPCOMIPCC.so`DConnectWorker::Run+0x137()
7fffadf5ef20 VBoxXPCOM.so`nsThread::Main+0x23()
7fffadf5ef40 VBoxXPCOM.so`_pt_root+0x86()
7fffadf5ef50 VBoxXPCOM.so`_pt_iprt_root+0xc()
7fffadf5ef70 VBoxRT.so`rtThreadMain+0x34()
7fffadf5efb0 VBoxRT.so`rtThreadNativeMain+0x43()
7fffadf5efe0 libc.so.1`_thrp_setup+0x77(7fffaeaa4a40)
7fffadf5eff0 libc.so.1`_lwp_start()


also VirtualBox crashes some time with SIGSEGV



$C

7fffbfffe810 libQt5Widgets.so.5.15.4`QToolBar::toolButtonStyle()
7fffbfffe850 UIVirtualBoxManagerWidget::cleanup+0x12()
7fffbfffe870 
UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
7fffbfffe890 
UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()

7fffbfffe900 libQt5Core.so.5.15.4`QObject::event+0x40()
7fffbfffe930 
libQt5Widgets.so.5.15.4`QApplicationPrivate::notify_helper+0x82()
7fffbfffe9a0 
libQt5Core.so.5.15.4`QCoreApplication::notifyInternal2+0x111()
7fffbfffea40 
libQt5Core.so.5.15.4`QCoreApplicationPrivate::sendPostedEvents+0x170()

7fffbfffea60 libQt5Core.so.5.15.4`postEventSourceDispatch+0x1b()
7fffbfffeae0 libglib-2.0.so.0.7400.7`g_main_context_dispatch+0x23d()
7fffbfffeb40 
libglib-2.0.so.0.7400.7`g_main_context_iterate.constprop.0+0x1c8()

7fffbfffeb60 libglib-2.0.so.0.7400.7`g_main_context_iteration+0x30()
7fffbfffebb0 
libQt5Core.so.5.15.4`QEventDispatcherGlib::processEvents+0x64()

7fffbfffec30 libQt5Core.so.5.15.4`QEventLoop::exec+0x11b()
7fffbfffec80 UICommon.so`QIDialog::execute+0xd5()
7fffbfffed20 UICommon.so`UIMessageCenter::showMessageBox+0x33e()
7fffbfffedb0 UICommon.so`UIMessageCenter::message+0xff()
7fffbfffee20 UICommon.so`UIMessageCenter::error+0x3e()
7fffbfffeee0 UICommon.so`UIMessageCenter::cannotSetExtraData+0xe3()
7fffb130 
UICommon.so`UIExtraDataManager::setExtraDataString+0x546()
7fffb170 
UICommon.so`UIExtraDataManager::setSelectorWindowToolBarVisible+0x6a()

7fffb1b0 UIVirtualBoxManagerWidget::saveSettings+0x2f()
7fffb1f0 UIVirtualBoxManagerWidget::cleanup+0x12()
7fffb210 
UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
7fffb230 
UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()

7fffb250 UIVirtualBoxManager::cleanupWidgets+0x22()
7fffb270 UIVirtualBoxManager::cleanup+0x3a()
7fffb280 UIVirtualBoxManager::destroy+0x4b()
7fffb350 libQt5Core.so.5.15.4`void doActivate+0x4d4()
7fffb380 
libQt5Core.so.5.15.4`QCoreApplication::aboutToQuit+0x2a()
7fffb3a0 
libQt5Core.so.5.15.4`QCoreApplicationPrivate::execCleanup+0x49()

7fffb3f0 libQt5Core.so.5.15.4`QCoreApplication::exec+0x9c()
7fffb4d0 TrustedMain+0x27c()
7fffb560 main+0x5f()
7fffb590 _start_crt+0x87()
7fffb5a0 _start+0x18()


Am 25.08.23 09:23 schrieb Stephan Althaus 
:


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@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 

Re: [OpenIndiana-discuss] VirtualBox status?

[Predrag Zečević via openindiana-discuss]

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

7fffadf5e270 libc.so.1`_lwp_kill+0xa()
7fffadf5e2a0 libc.so.1`raise+0x22(6)
7fffadf5e2f0 libc.so.1`abort+0x58()
7fffadf5e330 
libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()
7fffadf5e350 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9()
7fffadf5e370 0x7fffa67f6099()
7fffadf5e460 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc()
7fffadf5e630 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
7fffadf5e9e0 libgcc_s.so.1`_Unwind_RaiseException+0x331()
7fffadf5ea10 libstdc++.so.6.0.28`__cxa_throw+0x40()
7fffadf5eb90 Medium::i_queryInfo+0x6a6()
7fffadf5ebd0 Medium::refreshState+0x8d()
7fffadf5ec20 MediumWrap::RefreshState+0xd1()
7fffadf5ecd0 VBoxXPCOM.so`XPTC_InvokeByIndex+0x13f()
7fffadf5eea0 VBoxXPCOMIPCC.so`ipcDConnectService::OnInvoke+0x3bc()
7fffadf5eeb0 VBoxXPCOMIPCC.so`ipcDConnectService::OnIncomingRequest+0x28()
7fffadf5ef00 VBoxXPCOMIPCC.so`DConnectWorker::Run+0x137()
7fffadf5ef20 VBoxXPCOM.so`nsThread::Main+0x23()
7fffadf5ef40 VBoxXPCOM.so`_pt_root+0x86()
7fffadf5ef50 VBoxXPCOM.so`_pt_iprt_root+0xc()
7fffadf5ef70 VBoxRT.so`rtThreadMain+0x34()
7fffadf5efb0 VBoxRT.so`rtThreadNativeMain+0x43()
7fffadf5efe0 libc.so.1`_thrp_setup+0x77(7fffaeaa4a40)
7fffadf5eff0 libc.so.1`_lwp_start()


also VirtualBox crashes some time with SIGSEGV



$C

7fffbfffe810 libQt5Widgets.so.5.15.4`QToolBar::toolButtonStyle()
7fffbfffe850 UIVirtualBoxManagerWidget::cleanup+0x12()
7fffbfffe870 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
7fffbfffe890 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()
7fffbfffe900 libQt5Core.so.5.15.4`QObject::event+0x40()
7fffbfffe930 
libQt5Widgets.so.5.15.4`QApplicationPrivate::notify_helper+0x82()
7fffbfffe9a0 libQt5Core.so.5.15.4`QCoreApplication::notifyInternal2+0x111()
7fffbfffea40 
libQt5Core.so.5.15.4`QCoreApplicationPrivate::sendPostedEvents+0x170()
7fffbfffea60 libQt5Core.so.5.15.4`postEventSourceDispatch+0x1b()
7fffbfffeae0 libglib-2.0.so.0.7400.7`g_main_context_dispatch+0x23d()
7fffbfffeb40 
libglib-2.0.so.0.7400.7`g_main_context_iterate.constprop.0+0x1c8()
7fffbfffeb60 libglib-2.0.so.0.7400.7`g_main_context_iteration+0x30()
7fffbfffebb0 libQt5Core.so.5.15.4`QEventDispatcherGlib::processEvents+0x64()
7fffbfffec30 libQt5Core.so.5.15.4`QEventLoop::exec+0x11b()
7fffbfffec80 UICommon.so`QIDialog::execute+0xd5()
7fffbfffed20 UICommon.so`UIMessageCenter::showMessageBox+0x33e()
7fffbfffedb0 UICommon.so`UIMessageCenter::message+0xff()
7fffbfffee20 UICommon.so`UIMessageCenter::error+0x3e()
7fffbfffeee0 UICommon.so`UIMessageCenter::cannotSetExtraData+0xe3()
7fffb130 UICommon.so`UIExtraDataManager::setExtraDataString+0x546()
7fffb170 
UICommon.so`UIExtraDataManager::setSelectorWindowToolBarVisible+0x6a()
7fffb1b0 UIVirtualBoxManagerWidget::saveSettings+0x2f()
7fffb1f0 UIVirtualBoxManagerWidget::cleanup+0x12()
7fffb210 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
7fffb230 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()
7fffb250 UIVirtualBoxManager::cleanupWidgets+0x22()
7fffb270 UIVirtualBoxManager::cleanup+0x3a()
7fffb280 UIVirtualBoxManager::destroy+0x4b()
7fffb350 libQt5Core.so.5.15.4`void doActivate+0x4d4()
7fffb380 libQt5Core.so.5.15.4`QCoreApplication::aboutToQuit+0x2a()
7fffb3a0 
libQt5Core.so.5.15.4`QCoreApplicationPrivate::execCleanup+0x49()
7fffb3f0 libQt5Core.so.5.15.4`QCoreApplication::exec+0x9c()
7fffb4d0 TrustedMain+0x27c()
7fffb560 main+0x5f()
7fffb590 _start_crt+0x87()
7fffb5a0 _start+0x18()


Am 25.08.23 09:23 schrieb Stephan Althaus  :


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@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 

Re: [OpenIndiana-discuss] VirtualBox status?

[Carsten Grzemba via openindiana-discuss]

Unfortunately starting the GUI VirtualBox still leads to crash VBoxSVC 
(SIGABRT) and no installed VM's listed in the GUI.

> $C
7fffadf5e270 libc.so.1`_lwp_kill+0xa()
7fffadf5e2a0 libc.so.1`raise+0x22(6)
7fffadf5e2f0 libc.so.1`abort+0x58()
7fffadf5e330 
libstdc++.so.6.0.28`__gnu_cxx::__verbose_terminate_handler+0x65()
7fffadf5e350 libstdc++.so.6.0.28`__cxxabiv1::__terminate+9()
7fffadf5e370 0x7fffa67f6099()
7fffadf5e460 libstdc++.so.6.0.28`__gxx_personality_v0+0x2bc()
7fffadf5e630 libgcc_s.so.1`_Unwind_RaiseException_Phase2+0xa6()
7fffadf5e9e0 libgcc_s.so.1`_Unwind_RaiseException+0x331()
7fffadf5ea10 libstdc++.so.6.0.28`__cxa_throw+0x40()
7fffadf5eb90 Medium::i_queryInfo+0x6a6()
7fffadf5ebd0 Medium::refreshState+0x8d()
7fffadf5ec20 MediumWrap::RefreshState+0xd1()
7fffadf5ecd0 VBoxXPCOM.so`XPTC_InvokeByIndex+0x13f()
7fffadf5eea0 VBoxXPCOMIPCC.so`ipcDConnectService::OnInvoke+0x3bc()
7fffadf5eeb0 VBoxXPCOMIPCC.so`ipcDConnectService::OnIncomingRequest+0x28()
7fffadf5ef00 VBoxXPCOMIPCC.so`DConnectWorker::Run+0x137()
7fffadf5ef20 VBoxXPCOM.so`nsThread::Main+0x23()
7fffadf5ef40 VBoxXPCOM.so`_pt_root+0x86()
7fffadf5ef50 VBoxXPCOM.so`_pt_iprt_root+0xc()
7fffadf5ef70 VBoxRT.so`rtThreadMain+0x34()
7fffadf5efb0 VBoxRT.so`rtThreadNativeMain+0x43()
7fffadf5efe0 libc.so.1`_thrp_setup+0x77(7fffaeaa4a40)
7fffadf5eff0 libc.so.1`_lwp_start()


also VirtualBox crashes some time with SIGSEGV


> $C
7fffbfffe810 libQt5Widgets.so.5.15.4`QToolBar::toolButtonStyle()
7fffbfffe850 UIVirtualBoxManagerWidget::cleanup+0x12()
7fffbfffe870 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
7fffbfffe890 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()
7fffbfffe900 libQt5Core.so.5.15.4`QObject::event+0x40()
7fffbfffe930 
libQt5Widgets.so.5.15.4`QApplicationPrivate::notify_helper+0x82()
7fffbfffe9a0 libQt5Core.so.5.15.4`QCoreApplication::notifyInternal2+0x111()
7fffbfffea40 
libQt5Core.so.5.15.4`QCoreApplicationPrivate::sendPostedEvents+0x170()
7fffbfffea60 libQt5Core.so.5.15.4`postEventSourceDispatch+0x1b()
7fffbfffeae0 libglib-2.0.so.0.7400.7`g_main_context_dispatch+0x23d()
7fffbfffeb40 
libglib-2.0.so.0.7400.7`g_main_context_iterate.constprop.0+0x1c8()
7fffbfffeb60 libglib-2.0.so.0.7400.7`g_main_context_iteration+0x30()
7fffbfffebb0 libQt5Core.so.5.15.4`QEventDispatcherGlib::processEvents+0x64()
7fffbfffec30 libQt5Core.so.5.15.4`QEventLoop::exec+0x11b()
7fffbfffec80 UICommon.so`QIDialog::execute+0xd5()
7fffbfffed20 UICommon.so`UIMessageCenter::showMessageBox+0x33e()
7fffbfffedb0 UICommon.so`UIMessageCenter::message+0xff()
7fffbfffee20 UICommon.so`UIMessageCenter::error+0x3e()
7fffbfffeee0 UICommon.so`UIMessageCenter::cannotSetExtraData+0xe3()
7fffb130 UICommon.so`UIExtraDataManager::setExtraDataString+0x546()
7fffb170 
UICommon.so`UIExtraDataManager::setSelectorWindowToolBarVisible+0x6a()
7fffb1b0 UIVirtualBoxManagerWidget::saveSettings+0x2f()
7fffb1f0 UIVirtualBoxManagerWidget::cleanup+0x12()
7fffb210 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x2a()
7fffb230 UIVirtualBoxManagerWidget::~UIVirtualBoxManagerWidget+0x12()
7fffb250 UIVirtualBoxManager::cleanupWidgets+0x22()
7fffb270 UIVirtualBoxManager::cleanup+0x3a()
7fffb280 UIVirtualBoxManager::destroy+0x4b()
7fffb350 libQt5Core.so.5.15.4`void doActivate+0x4d4()
7fffb380 libQt5Core.so.5.15.4`QCoreApplication::aboutToQuit+0x2a()
7fffb3a0 
libQt5Core.so.5.15.4`QCoreApplicationPrivate::execCleanup+0x49()
7fffb3f0 libQt5Core.so.5.15.4`QCoreApplication::exec+0x9c()
7fffb4d0 TrustedMain+0x27c()
7fffb560 main+0x5f()
7fffb590 _start_crt+0x87()
7fffb5a0 _start+0x18()


Am 25.08.23 09:23 schrieb Stephan Althaus  : 
> 
> 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@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
> 

Re: [OpenIndiana-discuss] VirtualBox status?

[Philip Kime]

signature.asc
Description: OpenPGP digital signature
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] VirtualBox status?

[Predrag Zečević via openindiana-discuss]

On 8/25/23 09:22, Stephan Althaus wrote:

So my VM is running on today's OI.


Regards,
Stephan


Hi Stephan,

Thanks for checks and report.

As soon as I have time, will give it a try

Best regards.

--
Predrag Zečević

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

Re: [OpenIndiana-discuss] VirtualBox status?

[Stephan Althaus]

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@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@projekte
applepie@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@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] VirtualBox status?

[Predrag Zečević via openindiana-discuss]

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@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


--
Predrag Zečević

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

Re: [OpenIndiana-discuss] VirtualBox status?

[Stephan Althaus]

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

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


Hello!

I will give it a try now,
pkg update is running, i'll report back.

Regards,

Stephan


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

Re: [OpenIndiana-discuss] Virtualbox webservice on 2023.05 won't start due to incorrect GSOAP version

[Stephan Althaus]

On 7/28/23 19:23, Philip Kime wrote:

Hmm, I already have this:

pkg install 
pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z
No updates necessary for this image.

and the GUI gives the GSOAP error in the ticket.

PK

--
Dr Phil. Philip Kime
BA (Hons) Msc (Dist) PhD


On 28 Jul 2023, at 18:40, Stephan Althaus  
wrote:

On 7/28/23 17:43, Philip Kime wrote:

I am trying to resolve the issue detailed on the bug tracker here:


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

any ideas on how to deal with this until a new VB package is available?

PK

--
Dr Phil. Philip Kime
BA (Hons) Msc (Dist) PhD



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

Hello!

I use

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

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

to get a working GUI.


We have to get some more libs PR'ed for rebuild with GCC-10 until this
is solved, and maybe the non-starting mate-system-monitor..


Regards,

Stephan



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



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


Ah i see now...

In oi-userland we need a PR for a virtualbox with a COMPONENT_REVISION=2 
for example (or even better an update to 6.1.46),
maybe the vboxwebsrv will run again, but we will fail in the GUI with 
the GCC-7-lib-problem..


i think we have to solve out this GCC-7 problem first..

Regards,
Stephan



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

Re: [OpenIndiana-discuss] Virtualbox webservice on 2023.05 won't start due to incorrect GSOAP version

[Philip Kime]

Hmm, I already have this:

pkg install 
pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z
No updates necessary for this image.

and the GUI gives the GSOAP error in the ticket.

PK

--
Dr Phil. Philip Kime
BA (Hons) Msc (Dist) PhD

> On 28 Jul 2023, at 18:40, Stephan Althaus  
> wrote:
> 
> On 7/28/23 17:43, Philip Kime wrote:
>> I am trying to resolve the issue detailed on the bug tracker here:
>> 
>> 
>> https://www.illumos.org/issues/15768
>> 
>> any ideas on how to deal with this until a new VB package is available?
>> 
>> PK
>> 
>> --
>> Dr Phil. Philip Kime
>> BA (Hons) Msc (Dist) PhD
>> 
>> 
>> 
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hello!
> 
> I use
> 
> pfexec pkg install
> pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z
> 
> pfexec pkg freeze
> pkg://openindiana.org/system/virtualbox@6.1.40,5.11-2022.0.0.0:20221108T082551Z
> 
> to get a working GUI.
> 
> 
> We have to get some more libs PR'ed for rebuild with GCC-10 until this
> is solved, and maybe the non-starting mate-system-monitor..
> 
> 
> Regards,
> 
> Stephan
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss



signature.asc
Description: OpenPGP digital signature
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Virtualbox webservice on 2023.05 won't start due to incorrect GSOAP version

[Stephan Althaus]

On 7/28/23 17:43, Philip Kime wrote:

I am trying to resolve the issue detailed on the bug tracker here:


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

any ideas on how to deal with this until a new VB package is available?

PK

--
Dr Phil. Philip Kime
BA (Hons) Msc (Dist) PhD



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


Hello!

I use

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


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


to get a working GUI.


We have to get some more libs PR'ed for rebuild with GCC-10 until this 
is solved, and maybe the non-starting mate-system-monitor..



Regards,

Stephan



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

Re: [OpenIndiana-discuss] Virtualbox 7.0.4?

[Carl Brewer]

On 16/01/2023 3:48 am, Till Wegmüller wrote:

Hi Carl

If you can at least check the compile process in [0] or even update the 
makefile then we can easily make the PR to update it.


I can also lead you through the process on IRC, Matrix or Discord or 
here on mail.


I'll get some time to work on it tomorrow, thank you




Greeting
Till

[0] 
https://github.com/OpenIndiana/oi-userland/tree/ced366e8e9a0a065ec50a3b5e08ae4415df9b9b8/components/sysutils/virtualbox


On 15.01.23 03:00, Carl Brewer wrote:

Hey,
Virtualbox 7 was released not long ago, now at 7.0.4, in oi-userland 
it's 6.1.40.  Anything I can do to help get it going?



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


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



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

Re: [OpenIndiana-discuss] Virtualbox 7.0.4?

[Till Wegmüller]

Hi Carl

If you can at least check the compile process in [0] or even update the 
makefile then we can easily make the PR to update it.


I can also lead you through the process on IRC, Matrix or Discord or 
here on mail.


Greeting
Till

[0] 
https://github.com/OpenIndiana/oi-userland/tree/ced366e8e9a0a065ec50a3b5e08ae4415df9b9b8/components/sysutils/virtualbox


On 15.01.23 03:00, Carl Brewer wrote:

Hey,
Virtualbox 7 was released not long ago, now at 7.0.4, in oi-userland 
it's 6.1.40.  Anything I can do to help get it going?



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


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

Re: [OpenIndiana-discuss] VirtualBox and USB passthru

[s...@pandora.be]

I've not been able to get USB passthru to work so far.

Last time I tried it panic'd my machine.

On the positive side on the current OI 2022.11 USB automount immediately works,
so as soon as some USB device is inserted it seems HAL (hardware abstraction 
daemon) knows about it and is aware of the new USB device. 

- Op 1 dec 2022 om 17:34 schreef Stephan Althaus 
stephan.alth...@duedinghausen.eu:

> Hello!
> 
> Maybe..  the device must not be used by an OI driver, this is the case
> with my Broadcom device..
> 
> $ pfexec mdb -ke '::prtusb'
> INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
> 1   xhci    2 pci1028,7b1   3.0  .   No Product String
> 2   usb_mid 35    device    1.1  0bf8.100c   FSC KBPC PX
> 3   hid 36    mouse 2.0  046d.c05a   USB Optical Mouse
> 4   hubd    18    hub   2.0  413c.2513   No Product String
> 5   usb_mid 32    device    2.0  8087.0a2b   No Product String
> 6   hubd    19    hub   2.0  413c.2134   USB2134
> *7   vboxusb 4 device    1.1  0a5c.5832   5880*
> 
> $ VBoxManage showvminfo aLinux | grep USB
> Pointing Device: USB Tablet
> VRDE property   : Client/DisableUSB = 
> OHCI USB:    disabled
> EHCI USB:    disabled
> *xHCI USB:    enabled*
> USB Device Filters:
> 
> steven@ubuntuvm:~$ lsusb
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> *Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. *
> Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> 
> HTH
> 
> Stephan
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

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

Re: [OpenIndiana-discuss] VirtualBox and USB passthru

[Stephan Althaus]

Hello!

Maybe..  the device must not be used by an OI driver, this is the case 
with my Broadcom device..


$ pfexec mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci    2 pci1028,7b1   3.0  .   No Product String
2   usb_mid 35    device    1.1  0bf8.100c   FSC KBPC PX
3   hid 36    mouse 2.0  046d.c05a   USB Optical Mouse
4   hubd    18    hub   2.0  413c.2513   No Product String
5   usb_mid 32    device    2.0  8087.0a2b   No Product String
6   hubd    19    hub   2.0  413c.2134   USB2134
*7   vboxusb 4 device    1.1  0a5c.5832   5880*

$ VBoxManage showvminfo aLinux | grep USB
Pointing Device: USB Tablet
VRDE property   : Client/DisableUSB = 
OHCI USB:    disabled
EHCI USB:    disabled
*xHCI USB:    enabled*
USB Device Filters:

steven@ubuntuvm:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
*Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. *
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


HTH

Stephan

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[s...@pandora.be]

"Vagrant" uses shared folders, and shared folders seem to work

vagrant automatically defines for me a mountpoint in a Vagrant VM /vagrant

works for me with VirtualBox 6.1.38 and the box:

$ vagrant box list
openindiana/hipster (virtualbox, 20220801)

in the vagrant vm there is:

$ pkg list | grep virtu
system/virtualbox/virtualbox-additions6.1.38-2022.0.0.0  i--

so in this case the VirtualBox host runs the same version of VirtualBox as the 
version of the vbox guest additions in the guest vm

Regards,
David Stes

- Op 7 okt 2022 om 9:00 schreef carl c...@bl.echidna.id.au:

> On 6/10/2022 7:06 pm, david allan finch wrote:
>> On 10/6/22 07:51, Predrag Zečević via openindiana-discuss wrote:
>>>
 The reference into VB's git seems to suggest that it was done in
 January?

 https://github.com/omniosorg/omnios-extra/pull/921

 I'm not seeing any issues with VB 6.1.38 on my OI servers, with a
 build from a week ago, but I'm not using shared folders at all.

>>> Host is OI (updated yesterday) and shared folders (to Win Guest) works:
>>>
>>> ; pkg list virtualbox
>>> NAME (PUBLISHER)  VERSION     IFO
>>> system/virtualbox 6.1.38-2022.0.0.0     i--
>>>
>> 
>> Running the update I see:
>> 
>> david@hal9k:~$ sudo pkg update
>> pkg: 0/1 catalogs successfully updated:
>> 
>>    1: Invalid contentpath
>> /var/pkg/cache/incoming-1975/update.20221006T06Z.C: CatalogPart failed
>> validation: The signature data for the
>> '/var/pkg/cache/incoming-1975/update.20221006T06Z.C' catalog file is not
>> valid.. (happened 4 times)
>>    2: Invalid contentpath
>> /var/pkg/cache/incoming-1975/update.20221006T07Z.C: CatalogPart failed
>> validation: The signature data for the
>> '/var/pkg/cache/incoming-1975/update.20221006T07Z.C' catalog file is not
>> valid.. (happened 4 times)
> 
> It's some issue with the distribution server?
> 
> Aurélien's looking into it.
> 
> 
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Carl Brewer]

On 6/10/2022 7:06 pm, david allan finch wrote:

On 10/6/22 07:51, Predrag Zečević via openindiana-discuss wrote:


The reference into VB's git seems to suggest that it was done in 
January?


https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a 
build from a week ago, but I'm not using shared folders at all.



Host is OI (updated yesterday) and shared folders (to Win Guest) works:

; pkg list virtualbox
NAME (PUBLISHER)  VERSION     IFO
system/virtualbox 6.1.38-2022.0.0.0     i--



Running the update I see:

david@hal9k:~$ sudo pkg update
pkg: 0/1 catalogs successfully updated:

   1: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T06Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
   2: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T07Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)


It's some issue with the distribution server?

Aurélien's looking into it.




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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Stephan Althaus]

On 10/6/22 12:19, david allan finch wrote:

On 10/6/22 10:36, Marcel Telka wrote:

Maybe rebuild-index would work better than rebiuld-index. :-)


I did spot that before I ran it, but as my first language is not 
Modern English but old-fashioned-westcounty-giberish I didn't think it 
should complain.




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



:-D



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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[david allan finch]

On 10/6/22 10:36, Marcel Telka wrote:

Maybe rebuild-index would work better than rebiuld-index. :-)


I did spot that before I ran it, but as my first language is not Modern 
English but old-fashioned-westcounty-giberish I didn't think it should 
complain.




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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Predrag Zečević via openindiana-discuss]

On 10/6/22 11:27, Stephan Althaus wrote:

On 10/6/22 10:52, david allan finch wrote:

On 10/6/22 09:20, Predrag Zečević wrote:

I would try:

:; pfexec pkg refresh --full
:; pfexec pkg rebiuld-index



thanks.

I just tried that, refresh gives the same error. I did this three 
times (refresh gives the error) and then tried the update and it gives 
the same error message.


This is weird as yesterday I build a new VM and did pkg update and it 
worked, but today that new VM see the same error that my older VM does.




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


Hi!

Tried this a minute ago and had the same error:

# pkg refresh --full && pkg rebiuld-index
pkg: 1/2 catalogs successfully updated:


   Invalid contentpath /var/pkg/cache/incoming-3290/catalog.summary.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-3290/catalog.summary.C' catalog file is not 
valid.. (happened 4 times)



Stephan

Checked right now, and yes it happens to me too!

And 'pfexec pkg update -v --be-name ...' fails too, with same error.

So, something is really broken her (luckily, I have kept few older BEs)!

Any clue how to fix this?





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


--
Predrag Zečević

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Marcel Telka]

On Thu, Oct 06, 2022 at 11:43:29AM +0200, Stephan Althaus wrote:
> On 10/6/22 11:36, Marcel Telka wrote:
> > On Thu, Oct 06, 2022 at 10:20:45AM +0200, Predrag Zečević via 
> > openindiana-discuss wrote:
> > > I would try:
> > > 
> > > :; pfexec pkg refresh --full
> > > :; pfexec pkg rebiuld-index
> > Maybe rebuild-index would work better than rebiuld-index. :-)
> > 
> You're right of course :-)
> 
> pfexec pkg refresh --full
> throws the problem.
> Did you try it?

Yes, pkg refresh does not work (hipster-encumbered publisher works okay):

# pkg refresh openindiana.org
pkg: 0/1 catalogs successfully updated:

   
  1: Invalid contentpath /var/pkg/cache/incoming-23873/update.20221006T06Z.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-23873/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
  2: Invalid contentpath /var/pkg/cache/incoming-23873/update.20221006T07Z.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-23873/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)

#


Also these commands does not work:

# pkg list -a
pkg: 1/2 catalogs successfully updated:


  1: Invalid contentpath /var/pkg/cache/incoming-24526/update.20221006T06Z.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-24526/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
  2: Invalid contentpath /var/pkg/cache/incoming-24526/update.20221006T07Z.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-24526/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)

# pkg list -u
pkg: 1/2 catalogs successfully updated:


  1: Invalid contentpath /var/pkg/cache/incoming-24712/update.20221006T06Z.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-24712/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
  2: Invalid contentpath /var/pkg/cache/incoming-24712/update.20221006T07Z.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-24712/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)

#


It is anything that needs access to full packages list.  Commands that does not
need full package list works:

# pkg list | head
NAME (PUBLISHER)  VERSIONIFO
SUNWcs0.5.11-2022.0.0.21255  i--
SUNWcsd   0.5.11-2022.0.0.21255  i--
antivirus/c_icap  0.5.10-2022.0.0.0  i--
antivirus/c_icap_modules  0.5.5-2022.0.0.0   i--
antivirus/clamav  0.105.1-2022.0.0.1 i--
antivirus/clamav-clamdtop 0.105.1-2022.0.0.1 i--
antivirus/clamav-common   0.105.1-2022.0.0.1 i--
antivirus/clamav-core 0.105.1-2022.0.0.1 i--
antivirus/clamav-milter   0.105.1-2022.0.0.1 i--
#

So apparently the openindiana.org repo/publisher is broken at
pkg.openindiana.org.


Regards.

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

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Stephan Althaus]

On 10/6/22 11:36, Marcel Telka wrote:

On Thu, Oct 06, 2022 at 10:20:45AM +0200, Predrag Zečević via 
openindiana-discuss wrote:

I would try:

:; pfexec pkg refresh --full
:; pfexec pkg rebiuld-index

Maybe rebuild-index would work better than rebiuld-index. :-)


You're right of course :-)

pfexec pkg refresh --full
throws the problem.
Did you try it?

Stephan


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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Marcel Telka]

On Thu, Oct 06, 2022 at 10:20:45AM +0200, Predrag Zečević via 
openindiana-discuss wrote:
> I would try:
> 
> :; pfexec pkg refresh --full
> :; pfexec pkg rebiuld-index

Maybe rebuild-index would work better than rebiuld-index. :-)

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

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Stephan Althaus]

On 10/6/22 10:52, david allan finch wrote:

On 10/6/22 09:20, Predrag Zečević wrote:

I would try:

:; pfexec pkg refresh --full
:; pfexec pkg rebiuld-index



thanks.

I just tried that, refresh gives the same error. I did this three 
times (refresh gives the error) and then tried the update and it gives 
the same error message.


This is weird as yesterday I build a new VM and did pkg update and it 
worked, but today that new VM see the same error that my older VM does.




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


Hi!

Tried this a minute ago and had the same error:

# pkg refresh --full && pkg rebiuld-index
pkg: 1/2 catalogs successfully updated:


  Invalid contentpath /var/pkg/cache/incoming-3290/catalog.summary.C: 
CatalogPart failed validation: The signature data for the 
'/var/pkg/cache/incoming-3290/catalog.summary.C' catalog file is not 
valid.. (happened 4 times)



Stephan



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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Predrag Zečević via openindiana-discuss]

On 10/6/22 11:06, Predrag Zečević wrote:



On 10/6/22 10:06, david allan finch wrote:

On 10/6/22 07:51, Predrag Zečević via openindiana-discuss wrote:


The reference into VB's git seems to suggest that it was done in 
January?


https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a 
build from a week ago, but I'm not using shared folders at all.



Host is OI (updated yesterday) and shared folders (to Win Guest) works:

; pkg list virtualbox
NAME (PUBLISHER)  VERSION     IFO
system/virtualbox 6.1.38-2022.0.0.0     i--



Running the update I see:

david@hal9k:~$ sudo pkg update
pkg: 0/1 catalogs successfully updated:

   1: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T06Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T06Z.C' catalog file is 
not valid.. (happened 4 times)
   2: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T07Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T07Z.C' catalog file is 
not valid.. (happened 4 times)


:(



Not sure,

I have several (empty) directories present:
:; find /var/pkg/cache/incoming-*
/var/pkg/cache/incoming-1272
/var/pkg/cache/incoming-15088
/var/pkg/cache/incoming-15095
/var/pkg/cache/incoming-15724
/var/pkg/cache/incoming-18944

I am not sure what will happen if you remove all /var/cache/incoming-* 
directories and try again... (and also I would not try that before 
creating backup BE).


Maybe someone has an idea how to solve it.
Regards.




Forgot to add (I have set this long time ago, to avoid growing cache == 
disk usage issues, which explains empty directories, I guess):


:; pkg property flush-content-cache-on-success
PROPERTY   VALUE
flush-content-cache-on-success True

Regards.


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




--
Predrag Zečević

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Predrag Zečević via openindiana-discuss]

On 10/6/22 10:06, david allan finch wrote:

On 10/6/22 07:51, Predrag Zečević via openindiana-discuss wrote:


The reference into VB's git seems to suggest that it was done in 
January?


https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a 
build from a week ago, but I'm not using shared folders at all.



Host is OI (updated yesterday) and shared folders (to Win Guest) works:

; pkg list virtualbox
NAME (PUBLISHER)  VERSION     IFO
system/virtualbox 6.1.38-2022.0.0.0     i--



Running the update I see:

david@hal9k:~$ sudo pkg update
pkg: 0/1 catalogs successfully updated:

   1: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T06Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
   2: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T07Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)


:(



Not sure,

I have several (empty) directories present:
:; find /var/pkg/cache/incoming-*
/var/pkg/cache/incoming-1272
/var/pkg/cache/incoming-15088
/var/pkg/cache/incoming-15095
/var/pkg/cache/incoming-15724
/var/pkg/cache/incoming-18944

I am not sure what will happen if you remove all /var/cache/incoming-* 
directories and try again... (and also I would not try that before 
creating backup BE).


Maybe someone has an idea how to solve it.
Regards.



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


--
Predrag Zečević

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[david allan finch]

On 10/6/22 09:20, Predrag Zečević wrote:

I would try:

:; pfexec pkg refresh --full
:; pfexec pkg rebiuld-index



thanks.

I just tried that, refresh gives the same error. I did this three times 
(refresh gives the error) and then tried the update and it gives the 
same error message.


This is weird as yesterday I build a new VM and did pkg update and it 
worked, but today that new VM see the same error that my older VM does.




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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Predrag Zečević via openindiana-discuss]

On 10/6/22 10:06, david allan finch wrote:

On 10/6/22 07:51, Predrag Zečević via openindiana-discuss wrote:


The reference into VB's git seems to suggest that it was done in 
January?


https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a 
build from a week ago, but I'm not using shared folders at all.



Host is OI (updated yesterday) and shared folders (to Win Guest) works:

; pkg list virtualbox
NAME (PUBLISHER)  VERSION     IFO
system/virtualbox 6.1.38-2022.0.0.0     i--



Running the update I see:

david@hal9k:~$ sudo pkg update
pkg: 0/1 catalogs successfully updated:

   1: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T06Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
   2: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T07Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)


:(

I would try:

:; pfexec pkg refresh --full
:; pfexec pkg rebiuld-index

Regards


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


--
Predrag Zečević

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[david allan finch]

On 10/6/22 07:51, Predrag Zečević via openindiana-discuss wrote:


The reference into VB's git seems to suggest that it was done in 
January?


https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a 
build from a week ago, but I'm not using shared folders at all.



Host is OI (updated yesterday) and shared folders (to Win Guest) works:

; pkg list virtualbox
NAME (PUBLISHER)  VERSION     IFO
system/virtualbox 6.1.38-2022.0.0.0     i--



Running the update I see:

david@hal9k:~$ sudo pkg update
pkg: 0/1 catalogs successfully updated:

  1: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T06Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T06Z.C' catalog file is not 
valid.. (happened 4 times)
  2: Invalid contentpath 
/var/pkg/cache/incoming-1975/update.20221006T07Z.C: CatalogPart failed 
validation: The signature data for the 
'/var/pkg/cache/incoming-1975/update.20221006T07Z.C' catalog file is not 
valid.. (happened 4 times)


:(



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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Predrag Zečević via openindiana-discuss]

On 10/6/22 00:43, Carl Brewer wrote:

On 5/10/2022 11:22 pm, Joshua M. Clulow via openindiana-discuss wrote:
On Wed, Oct 5, 2022, 00:28 david allan finch  
wrote:



Not quite sure what has broken it but, I installed the latest version of
VirtualBox 6.1.38 and updated the client extension into my OpenIndiana
VM client (it was the last build 2021Oct from the ISO). Around the same
time I did a pkg update to the latest changes. Since then the Shared
Folders have not worked. (The host is a windows 11 box there was also an
microsoft update on that day which I initially wondered about).

On boot of the VM I now see undefined symbol 'removectx' and
'installctx' from /usr/kernel/drv/smd64/vboxguest.



I believe that's related to: https://www.illumos.org/issues/13917


The reference into VB's git seems to suggest that it was done in January?

https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a build 
from a week ago, but I'm not using shared folders at all.



Host is OI (updated yesterday) and shared folders (to Win Guest) works:

; pkg list virtualbox
NAME (PUBLISHER)  VERSION 
IFO
system/virtualbox 6.1.38-2022.0.0.0 
i--


Regards.




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


--
Predrag Zečević

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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Carl Brewer]

On 5/10/2022 11:22 pm, Joshua M. Clulow via openindiana-discuss wrote:

On Wed, Oct 5, 2022, 00:28 david allan finch  wrote:


Not quite sure what has broken it but, I installed the latest version of
VirtualBox 6.1.38 and updated the client extension into my OpenIndiana
VM client (it was the last build 2021Oct from the ISO). Around the same
time I did a pkg update to the latest changes. Since then the Shared
Folders have not worked. (The host is a windows 11 box there was also an
microsoft update on that day which I initially wondered about).

On boot of the VM I now see undefined symbol 'removectx' and
'installctx' from /usr/kernel/drv/smd64/vboxguest.



I believe that's related to: https://www.illumos.org/issues/13917


The reference into VB's git seems to suggest that it was done in January?

https://github.com/omniosorg/omnios-extra/pull/921

I'm not seeing any issues with VB 6.1.38 on my OI servers, with a build 
from a week ago, but I'm not using shared folders at all.





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

Re: [OpenIndiana-discuss] VirtualBox Client Extensions Broken

[Joshua M. Clulow via openindiana-discuss]

On Wed, Oct 5, 2022, 00:28 david allan finch  wrote:

> Not quite sure what has broken it but, I installed the latest version of
> VirtualBox 6.1.38 and updated the client extension into my OpenIndiana
> VM client (it was the last build 2021Oct from the ISO). Around the same
> time I did a pkg update to the latest changes. Since then the Shared
> Folders have not worked. (The host is a windows 11 box there was also an
> microsoft update on that day which I initially wondered about).
>
> On boot of the VM I now see undefined symbol 'removectx' and
> 'installctx' from /usr/kernel/drv/smd64/vboxguest.
>

I believe that's related to: https://www.illumos.org/issues/13917


Cheers.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] VirtualBox Error because of kernel module version

[Predrag Zecevic via openindiana-discuss]

On 20.02.2022 20:22, Stephan Althaus wrote:

Hello!

I am getting errors today and had not updated for a week or so, 
virtualbox was last running on friday.


Maybe someone can check the kernel module versions if they are the 
same as i have:


$ VBoxManage startvm aLinux
Waiting for VM "aLinux" to power on...
VBoxManage: error: The virtual machine 'aLinux' has terminated 
unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), 
component MachineWrap, interface IMachine


$ modinfo|grep -i vb
*239 fa05b000  5a270 304   1  vboxdrv (VirtualBox HostDrv 
6.1.30r14843) <- ???*
240 fa09d000   79e8 305   1  vboxflt (VirtualBox NetDrv 
6.1.30r148432)
240 fa09d000   79e8   -   1  vboxflt (VirtualBox NetMod 
6.1.30r148432)
241 f9cc34f8    d38 306   1  vboxnet (VirtualBox NetAdp 
6.1.30r148432)
244 fa0b   70e0 307   1  vboxusb (VirtualBox USB 
6.1.30r148432)
245 fa0b7000   4838 308   1  vboxusbmon (VirtualBox USBMon 
6.1.30r148432


$ pkg info virtualbox
 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
    State: Installed
    Publisher: openindiana.org
  Version: 6.1.30
   Branch: 2022.0.0.2
   Packaging Date: January 28, 2022 at 06:55:02 AM
Last Install Time: September  7, 2019 at 07:43:17 PM
 Last Update Time: February  2, 2022 at 12:05:54 PM
 Size: 124.01 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.30-2022.0.0.2:20220128T065502Z
   Source URL: 
https://download.virtualbox.org/virtualbox/6.1.30/VirtualBox-6.1.30.tar.bz2

  Project URL: https://www.virtualbox.org/


Greetings,

Stephan

Hi Stephan,

I have identical package and modules:
:; modinfo|grep -i vb
182 f9ce94f8    d38 289   1  vboxnet (VirtualBox NetAdp 
6.1.30r148432)
184 f9f3f000  5a270 287   1  vboxdrv (VirtualBox HostDrv 
6.1.30r14843)
246 fa2a2000   79e8 288   1  vboxflt (VirtualBox NetDrv 
6.1.30r148432)
246 fa2a2000   79e8   -   1  vboxflt (VirtualBox NetMod 
6.1.30r148432)

247 fa2aa000   70e0 290   1  vboxusb (VirtualBox USB 6.1.30r148432)
248 fa2b1000   4838 291   1  vboxusbmon (VirtualBox USBMon 
6.1.30r148432


VB guest (CentOS 8 Stream)  was started (in headless mode) w/o problems, 
from /var/log/messages:


Feb 21 12:44:26 solarium kernel: vboxguest: loading out-of-tree module 
taints kernel.
Feb 21 12:44:26 solarium kernel: vboxguest: module verification failed: 
signature and/or required key missing - tainting kernel
Feb 21 12:44:26 solarium kernel: vboxguest: Successfully loaded version 
6.1.30 r148432


Regards.

P.S: OI was updated on
:; beadm list -K date oi_220215.oi_nvidia
BE  Active Mountpoint Space  Policy Created
oi_220215.oi_nvidia NR /  51,76G static 2022-02-15 14:15




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


--
Predrag Zečević
predrag.zecevic.1...@googlemail.com


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

Re: [OpenIndiana-discuss] VirtualBox Error because of kernel module version

[Stephan Althaus]

On 2/20/22 20:22, Stephan Althaus wrote:

Hello!

I am getting errors today and had not updated for a week or so, 
virtualbox was last running on friday.


Maybe someone can check the kernel module versions if they are the 
same as i have:


$ VBoxManage startvm aLinux
Waiting for VM "aLinux" to power on...
VBoxManage: error: The virtual machine 'aLinux' has terminated 
unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), 
component MachineWrap, interface IMachine


$ modinfo|grep -i vb
*239 fa05b000  5a270 304   1  vboxdrv (VirtualBox HostDrv 
6.1.30r14843) <- ???*
240 fa09d000   79e8 305   1  vboxflt (VirtualBox NetDrv 
6.1.30r148432)
240 fa09d000   79e8   -   1  vboxflt (VirtualBox NetMod 
6.1.30r148432)
241 f9cc34f8    d38 306   1  vboxnet (VirtualBox NetAdp 
6.1.30r148432)
244 fa0b   70e0 307   1  vboxusb (VirtualBox USB 
6.1.30r148432)
245 fa0b7000   4838 308   1  vboxusbmon (VirtualBox USBMon 
6.1.30r148432


$ pkg info virtualbox
 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
    State: Installed
    Publisher: openindiana.org
  Version: 6.1.30
   Branch: 2022.0.0.2
   Packaging Date: January 28, 2022 at 06:55:02 AM
Last Install Time: September  7, 2019 at 07:43:17 PM
 Last Update Time: February  2, 2022 at 12:05:54 PM
 Size: 124.01 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.30-2022.0.0.2:20220128T065502Z
   Source URL: 
https://download.virtualbox.org/virtualbox/6.1.30/VirtualBox-6.1.30.tar.bz2

  Project URL: https://www.virtualbox.org/


Greetings,

Stephan

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


Hello!

I am using a be from 2022-02-06 right now and here virtualbox works, and 
has the same kernel module versions.


So it is something different..

$ modinfo|grep -i vb
239 fa059000  5a270 304   1  vboxdrv (VirtualBox HostDrv 
6.1.30r14843)
240 fa09b000   79e8 305   1  vboxflt (VirtualBox NetDrv 
6.1.30r148432)
240 fa09b000   79e8   -   1  vboxflt (VirtualBox NetMod 
6.1.30r148432)
241 f9cc24f8    d38 306   1  vboxnet (VirtualBox NetAdp 
6.1.30r148432)

244 fa0ae000   70e0 307   1  vboxusb (VirtualBox USB 6.1.30r148432)
245 fa0b5000   4838 308   1  vboxusbmon (VirtualBox USBMon 
6.1.30r148432


Sorry, didn't want to irritate anyone..

Stephan



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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Carl Brewer]

6.1.24 was released a couple of days ago, I can't see anything 
showstopping in the changelog.



On 7/06/2021 5:32 pm, Predrag Zecevic wrote:

On 05.06.2021 12:16, Andreas Wacknitz wrote:

Any news on this issue? Shall I merge the PR or close it?

Andreas



Thanks Andreas,

I am using it, and so far I could not spot problems...
(NOTE: not using any GUI guest, just headless)

Regards.


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





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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Predrag Zecevic]

On 05.06.2021 12:16, Andreas Wacknitz wrote:

Any news on this issue? Shall I merge the PR or close it?

Andreas



Thanks Andreas,

I am using it, and so far I could not spot problems...
(NOTE: not using any GUI guest, just headless)

Regards.


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


--
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.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 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!

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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Carl Brewer]

On 5/06/2021 8:16 pm, Andreas Wacknitz wrote:

Any news on this issue? Shall I merge the PR or close it?


I couldn't get it to compile, but that's not because of something wrong 
with it, just I don't know the magic to make it happen.  +1 from me


Carl

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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Stephan Althaus]

On 6/5/21 12:16 PM, Andreas Wacknitz wrote:
> Any news on this issue? Shall I merge the PR or close it?
>
> Andreas
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

Merge +1


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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Andreas Wacknitz]

Any news on this issue? Shall I merge the PR or close it?

Andreas


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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Stephan Althaus]

On 5/21/21 9:40 AM, Predrag Zecevic wrote:
> On 21.05.2021 07:10, Stephan Althaus wrote:
>> On 5/19/21 1:30 PM, Predrag Zecevic wrote:
>>> On 19.05.2021 12:25, Stephan Althaus wrote:
>> Hello!
>>
>> i am using this version for a week now, no issues here.
>>
>> @Carl: did you also had time to test version 6.1.22 ?
>>
>> Stephan
>
> Hi Stephan,
>
> where it can be retrieved from? I would like to test it too.
> Regards.
>
>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

 At the moment here:

 userland    origin   online F
 http://duedinghausen.eu:1/userland/

>>>
>>> Hi Stephan,
>>>
>>> seems it is working fine (at least for headless guests, since I am in
>>> home office now):
>>>
>>> :; pfexec pkg set-publisher -O http://duedinghausen.eu:1/userland/
>>> userland
>>> :; pfexec pkg update pkg:/system/virtualbox@6.1.22-2020.0.1.0
>>> :; pfexec pkg unset-publisher userland
>>>
>>>
>>> Guest (CentOS 8 headless started; rdesktop connection works; xfreerdp
>>> connects but it stucks --- maybe internal network error) and I can use
>>> shared folder (also VirtualBox Guest Additions installer has finished
>>> w/o problems).
>>>
>>> Many thanks
>>>
>>> P.S: did not checked guest with GUI yet...
>>>
>> Hello!
>>
>> However, i found a bootup message
>>
>> May 21 07:06:04 myhost svc.startd[9]: [ID 652011 daemon.warning]
>> svc:/application/virtualbox/zoneaccess:default: Method
>> "/opt/VirtualBox/VBoxZoneAccess" failed with exit status 127.
>>
>> and i don't know what it is all about. i have no "virtual box zone" -
>> what ever that might be.
>>
>> Stephan
>>
>>
> Maybe your service is set to be started, but not configured? E.G. that
> is supposed to be used when you have VBox running in Zone. I did not
> look closer for documentation.
>
> On my box (VBox is *not* running in Zone):
> :; svcs -a | grep virtualbox
> disabled   May_17   svc:/application/virtualbox/autostart:default
> disabled   May_17   svc:/application/virtualbox/webservice:default
> disabled   May_17   svc:/application/virtualbox/balloonctrl:default
> disabled   May_17   svc:/application/virtualbox/zoneaccess:default
> online May_17   svc:/application/virtualbox/run-once:default
>
> Regards.
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
Yes, you are right:

$ svcs -a | grep virtualbox
disabled    7:06:00 svc:/application/virtualbox/balloonctrl:default
disabled    7:06:00 svc:/application/virtualbox/autostart:default
disabled    7:06:00 svc:/application/virtualbox/webservice:default
online  7:06:04 svc:/application/virtualbox/run-once:default
maintenance 7:06:04 svc:/application/virtualbox/zoneaccess:default

i disabled it as i don't need it:

# svcadm disable svc:/application/virtualbox/zoneaccess:default


Thank you for this valueable hint, Predrag!

Stephan



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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Predrag Zecevic]

On 21.05.2021 09:40, Predrag Zecevic wrote:

On 21.05.2021 07:10, Stephan Althaus wrote:

On 5/19/21 1:30 PM, Predrag Zecevic wrote:

On 19.05.2021 12:25, Stephan Althaus wrote:

Hello!

i am using this version for a week now, no issues here.

@Carl: did you also had time to test version 6.1.22 ?

Stephan


Hi Stephan,

where it can be retrieved from? I would like to test it too.
Regards.




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




At the moment here:

userland    origin   online F
http://duedinghausen.eu:1/userland/



Hi Stephan,

seems it is working fine (at least for headless guests, since I am in
home office now):

:; pfexec pkg set-publisher -O http://duedinghausen.eu:1/userland/
userland
:; pfexec pkg update pkg:/system/virtualbox@6.1.22-2020.0.1.0
:; pfexec pkg unset-publisher userland


Guest (CentOS 8 headless started; rdesktop connection works; xfreerdp
connects but it stucks --- maybe internal network error) and I can use
shared folder (also VirtualBox Guest Additions installer has finished
w/o problems).

Many thanks

P.S: did not checked guest with GUI yet...


Hello!

However, i found a bootup message

May 21 07:06:04 myhost svc.startd[9]: [ID 652011 daemon.warning]
svc:/application/virtualbox/zoneaccess:default: Method
"/opt/VirtualBox/VBoxZoneAccess" failed with exit status 127.

and i don't know what it is all about. i have no "virtual box zone" -
what ever that might be.

Stephan


Maybe your service is set to be started, but not configured? E.G. that 
is supposed to be used when you have VBox running in Zone. I did not 
look closer for documentation.


On my box (VBox is *not* running in Zone):
:; svcs -a | grep virtualbox
disabled   May_17   svc:/application/virtualbox/autostart:default
disabled   May_17   svc:/application/virtualbox/webservice:default
disabled   May_17   svc:/application/virtualbox/balloonctrl:default
disabled   May_17   svc:/application/virtualbox/zoneaccess:default
online May_17   svc:/application/virtualbox/run-once:default

Regards.

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





Hi all,

VirtualBox installed:
:; pkg list virtualbox
NAME (PUBLISHER)  VERSION 
 IFO
system/virtualbox (userland)  6.1.22-2020.0.1.0 
 i--


Regarding ZoneAccess, IHMO its manifest (XML) needs fix:
:; grep -E "exec=.*VBoxZoneAccess" 
/var/svc/manifest/application/virtualbox/virtualbox-zoneaccess.xml

exec='/opt/VirtualBox/VBoxZoneAccess'

:; file /opt/VirtualBox/VBoxZoneAccess
/opt/VirtualBox/VBoxZoneAccess: cannot open 
`/opt/VirtualBox/VBoxZoneAccess' (No such file or directory)


:; find /opt/VirtualBox/ -name VBoxZoneAccess
/opt/VirtualBox/amd64/VBoxZoneAccess

There is no sym-link or anything similar. It could be that more stuff is 
broken, but I did not checked all of them, just this one.


Regards.

--
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.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 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!

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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Predrag Zecevic]

On 21.05.2021 07:10, Stephan Althaus wrote:

On 5/19/21 1:30 PM, Predrag Zecevic wrote:

On 19.05.2021 12:25, Stephan Althaus wrote:

Hello!

i am using this version for a week now, no issues here.

@Carl: did you also had time to test version 6.1.22 ?

Stephan


Hi Stephan,

where it can be retrieved from? I would like to test it too.
Regards.




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




At the moment here:

userland    origin   online F
http://duedinghausen.eu:1/userland/



Hi Stephan,

seems it is working fine (at least for headless guests, since I am in
home office now):

:; pfexec pkg set-publisher -O http://duedinghausen.eu:1/userland/
userland
:; pfexec pkg update pkg:/system/virtualbox@6.1.22-2020.0.1.0
:; pfexec pkg unset-publisher userland


Guest (CentOS 8 headless started; rdesktop connection works; xfreerdp
connects but it stucks --- maybe internal network error) and I can use
shared folder (also VirtualBox Guest Additions installer has finished
w/o problems).

Many thanks

P.S: did not checked guest with GUI yet...


Hello!

However, i found a bootup message

May 21 07:06:04 myhost svc.startd[9]: [ID 652011 daemon.warning]
svc:/application/virtualbox/zoneaccess:default: Method
"/opt/VirtualBox/VBoxZoneAccess" failed with exit status 127.

and i don't know what it is all about. i have no "virtual box zone" -
what ever that might be.

Stephan


Maybe your service is set to be started, but not configured? E.G. that 
is supposed to be used when you have VBox running in Zone. I did not 
look closer for documentation.


On my box (VBox is *not* running in Zone):
:; svcs -a | grep virtualbox
disabled   May_17   svc:/application/virtualbox/autostart:default
disabled   May_17   svc:/application/virtualbox/webservice:default
disabled   May_17   svc:/application/virtualbox/balloonctrl:default
disabled   May_17   svc:/application/virtualbox/zoneaccess:default
online May_17   svc:/application/virtualbox/run-once:default

Regards.

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



--
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.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 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!

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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Stephan Althaus]

On 5/19/21 1:30 PM, Predrag Zecevic wrote:
> On 19.05.2021 12:25, Stephan Althaus wrote:
 Hello!

 i am using this version for a week now, no issues here.

 @Carl: did you also had time to test version 6.1.22 ?

 Stephan
>>>
>>> Hi Stephan,
>>>
>>> where it can be retrieved from? I would like to test it too.
>>> Regards.
>>>


 ___
 openindiana-discuss mailing list
 openindiana-discuss@openindiana.org
 https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>
>> At the moment here:
>>
>> userland    origin   online F
>> http://duedinghausen.eu:1/userland/
>>
>
> Hi Stephan,
>
> seems it is working fine (at least for headless guests, since I am in
> home office now):
>
> :; pfexec pkg set-publisher -O http://duedinghausen.eu:1/userland/
> userland
> :; pfexec pkg update pkg:/system/virtualbox@6.1.22-2020.0.1.0
> :; pfexec pkg unset-publisher userland
>
>
> Guest (CentOS 8 headless started; rdesktop connection works; xfreerdp
> connects but it stucks --- maybe internal network error) and I can use
> shared folder (also VirtualBox Guest Additions installer has finished
> w/o problems).
>
> Many thanks
>
> P.S: did not checked guest with GUI yet...
>
Hello!

However, i found a bootup message

May 21 07:06:04 myhost svc.startd[9]: [ID 652011 daemon.warning]
svc:/application/virtualbox/zoneaccess:default: Method
"/opt/VirtualBox/VBoxZoneAccess" failed with exit status 127.

and i don't know what it is all about. i have no "virtual box zone" -
what ever that might be.

Stephan



$ dmesg|grep -i vbox

May 21 07:06:01 myhost vboxdrv: [ID 177632 kern.info] cpu_t::cpu_runrun
@ 0xd8 (216)
May 21 07:06:01 myhost vboxdrv: [ID 460700 kern.info]
cpu_t::cpu_kprunrun @ 0xd9 (217)
May 21 07:06:01 myhost vboxdrv: [ID 444890 kern.info]
kthread_t::t_preempt @ 0x2c (44)
May 21 07:06:01 myhost vboxdrv: [ID 171789 kern.info] kthread_t::t_did @
0x118 (280)
May 21 07:06:01 myhost vboxdrv: [ID 150368 kern.info] kthread_t::t_intr
@ 0x108 (264)
May 21 07:06:01 myhost vboxdrv: [ID 454121 kern.info] kthread_t::t_lockp
@ 0x200 (512)
May 21 07:06:01 myhost vboxdrv: [ID 669395 kern.info] kthread_t::t_procp
@ 0x198 (408)
May 21 07:06:01 myhost vboxdrv: [ID 646993 kern.info] tsc::mode
Invariant @ tentative 3095680101 Hz
May 21 07:06:01 myhost pseudo: [ID 129642 kern.info] pseudo-device: vboxdrv0
May 21 07:06:01 myhost genunix: [ID 936769 kern.info] vboxdrv0 is
/pseudo/vboxdrv@0
May 21 07:06:01 myhost pseudo: [ID 129642 kern.info] pseudo-device: vboxflt0
May 21 07:06:01 myhost genunix: [ID 936769 kern.info] vboxflt0 is
/pseudo/vboxflt@0
May 21 07:06:01 myhost gld: [ID 944156 kern.info] vboxnet0: vboxnet:
type "ether" mac address 08:00:27:a3:4a:2d
May 21 07:06:01 myhost pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
May 21 07:06:01 myhost genunix: [ID 936769 kern.info] vboxnet0 is
/pseudo/vboxnet@0
May 21 07:06:01 myhost pseudo: [ID 129642 kern.info] pseudo-device: vboxnet0
May 21 07:06:01 myhost genunix: [ID 936769 kern.info] vboxnet0 is
/pseudo/vboxnet@0
May 21 07:06:01 myhost vboxusb: [ID 248386 kern.info] usba_ep_data_t is
32 bytes
May 21 07:06:01 myhost vboxusb: [ID 323768 kern.info]
usba_ep_data_t::ep_descr @ 0x0 (0)
May 21 07:06:01 myhost pseudo: [ID 129642 kern.info] pseudo-device:
vboxusbmon0
May 21 07:06:01 myhost genunix: [ID 936769 kern.info] vboxusbmon0 is
/pseudo/vboxusbmon@0
May 21 07:06:04 myhost svc.startd[9]: [ID 652011 daemon.warning]
svc:/application/virtualbox/zoneaccess:default: Method
"/opt/VirtualBox/VBoxZoneAccess" failed with exit status 127.
May 21 07:06:28 myhost pseudo: [ID 129642 kern.info] pseudo-device:
vboxusbmon0
May 21 07:06:28 myhost genunix: [ID 936769 kern.info] vboxusbmon0 is
/pseudo/vboxusbmon@0
May 21 07:06:29 myhost pseudo: [ID 129642 kern.info] pseudo-device: vboxdrv0
May 21 07:06:29 myhost genunix: [ID 936769 kern.info] vboxdrv0 is
/pseudo/vboxdrv@0


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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Carl Brewer]

On 19/05/2021 8:12 pm, Stephan Althaus wrote:



Hello!

i am using this version for a week now, no issues here.

@Carl: did you also had time to test version 6.1.22 ?


No, I couldn't get it to compile, something I did wrong no-doubt.

Carl


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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Predrag Zecevic]

On 19.05.2021 12:25, Stephan Althaus wrote:

Hello!

i am using this version for a week now, no issues here.

@Carl: did you also had time to test version 6.1.22 ?

Stephan


Hi Stephan,

where it can be retrieved from? I would like to test it too.
Regards.




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




At the moment here:

userland    origin   online F 
http://duedinghausen.eu:1/userland/




Hi Stephan,

seems it is working fine (at least for headless guests, since I am in 
home office now):


:; pfexec pkg set-publisher -O http://duedinghausen.eu:1/userland/ 
userland

:; pfexec pkg update pkg:/system/virtualbox@6.1.22-2020.0.1.0
:; pfexec pkg unset-publisher userland


Guest (CentOS 8 headless started; rdesktop connection works; xfreerdp 
connects but it stucks --- maybe internal network error) and I can use 
shared folder (also VirtualBox Guest Additions installer has finished 
w/o problems).


Many thanks

P.S: did not checked guest with GUI yet...

--
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.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 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!

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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Predrag Zecevic]

On 19.05.2021 12:12, Stephan Althaus wrote:

On 05/11/21 01:01 PM, Stephan Althaus wrote:

On 05/11/21 11:47 AM, Carl Brewer wrote:

On 11/05/2021 10:35 am, Carl Brewer wrote:

On 10/05/2021 9:47 pm, Andreas Wacknitz wrote:

I have created a PR: 
https://github.com/OpenIndiana/oi-userland/pull/6739

As I said before: I cannot test it so I will leave it to the community
to test it appropriately and give it an approval.


Testing it now, will let you know


I know this is a dumb question, but I can't quickly find the answer, 
to test this, I need to build it. To build it, I have done this :


 git clone https://github.com/OpenIndiana/oi-userland

How do I then update the virtualboix src to 6739 so I can compile & 
test it?  With SVN I'd have just done an svn update, git is a foreign 
language to me :/


Carl




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


cd oi-userland

git fetch origin pull/6739/head:pr-6739
git checkout pr-6739
cd sysutils/virtualbox

gmake publish


Stephan


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


Hello!

i am using this version for a week now, no issues here.

@Carl: did you also had time to test version 6.1.22 ?

Stephan


Hi Stephan,

where it can be retrieved from? I would like to test it too.
Regards.




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


--
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.zece...@2e-systems.com

headquarter: 2e Systems GmbH, Koenigsteiner Str. 107, 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!

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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Stephan Althaus]

On 05/11/21 01:01 PM, Stephan Althaus wrote:

On 05/11/21 11:47 AM, Carl Brewer wrote:

On 11/05/2021 10:35 am, Carl Brewer wrote:

On 10/05/2021 9:47 pm, Andreas Wacknitz wrote:

I have created a PR: 
https://github.com/OpenIndiana/oi-userland/pull/6739

As I said before: I cannot test it so I will leave it to the community
to test it appropriately and give it an approval.


Testing it now, will let you know


I know this is a dumb question, but I can't quickly find the answer, 
to test this, I need to build it. To build it, I have done this :


 git clone https://github.com/OpenIndiana/oi-userland

How do I then update the virtualboix src to 6739 so I can compile & 
test it?  With SVN I'd have just done an svn update, git is a foreign 
language to me :/


Carl




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


cd oi-userland

git fetch origin pull/6739/head:pr-6739
git checkout pr-6739
cd sysutils/virtualbox

gmake publish


Stephan


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


Hello!

i am using this version for a week now, no issues here.

@Carl: did you also had time to test version 6.1.22 ?

Stephan



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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Stephan Althaus]

On 05/11/21 11:47 AM, Carl Brewer wrote:

On 11/05/2021 10:35 am, Carl Brewer wrote:

On 10/05/2021 9:47 pm, Andreas Wacknitz wrote:

I have created a PR: 
https://github.com/OpenIndiana/oi-userland/pull/6739

As I said before: I cannot test it so I will leave it to the community
to test it appropriately and give it an approval.


Testing it now, will let you know


I know this is a dumb question, but I can't quickly find the answer, 
to test this, I need to build it. To build it, I have done this :


 git clone https://github.com/OpenIndiana/oi-userland

How do I then update the virtualboix src to 6739 so I can compile & 
test it?  With SVN I'd have just done an svn update, git is a foreign 
language to me :/


Carl




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


cd oi-userland

git fetch origin pull/6739/head:pr-6739
git checkout pr-6739
cd sysutils/virtualbox

gmake publish


Stephan


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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Carl Brewer]

On 11/05/2021 10:35 am, Carl Brewer wrote:

On 10/05/2021 9:47 pm, Andreas Wacknitz wrote:


I have created a PR: https://github.com/OpenIndiana/oi-userland/pull/6739
As I said before: I cannot test it so I will leave it to the community
to test it appropriately and give it an approval.


Testing it now, will let you know


I know this is a dumb question, but I can't quickly find the answer, to 
test this, I need to build it. To build it, I have done this :


 git clone https://github.com/OpenIndiana/oi-userland

How do I then update the virtualboix src to 6739 so I can compile & test 
it?  With SVN I'd have just done an svn update, git is a foreign 
language to me :/


Carl




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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Carl Brewer]

On 10/05/2021 9:47 pm, Andreas Wacknitz wrote:


I have created a PR: https://github.com/OpenIndiana/oi-userland/pull/6739
As I said before: I cannot test it so I will leave it to the community
to test it appropriately and give it an approval.


Testing it now, will let you know

Carl


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

Re: [OpenIndiana-discuss] Virtualbox 6.1.22?

[Andreas Wacknitz]

Am 07.05.21 um 09:35 schrieb Carl Brewer:


Hey Andreas et al,
I just noticed VirtualBox 6.1.22 was released a few days ago, I'm
happy to test it out if there's a build ready to go?

Thank you
Carl

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

I have created a PR: https://github.com/OpenIndiana/oi-userland/pull/6739
As I said before: I cannot test it so I will leave it to the community
to test it appropriately and give it an approval.

Regards,
Andreas

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

Re: [OpenIndiana-discuss] Virtualbox and USB webcam

[Tony Brian Albers]

On Fri, 2021-05-07 at 17:37 +1000, Carl Brewer wrote:
> On 8/01/2021 10:09 pm, Till Wegmueller wrote:
> > Hey Tony
> > 
> > Here in the EU I always get myself a USB Gaming Headset for my
> > Audio 
> > needs. They are Cheap(ish) and you can get yourself a Wireless
> > Headset 
> > that has a dedicated receiver that needs no special driver, other
> > than 
> > Audio. You might also get away by simply using the Mic, Headset on
> > the 
> > host and using Virtuablox Audio.
> > 
> > And thanks for that Note that may be why I was unsuccessful in the
> > past 
> > with certain pass through combinations.
> 
> This isn't relevant?
> https://www.virtualbox.org/ticket/20176
> 
> 
> 

Nah, I managed to get the webcam working fine as soon as I got the USB
port right. But the mentioned bug is something that we should be aware
of nevertheless.

/tony

-- 
Tony Albers - Systems Architect - IT Development Royal Danish Library,
Victor Albecks Vej 1, 8000 Aarhus C, Denmark
Tel: +45 2566 2383 - CVR/SE: 2898 8842 - EAN: 5798000792142
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Virtualbox and USB webcam

[Carl Brewer]

On 8/01/2021 10:09 pm, Till Wegmueller wrote:

Hey Tony

Here in the EU I always get myself a USB Gaming Headset for my Audio 
needs. They are Cheap(ish) and you can get yourself a Wireless Headset 
that has a dedicated receiver that needs no special driver, other than 
Audio. You might also get away by simply using the Mic, Headset on the 
host and using Virtuablox Audio.


And thanks for that Note that may be why I was unsuccessful in the past 
with certain pass through combinations.


This isn't relevant?
https://www.virtualbox.org/ticket/20176


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.18 nested vms

[russell]

Hi

Upon further investigation it is not the CPU or bios settings as 
hardware virtualisation is enabled it appears that while VirtualBox 
provide an environment  to install ESX 6.7.0u3 (which works with AMD 
virtualisation) it does not expose enough functionality for the ESX 
instance to run a VM. At the office I have access to a Dual AMD Epyc 
7302 server running ESX 6.7.0u3 and have run ESX 6.7.0 instances as VMs 
without a problem. The key Virtualisation difference between Epyc 7302 
and Ryzen 5600 is the Secure Memory encryption (encrypt all memory with 
a common key when enabled in the bios is transparent to any operating 
system) and Secure Encrypted Virtualisation (encrypt each VM with its 
own key).


The basic AMD-V while used by VirtualBox it does not appear to be 
exposed within the virtual machine so that ESX can use it.


Thanks

Russell


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.18 nested vms

[Chris]

On 2021-04-27 08:32, L. F. Elia via openindiana-discuss wrote:
From what I recall, nested virtualization might require BIOS changes (at 
least on DELL). Good luck!


lfe...@yahoo.com, Portsmouth VA, 23701
Solaris/LINUX/Windows administration CISSP/Security consulting

On Thursday, April 1, 2021, 07:16:20 AM EDT, russell
 wrote:

 Hi

For what I have read VirtualBox 6.1 introduced the capability to have
nested VMs.

I have created a VM to run VMware 6.7.0u3, however when I attempt to
start any VM inside ESX 6.7.0u3 I get the following message

Failed to power on virtual machine Lethe. This host does not support
"AMD RVI" hardware assisted MMU virtualization. Click here for more
details.

While I haven't examined the specs for your specific version of the AMD CPU.
You won't get the information you desire from the VM. What you're really 
after
is what the VM HOST provides. I think your best bet is to have a look at 
dmesg

specifically dmesg.boot. It's the messages generated during boot. In FreeBSD
parlance; dmesg -a would give it to you, as would; less /var/run/dmesg.boot 
--

Sorry, I don't have my OI box handy to give you the exact incantation for OI.
Another thing to have a peek at is within your BOIS. You will need to be sure
you have VM option(s) enabled in order to expose them to the host OS.

HTH

--Chris


-

Looking at the log for the VBox VM

00:00:00.812397 Ext Name:    AuthenticAMD
00:00:00.812398 Ext Supports: 0x8000-0x801e
00:00:00.812398 Family:  15      Extended: 10
     Effective: 25
00:00:00.812398 Model:   1      Extended: 2    
Effective: 33
00:00:00.812399 Stepping:    0
00:00:00.812399 Brand ID:    0x000
00:00:00.812399 Ext Features
00:00:00.812399   Mnemonic -
Description  = guest (host)
00:00:00.812400   FPU - x87 FPU on
Chip   = 1 (1)
00:00:00.812400   VME - *Virtual 8086 Mode Enhancements* = 1 (1)
00:00:00.812401   DE - Debugging
extensions   = 1 (1)
00:00:00.812401   PSE - Page Size
Extension   = 1 (1)
00:00:00.812402   TSC - Time Stamp
Counter    = 1 (1)
00:00:00.812403   MSR - K86 Model Specific
Registers  = 1 (1)
00:00:00.812403   PAE - Physical Address
Extension    = 1 (1)
00:00:00.812404   MCE - Machine Check
Exception   = 0 (1)
00:00:00.812404   CX8 - CMPXCHG8B
instruction = 1 (1)
00:00:00.812405   APIC - APIC
On-Chip = 1 (1)
00:00:00.812405   SEP -
SYSCALL/SYSRET    = 1 (1)
00:00:00.812406   MTRR - Memory Type Range
Registers  = 1 (1)
00:00:00.812406   PGE - PTE Global
Bit    = 1 (1)
00:00:00.812407   MCA - Machine Check
Architecture    = 1 (1)
00:00:00.812407   CMOV - Conditional Move
instructions    = 1 (1)
00:00:00.812408   PAT - Page Attribute
Table  = 1 (1)
00:00:00.812408   PSE-36 - 36-bit Page Size
Extension = 1 (1)
00:00:00.812409   NX -
No-Execute/Execute-Disable = 1 (1)
00:00:00.812409   AXMMX - AMD Extensions to MMX
instructions  = 1 (1)
00:00:00.812410   MMX - Intel MMX
Technology  = 1 (1)
00:00:00.812410   FXSR - FXSAVE and FXRSTOR
Instructions  = 1 (1)
00:00:00.812411   FFXSR - AMD fast FXSAVE and FXRSTOR
instructions    = 1 (1)
00:00:00.812411   Page1GB - 1 GB large
page   = 0 (1)
00:00:00.812412   RDTSCP - RDTSCP
instruction = 1 (1)
00:00:00.812413   LM - AMD64 Long
Mode    = 1 (1)
00:00:00.812413   3DNOWEXT - AMD Extensions to
3DNow  = 0 (0)
00:00:00.812414   3DNOW - AMD
3DNow   = 0 (0)
00:00:00.812415   LahfSahf - LAHF/SAHF support in 64-bit
mode = 1 (1)
00:00:00.812415   CmpLegacy - Core multi-processing legacy
mode   = 1 (1)
00:00:00.812416 *SVM - AMD Secure Virtual Machine extensions* = 1 (1)
00:00:00.812416   EXTAPIC - AMD Extended APIC
registers   = 0 (1)
00:00:00.812417   CR8L - AMD LOCK MOV CR0 means MOV
CR8   = 1 (1)
00:00:00.812417   ABM - AMD Advanced Bit
Manipulation = 1 (1)
00:00:00.812418   SSE4A - SSE4A
instructions  = 1 (1)
00:00:00.812418   MISALIGNSSE - AMD Misaligned SSE
mode   = 1 (1)
00:00:00.812419   3DNOWPRF - AMD PREFETCH and PREFETCHW
instructions  = 1 (1)
00:00:00.812419   OSVW - AMD OS Visible
Workaround    = 0 (1)

Re: [OpenIndiana-discuss] VirtualBox 6.1.18 nested vms

[L. F. Elia via openindiana-discuss]

From what I recall, nested virtualization might require BIOS changes (at least 
on DELL). Good luck!

lfe...@yahoo.com, Portsmouth VA, 23701
Solaris/LINUX/Windows administration CISSP/Security consulting 

On Thursday, April 1, 2021, 07:16:20 AM EDT, russell 
 wrote:  
 
 Hi

For what I have read VirtualBox 6.1 introduced the capability to have 
nested VMs.

I have created a VM to run VMware 6.7.0u3, however when I attempt to 
start any VM inside ESX 6.7.0u3 I get the following message

Failed to power on virtual machine Lethe. This host does not support 
"AMD RVI" hardware assisted MMU virtualization. Click here for more 
details. 

 
-

Looking at the log for the VBox VM

00:00:00.812397 Ext Name:    AuthenticAMD
00:00:00.812398 Ext Supports: 0x8000-0x801e
00:00:00.812398 Family:  15      Extended: 10 
     Effective: 25
00:00:00.812398 Model:   1      Extended: 2     
Effective: 33
00:00:00.812399 Stepping:    0
00:00:00.812399 Brand ID:    0x000
00:00:00.812399 Ext Features
00:00:00.812399   Mnemonic - 
Description  = guest (host)
00:00:00.812400   FPU - x87 FPU on 
Chip   = 1 (1)
00:00:00.812400   VME - *Virtual 8086 Mode Enhancements* = 1 (1)
00:00:00.812401   DE - Debugging 
extensions   = 1 (1)
00:00:00.812401   PSE - Page Size 
Extension   = 1 (1)
00:00:00.812402   TSC - Time Stamp 
Counter    = 1 (1)
00:00:00.812403   MSR - K86 Model Specific 
Registers  = 1 (1)
00:00:00.812403   PAE - Physical Address 
Extension    = 1 (1)
00:00:00.812404   MCE - Machine Check 
Exception   = 0 (1)
00:00:00.812404   CX8 - CMPXCHG8B 
instruction = 1 (1)
00:00:00.812405   APIC - APIC 
On-Chip = 1 (1)
00:00:00.812405   SEP - 
SYSCALL/SYSRET    = 1 (1)
00:00:00.812406   MTRR - Memory Type Range 
Registers  = 1 (1)
00:00:00.812406   PGE - PTE Global 
Bit    = 1 (1)
00:00:00.812407   MCA - Machine Check 
Architecture    = 1 (1)
00:00:00.812407   CMOV - Conditional Move 
instructions    = 1 (1)
00:00:00.812408   PAT - Page Attribute 
Table  = 1 (1)
00:00:00.812408   PSE-36 - 36-bit Page Size 
Extension = 1 (1)
00:00:00.812409   NX - 
No-Execute/Execute-Disable = 1 (1)
00:00:00.812409   AXMMX - AMD Extensions to MMX 
instructions  = 1 (1)
00:00:00.812410   MMX - Intel MMX 
Technology  = 1 (1)
00:00:00.812410   FXSR - FXSAVE and FXRSTOR 
Instructions  = 1 (1)
00:00:00.812411   FFXSR - AMD fast FXSAVE and FXRSTOR 
instructions    = 1 (1)
00:00:00.812411   Page1GB - 1 GB large 
page   = 0 (1)
00:00:00.812412   RDTSCP - RDTSCP 
instruction = 1 (1)
00:00:00.812413   LM - AMD64 Long 
Mode    = 1 (1)
00:00:00.812413   3DNOWEXT - AMD Extensions to 
3DNow  = 0 (0)
00:00:00.812414   3DNOW - AMD 
3DNow   = 0 (0)
00:00:00.812415   LahfSahf - LAHF/SAHF support in 64-bit 
mode = 1 (1)
00:00:00.812415   CmpLegacy - Core multi-processing legacy 
mode   = 1 (1)
00:00:00.812416 *SVM - AMD Secure Virtual Machine extensions* = 1 (1)
00:00:00.812416   EXTAPIC - AMD Extended APIC 
registers   = 0 (1)
00:00:00.812417   CR8L - AMD LOCK MOV CR0 means MOV 
CR8   = 1 (1)
00:00:00.812417   ABM - AMD Advanced Bit 
Manipulation = 1 (1)
00:00:00.812418   SSE4A - SSE4A 
instructions  = 1 (1)
00:00:00.812418   MISALIGNSSE - AMD Misaligned SSE 
mode   = 1 (1)
00:00:00.812419   3DNOWPRF - AMD PREFETCH and PREFETCHW 
instructions  = 1 (1)
00:00:00.812419   OSVW - AMD OS Visible 
Workaround    = 0 (1)
00:00:00.812420   IBS - Instruct Based 
Sampling   = 0 (1)
00:00:00.812420   XOP - Extended Operation 
support    = 0 (0)
00:00:00.812421   SKINIT - SKINIT, STGI, and DEV 
support  = 0 (1)
00:00:00.812421   WDT - AMD Watchdog Timer 
support    = 0 (1)
00:00:00.812422   LWP - Lightweight Profiling 
support = 0 (0)
00:00:00.812422   FMA4 - Four operand FMA instruction 
support = 0 (0)
00:00:00.812423   17 - 
Reserved   = 0 (1)
00:00:00.812423   NodeId - NodeId in MSR 
C001_100C  

Re: [OpenIndiana-discuss] Virtualbox and USB webcam

[Till Wegmueller]

Hey Tony

Here in the EU I always get myself a USB Gaming Headset for my Audio 
needs. They are Cheap(ish) and you can get yourself a Wireless Headset 
that has a dedicated receiver that needs no special driver, other than 
Audio. You might also get away by simply using the Mic, Headset on the 
host and using Virtuablox Audio.


And thanks for that Note that may be why I was unsuccessful in the past 
with certain pass through combinations.


-Till

On 08.01.21 05:09, Tony Brian Albers wrote:

Hi Till,

Thanks a lot for your reply.

Well, it wasn't a kernel driver hogging the device. I could modunload
the usbvc driver easily, but when I tried to attach the device in vbox,
the kernel loaded the usbvc driver automagically again.

But you did actually point me in the right direction, this post helped:

https://forums.virtualbox.org/viewtopic.php?t=87398#p475462

### THE IMPORTANT PART ###
It seems that you need to make sure that the USB device goes into a USB
port that matches the device's type (USB 2, 3 etc.) and then make sure
that your USB controller type configuration of the VM matches the
physical port you're trying to pass through.
### END OF THE IMPORTANT PART"

So when I attached the webcam to a USB 2.0 port, there was a bit more
stuff logged in /var/adm/messages. Then I selected
"USB 2.0 (OHCI + EHCI) Controller"
in vbox settings(USB for the VM), and suddenly it works!

Next challenge is to get the mic working. And since I don't have an
external mic that might prove a bit difficult :)

And of course my old(ish) PC doesn't have a headset port, but separate
headphones/mic ports.

/tony



On 01/07/21 10:30 PM, Till Wegmueller wrote:

Hey Tony

That sounds to me like the a kernel driver is attaching to the device
and thus Virtualbox cannot do that anymore.

There is a blacklisting capability but I have never done that or know
how exactly that works, or if it helps in this situation.

It should be comparable to bhyve passthrough setups where a Host OS
driver already attaches. And I know there are guides there for that. but
you might ask best on IRC about specifically Virtualbox passthrough. As
we have new facilities to achieve such a passthrough.

I also remember this issue being solved once before. So you may also
want to search the archives.

-Till

On 07.01.21 11:53, Tony Brian Albers wrote:

Hi guys,

I'm trying to get my webcam to work in a vbox guest (to use zoom), but
even though it seems to be present in the VM, cheese, zoom and qv4l2
only shows a blank screen. The video device is there though.

On the host I see:

messages:Jan  7 15:46:00 emu usba: [ID 691482 kern.warning] WARNING:
/pci@0,0/pci1028,546@14 (xhci0): usb_mid2 cannot be reset due to other
applications are using it, please first close these applications, then
disconnect and reconnectthe device.

In /var/adm/messages.

I'm using virtualbox 6.1.16 r140961 with the extension pack of the same
version and guest additions. I use the webcam passthrough option under
"Devices".

The guest is SolydX64 (debian respin)

Does anyone have any ideas? I haven't been able to find any info about
this specific issue.

TIA

/tony




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





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

Re: [OpenIndiana-discuss] Virtualbox and USB webcam

[Tony Brian Albers]

Hi Till,

Thanks a lot for your reply.

Well, it wasn't a kernel driver hogging the device. I could modunload 
the usbvc driver easily, but when I tried to attach the device in vbox, 
the kernel loaded the usbvc driver automagically again.

But you did actually point me in the right direction, this post helped:

https://forums.virtualbox.org/viewtopic.php?t=87398#p475462

### THE IMPORTANT PART ###
It seems that you need to make sure that the USB device goes into a USB 
port that matches the device's type (USB 2, 3 etc.) and then make sure 
that your USB controller type configuration of the VM matches the 
physical port you're trying to pass through.
### END OF THE IMPORTANT PART"

So when I attached the webcam to a USB 2.0 port, there was a bit more 
stuff logged in /var/adm/messages. Then I selected
"USB 2.0 (OHCI + EHCI) Controller"
in vbox settings(USB for the VM), and suddenly it works!

Next challenge is to get the mic working. And since I don't have an 
external mic that might prove a bit difficult :)

And of course my old(ish) PC doesn't have a headset port, but separate 
headphones/mic ports.

/tony



On 01/07/21 10:30 PM, Till Wegmueller wrote:
> Hey Tony
> 
> That sounds to me like the a kernel driver is attaching to the device 
> and thus Virtualbox cannot do that anymore.
> 
> There is a blacklisting capability but I have never done that or know 
> how exactly that works, or if it helps in this situation.
> 
> It should be comparable to bhyve passthrough setups where a Host OS 
> driver already attaches. And I know there are guides there for that. but 
> you might ask best on IRC about specifically Virtualbox passthrough. As 
> we have new facilities to achieve such a passthrough.
> 
> I also remember this issue being solved once before. So you may also 
> want to search the archives.
> 
> -Till
> 
> On 07.01.21 11:53, Tony Brian Albers wrote:
>> Hi guys,
>>
>> I'm trying to get my webcam to work in a vbox guest (to use zoom), but
>> even though it seems to be present in the VM, cheese, zoom and qv4l2
>> only shows a blank screen. The video device is there though.
>>
>> On the host I see:
>>
>> messages:Jan  7 15:46:00 emu usba: [ID 691482 kern.warning] WARNING:
>> /pci@0,0/pci1028,546@14 (xhci0): usb_mid2 cannot be reset due to other
>> applications are using it, please first close these applications, then
>> disconnect and reconnectthe device.
>>
>> In /var/adm/messages.
>>
>> I'm using virtualbox 6.1.16 r140961 with the extension pack of the same
>> version and guest additions. I use the webcam passthrough option under
>> "Devices".
>>
>> The guest is SolydX64 (debian respin)
>>
>> Does anyone have any ideas? I haven't been able to find any info about
>> this specific issue.
>>
>> TIA
>>
>> /tony
>>
>>
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss


-- 
Tony Albers - Systems Architect - IT Development Royal Danish Library, 
Victor Albecks Vej 1, 8000 Aarhus C, Denmark
Tel: +45 2566 2383 - CVR/SE: 2898 8842 - EAN: 5798000792142

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

Re: [OpenIndiana-discuss] Virtualbox and USB webcam

[Till Wegmueller]

Hey Tony

That sounds to me like the a kernel driver is attaching to the device 
and thus Virtualbox cannot do that anymore.


There is a blacklisting capability but I have never done that or know 
how exactly that works, or if it helps in this situation.


It should be comparable to bhyve passthrough setups where a Host OS 
driver already attaches. And I know there are guides there for that. but 
you might ask best on IRC about specifically Virtualbox passthrough. As 
we have new facilities to achieve such a passthrough.


I also remember this issue being solved once before. So you may also 
want to search the archives.


-Till

On 07.01.21 11:53, Tony Brian Albers wrote:

Hi guys,

I'm trying to get my webcam to work in a vbox guest (to use zoom), but
even though it seems to be present in the VM, cheese, zoom and qv4l2
only shows a blank screen. The video device is there though.

On the host I see:

messages:Jan  7 15:46:00 emu usba: [ID 691482 kern.warning] WARNING:
/pci@0,0/pci1028,546@14 (xhci0): usb_mid2 cannot be reset due to other
applications are using it, please first close these applications, then
disconnect and reconnectthe device.

In /var/adm/messages.

I'm using virtualbox 6.1.16 r140961 with the extension pack of the same
version and guest additions. I use the webcam passthrough option under
"Devices".

The guest is SolydX64 (debian respin)

Does anyone have any ideas? I haven't been able to find any info about
this specific issue.

TIA

/tony




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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16

[Carl Brewer]

On 27/11/2020 6:53 pm, Carl Brewer wrote:

On 27/11/2020 12:01 am, Stephan Althaus wrote:

Hello!

I just did a pkg upgrade,
which included a new QT5 Version 5.12.10

GUI seems is now fine again :-)


Fantastic, will try it now on mine


Yup, fixed.

Awesome :)

Carl


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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16

[Carl Brewer]

On 27/11/2020 12:01 am, Stephan Althaus wrote:

Hello!

I just did a pkg upgrade,
which included a new QT5 Version 5.12.10

GUI seems is now fine again :-)


Fantastic, will try it now on mine

Carl


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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16

[Stephan Althaus]

Hello!

I just did a pkg upgrade,
which included a new QT5 Version 5.12.10

GUI seems is now fine again :-)

$ pkg info qt5
 Name: library/qt5
  Summary: Qt cross-platform application and UI framework
 Category: Desktop (GNOME)/Libraries
    State: Installed
    Publisher: openindiana.org
*  Version: 5.12.10*
   Branch: 2020.0.1.0
   Packaging Date: 23 November 2020 at 21:24:45
Last Install Time:  7 September 2019 at 19:43:17
 Last Update Time: 26 November 2020 at 12:52:34
 Size: 376.61 MB
 FMRI: 
pkg://openindiana.org/library/qt5@5.12.10-2020.0.1.0:20201123T212445Z
   Source URL: 
https://download.qt.io/official_releases/qt/5.12/5.12.10/single/qt-everywhere-src-5.12.10.tar.xz

  Project URL: https://www.qt.io/

Greetings,
Stephan


On 11/05/20 21:45, Stephan Althaus wrote:

Hi Carl!

Thanks for your replay on this.
As you see the weirdness in the gui it seems to be not a local issue 
on my machine - lucky me :-)


I found it best when using full-frame, i could work with no issues 
there - if i start with full screen mode from the start.
Any vm in a window will have issues - win 7/XP and linux, i don't have 
anything else right now.


I have used the VMs in headless mod and VNC connect some time ago,
i will try again as soon as i feel that i have to do so,
but i hope that we can find the root of it.

Is there anything i could provide to debug this?
Is everyone seeing this who uses the gui? (a quick test is zo scroll 
the mouse over the list of installed VMs))



Stephan



On 11/05/20 21:32, Carl Brewer wrote:
I'm seeing similar issues to Stephan, VBox is working, my virtual 
servers are all running (they're all essentially headless, I don't 
use graphics on them).


The VBox GUI is a bit weird, it's not working "properly", without a 
screenshot it's hard to describe. I'm using TightVNV and a VNC 
session, not a directly connected screen to run it too.


This is from a BE I installed 15 minutes ago.

Not sure how best to help sort this one out. It's not directly 
effecting me, my stuff works and I don't need the GUI to have all the 
icons looking right etc, as long as they're workable.


Carl



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




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



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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16

[Stephan Althaus]

Hi Carl!

Thanks for your replay on this.
As you see the weirdness in the gui it seems to be not a local issue on 
my machine - lucky me :-)


I found it best when using full-frame, i could work with no issues there 
- if i start with full screen mode from the start.
Any vm in a window will have issues - win 7/XP and linux, i don't have 
anything else right now.


I have used the VMs in headless mod and VNC connect some time ago,
i will try again as soon as i feel that i have to do so,
but i hope that we can find the root of it.

Is there anything i could provide to debug this?
Is everyone seeing this who uses the gui? (a quick test is zo scroll the 
mouse over the list of installed VMs))



Stephan



On 11/05/20 21:32, Carl Brewer wrote:
I'm seeing similar issues to Stephan, VBox is working, my virtual 
servers are all running (they're all essentially headless, I don't use 
graphics on them).


The VBox GUI is a bit weird, it's not working "properly", without a 
screenshot it's hard to describe. I'm using TightVNV and a VNC 
session, not a directly connected screen to run it too.


This is from a BE I installed 15 minutes ago.

Not sure how best to help sort this one out. It's not directly 
effecting me, my stuff works and I don't need the GUI to have all the 
icons looking right etc, as long as they're workable.


Carl



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




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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16

[Carl Brewer]

I'm seeing similar issues to Stephan, VBox is working, my virtual 
servers are all running (they're all essentially headless, I don't use 
graphics on them).


The VBox GUI is a bit weird, it's not working "properly", without a 
screenshot it's hard to describe. I'm using TightVNV and a VNC session, 
not a directly connected screen to run it too.


This is from a BE I installed 15 minutes ago.

Not sure how best to help sort this one out. It's not directly effecting 
me, my stuff works and I don't need the GUI to have all the icons 
looking right etc, as long as they're workable.


Carl



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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16

[Stephan Althaus]

Hi!

Additional Info:
a BE from 15.09.2020 is working without issues.

What can i do to help locating the root of the issue?

:~$ pkg info virtualbox
 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
    State: Installed
    Publisher: userland
  Version: 6.1.8
   Branch: 2020.0.1.1
   Packaging Date: 18 May 2020 at 09:37:36
Last Install Time:  7 September 2019 at 19:43:17
 Last Update Time: 18 May 2020 at 09:40:21
 Size: 124.20 MB
 FMRI: 
pkg://userland/system/virtualbox@6.1.8-2020.0.1.1:20200518T093736Z
   Source URL: 
http://download.virtualbox.org/virtualbox/6.1.8/VirtualBox-6.1.8.tar.bz2

  Project URL: http://www.virtualbox.org/

:~$ pkg info qt5
 Name: library/qt5
  Summary: Qt cross-platform application and UI framework
 Category: Desktop (GNOME)/Libraries
    State: Installed
    Publisher: openindiana.org
  Version: 5.8.0
   Branch: 2020.0.1.10
   Packaging Date:  2 June 2020 at 13:19:29
Last Install Time:  7 September 2019 at 19:43:17
 Last Update Time: 10 September 2020 at 17:49:16
 Size: 299.38 MB
 FMRI: 
pkg://openindiana.org/library/qt5@5.8.0-2020.0.1.10:20200602T131929Z
   Source URL: 
http://download.qt.io/official_releases/qt/5.8/5.8.0/single/qt-everywhere-opensource-src-5.8.0.tar.gz

  Project URL: https://www.qt.io/

:~$ pkginfo -l NVDAgraphics
   PKGINST:  NVDAgraphics
  NAME:  NVIDIA Graphics System Software
  CATEGORY:  system,graphics
  ARCH:  i386
   VERSION:  440.64,REV=2020.02.21.01.18
   BASEDIR:  /usr
    VENDOR:  NVIDIA Corporation
  DESC:  X and OpenGL Drivers for NVIDIA Quadro graphics
  INSTDATE:  Mar 31 2020 20:54
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
 FILES:  189 installed pathnames
   4 linked files
  42 directories
  11 executables
  289067 blocks used (approx)



On 11/02/20 21:57, Stephan Althaus wrote:

Hi!

Thanks for your input. I updated to NVIDIA 455.38 and made an pkg 
update a few minutes ago,

and i want to share my experience here

I use the vbox gui all the time to use virtualbox.
- At first a very minor thing, but what i see is that the buttons of 
the vm list on the left do not always change the background color - 
some lower part is left unchanged.
- Secondly, if i boot up a XP, Win7, ubuntu vm i cannot see the stars 
of the password that i'm typing.
- In all VMs there is a small rectangle that is not rendered correctly 
(grayed/blued out) - the size looks like the shadow of the status bar, 
just above it. I an other case it was a honrizontal scroll bar above 
the status bar.
- All Ms show severe graphical updating problems - window minimize and 
maximize again 'repairs' it for a moment.

- All VMs have been updated vb additions.


Now i don't think that it has something to do with the video driver of 
the host.
As all problems show up inside of the vbox windows, it is somewhere in 
the graphics stack/subsystem/libs that vbox uses.


Maybe there an issue with QT 5.12 ?

pkg versions below.

Greetings,
Stephan


 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
    State: Installed
    Publisher: openindiana.org
  Version: 6.1.16
   Branch: 2020.0.1.1
   Packaging Date: 30 October 2020 at 13:56:09
Last Install Time:  7 September 2019 at 19:43:17
 Last Update Time: 30 October 2020 at 21:19:24
 Size: 124.50 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.16-2020.0.1.1:20201030T135609Z
   Source URL: 
https://download.virtualbox.org/virtualbox/6.1.16/VirtualBox-6.1.16.tar.bz2

  Project URL: https://www.virtualbox.org/

   PKGINST:  NVDAgraphics
  NAME:  NVIDIA Graphics System Software
  CATEGORY:  system,graphics
  ARCH:  i386
   VERSION:  455.38,REV=2020.10.22.06.07
   BASEDIR:  /usr
    VENDOR:  NVIDIA Corporation
  DESC:  X and OpenGL Drivers for NVIDIA Quadro graphics
  INSTDATE:  Nov 02 2020 18:53
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
 FILES:  189 installed pathnames
   4 linked files
  42 directories
  11 executables
  307070 blocks used (approx)

 Name: library/qt5
  Summary: Qt cross-platform application and UI framework
 Category: Desktop (GNOME)/Libraries
    State: Installed
    Publisher: openindiana.org
  Version: 5.12.9
   Branch: 2020.0.1.0
   Packaging Date: 30 October 2020 at 13:08:26
Last Install Time:  7 September 2019 at 19:43:17
 Last Update Time: 30 October 2020 at 21:19:24
 Size: 376.59 MB
 FMRI: 

Re: [OpenIndiana-discuss] VirtualBox-6.1.16

[Stephan Althaus]

Hi!

Thanks for your input. I updated to NVIDIA 455.38 and made an pkg update 
a few minutes ago,

and i want to share my experience here

I use the vbox gui all the time to use virtualbox.
- At first a very minor thing, but what i see is that the buttons of the 
vm list on the left do not always change the background color - some 
lower part is left unchanged.
- Secondly, if i boot up a XP, Win7, ubuntu vm i cannot see the stars of 
the password that i'm typing.
- In all VMs there is a small rectangle that is not rendered correctly 
(grayed/blued out) - the size looks like the shadow of the status bar, 
just above it. I an other case it was a honrizontal scroll bar above the 
status bar.
- All Ms show severe graphical updating problems - window minimize and 
maximize again 'repairs' it for a moment.

- All VMs have been updated vb additions.


Now i don't think that it has something to do with the video driver of 
the host.
As all problems show up inside of the vbox windows, it is somewhere in 
the graphics stack/subsystem/libs that vbox uses.


Maybe there an issue with QT 5.12 ?

pkg versions below.

Greetings,
Stephan


 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
    State: Installed
    Publisher: openindiana.org
  Version: 6.1.16
   Branch: 2020.0.1.1
   Packaging Date: 30 October 2020 at 13:56:09
Last Install Time:  7 September 2019 at 19:43:17
 Last Update Time: 30 October 2020 at 21:19:24
 Size: 124.50 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.16-2020.0.1.1:20201030T135609Z
   Source URL: 
https://download.virtualbox.org/virtualbox/6.1.16/VirtualBox-6.1.16.tar.bz2

  Project URL: https://www.virtualbox.org/

   PKGINST:  NVDAgraphics
  NAME:  NVIDIA Graphics System Software
  CATEGORY:  system,graphics
  ARCH:  i386
   VERSION:  455.38,REV=2020.10.22.06.07
   BASEDIR:  /usr
    VENDOR:  NVIDIA Corporation
  DESC:  X and OpenGL Drivers for NVIDIA Quadro graphics
  INSTDATE:  Nov 02 2020 18:53
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
 FILES:  189 installed pathnames
   4 linked files
  42 directories
  11 executables
  307070 blocks used (approx)

 Name: library/qt5
  Summary: Qt cross-platform application and UI framework
 Category: Desktop (GNOME)/Libraries
    State: Installed
    Publisher: openindiana.org
  Version: 5.12.9
   Branch: 2020.0.1.0
   Packaging Date: 30 October 2020 at 13:08:26
Last Install Time:  7 September 2019 at 19:43:17
 Last Update Time: 30 October 2020 at 21:19:24
 Size: 376.59 MB
 FMRI: 
pkg://openindiana.org/library/qt5@5.12.9-2020.0.1.0:20201030T130826Z
   Source URL: 
http://download.qt.io/official_releases/qt/5.12/5.12.9/single/qt-everywhere-src-5.12.9.tar.xz

  Project URL: https://www.qt.io/


On 11/02/20 11:07, Predrag Zecevic - Unix Systems Administrator wrote:


On 11/02/20 06:42, Stephan Althaus wrote:

Hi all!

I did an Update 2 days ago, now i notice that my virtualbox 6.1.16  
has graphical issues.


i have installed 6.1.16 guest additions, and after reboot i did no 
see the login screen. After resize of the client window i see it,
but not the typing of the password - i did however succeed in loggin 
into the client (Win 7).

So the refresh ist not triggered or only partially done.
I do see some minor graphical update request in the vb gui, too. I 
can't take a screenshot of that because afer switching to the 
screenshot tool the gui is updated. :-/




Anyone else seeing this?

Nvidia 440.100 driver - worked well until now with vb 6.1.8 with "pkg 
update" from 16.09.2020.


Greetings,
Stephan

Hi Stephan,

have you (after managing to log-in into VM) upgraded VboxAdditions?

I have also VB 6.1.16 and it is not worse then previous version 
(sometimes I have to reboot guest, because seamless mode is not 
working, or because of audio device[s] problems).


Whilst waiting OI to get latest driver, I am using (on OI host) driver 
from NVIDIA site 
https://www.nvidia.com/en-us/drivers/unix/solaris-display-archive/:

:; pkginfo -l NVDAgraphics
   PKGINST:  NVDAgraphics
  NAME:  NVIDIA Graphics System Software
  CATEGORY:  system,graphics
  ARCH:  i386
   VERSION:  455.23.04,REV=2020.09.13.23.47
   BASEDIR:  /usr
    VENDOR:  NVIDIA Corporation
  DESC:  X and OpenGL Drivers for NVIDIA Quadro graphics
  INSTDATE:  Oct 01 2020 13:13
   HOTLINE:  Please contact your local service provider
    STATUS:  completely installed
 FILES:  189 installed pathnames
   4 linked files
  42 directories
  11 executables
  287063 blocks used (approx)

OI was updated on 2020-10-29, at 13:17

Regards.




On 10/20/20 21:52, 

Re: [OpenIndiana-discuss] VirtualBox-6.1.16: new pull request available for testing

[Predrag Zecevic - Unix Systems Administrator]

On 11/02/20 06:42, Stephan Althaus wrote:

Hi all!

I did an Update 2 days ago, now i notice that my virtualbox 6.1.16  has 
graphical issues.


i have installed 6.1.16 guest additions, and after reboot i did no see 
the login screen. After resize of the client window i see it,
but not the typing of the password - i did however succeed in loggin 
into the client (Win 7).

So the refresh ist not triggered or only partially done.
I do see some minor graphical update request in the vb gui, too. I can't 
take a screenshot of that because afer switching to the screenshot tool 
the gui is updated. :-/




Anyone else seeing this?

Nvidia 440.100 driver - worked well until now with vb 6.1.8 with "pkg 
update" from 16.09.2020.


Greetings,
Stephan

Hi Stephan,

have you (after managing to log-in into VM) upgraded VboxAdditions?

I have also VB 6.1.16 and it is not worse then previous version 
(sometimes I have to reboot guest, because seamless mode is not working, 
or because of audio device[s] problems).


Whilst waiting OI to get latest driver, I am using (on OI host) driver 
from NVIDIA site 
https://www.nvidia.com/en-us/drivers/unix/solaris-display-archive/:

:; pkginfo -l NVDAgraphics
   PKGINST:  NVDAgraphics
  NAME:  NVIDIA Graphics System Software
  CATEGORY:  system,graphics
  ARCH:  i386
   VERSION:  455.23.04,REV=2020.09.13.23.47
   BASEDIR:  /usr
VENDOR:  NVIDIA Corporation
  DESC:  X and OpenGL Drivers for NVIDIA Quadro graphics
  INSTDATE:  Oct 01 2020 13:13
   HOTLINE:  Please contact your local service provider
STATUS:  completely installed
 FILES:  189 installed pathnames
   4 linked files
  42 directories
  11 executables
  287063 blocks used (approx)

OI was updated on 2020-10-29, at 13:17

Regards.




On 10/20/20 21:52, Carl Brewer wrote:

On 21/10/2020 6:46 am, Andreas Wacknitz wrote:

Hi folks,

I have created a PR for the latest VB:
https://github.com/OpenIndiana/oi-userland/pull/6181
It needs to be tested before integration :)



I can confirm 6.1.14.1 works :/  I just bumped my server up to it!

carl@hog:~$ pkg info virtualbox
 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
    State: Installed
    Publisher: openindiana.org
  Version: 6.1.14.1
   Branch: 2020.0.1.0
   Packaging Date: 18 October 2020 at 09:28:52 am
Last Install Time: 19 October 2019 at 09:59:18 am
 Last Update Time: 18 October 2020 at 10:32:52 pm
 Size: 124.56 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.14.1-2020.0.1.0:20201018T092852Z 

   Source URL: 
https://download.virtualbox.org/virtualbox/6.1.14/VirtualBox-6.1.14a.tar.bz2 


  Project URL: https://www.virtualbox.org/

carl@hog:~$ VBoxManage list runningvms
"AvPlan Moodle" {bbb6d323-3a6f-4533-8d2a-bcb4ba9b5db1}
"YVA moodle" {c18dcc9e-c72b-4377-a35e-b29c693c66b1}
"tacos" {f0fdd516-7405-4d00-9a89-bf6b27d45642}


Carl


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



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


--
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.zece...@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!

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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16: new pull request available for testing

[Stephan Althaus]

Hi all!

I did an Update 2 days ago, now i notice that my virtualbox 6.1.16  has 
graphical issues.


i have installed 6.1.16 guest additions, and after reboot i did no see 
the login screen. After resize of the client window i see it,
but not the typing of the password - i did however succeed in loggin 
into the client (Win 7).

So the refresh ist not triggered or only partially done.
I do see some minor graphical update request in the vb gui, too. I can't 
take a screenshot of that because afer switching to the screenshot tool 
the gui is updated. :-/




Anyone else seeing this?

Nvidia 440.100 driver - worked well until now with vb 6.1.8 with "pkg 
update" from 16.09.2020.


Greetings,
Stephan



On 10/20/20 21:52, Carl Brewer wrote:

On 21/10/2020 6:46 am, Andreas Wacknitz wrote:

Hi folks,

I have created a PR for the latest VB:
https://github.com/OpenIndiana/oi-userland/pull/6181
It needs to be tested before integration :)



I can confirm 6.1.14.1 works :/  I just bumped my server up to it!

carl@hog:~$ pkg info virtualbox
 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
    State: Installed
    Publisher: openindiana.org
  Version: 6.1.14.1
   Branch: 2020.0.1.0
   Packaging Date: 18 October 2020 at 09:28:52 am
Last Install Time: 19 October 2019 at 09:59:18 am
 Last Update Time: 18 October 2020 at 10:32:52 pm
 Size: 124.56 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.14.1-2020.0.1.0:20201018T092852Z
   Source URL: 
https://download.virtualbox.org/virtualbox/6.1.14/VirtualBox-6.1.14a.tar.bz2

  Project URL: https://www.virtualbox.org/

carl@hog:~$ VBoxManage list runningvms
"AvPlan Moodle" {bbb6d323-3a6f-4533-8d2a-bcb4ba9b5db1}
"YVA moodle" {c18dcc9e-c72b-4377-a35e-b29c693c66b1}
"tacos" {f0fdd516-7405-4d00-9a89-bf6b27d45642}


Carl


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



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

Re: [OpenIndiana-discuss] VirtualBox-6.1.16: new pull request available for testing

[Carl Brewer]

On 21/10/2020 6:46 am, Andreas Wacknitz wrote:

Hi folks,

I have created a PR for the latest VB:
https://github.com/OpenIndiana/oi-userland/pull/6181
It needs to be tested before integration :)



I can confirm 6.1.14.1 works :/  I just bumped my server up to it!

carl@hog:~$ pkg info virtualbox
 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
State: Installed
Publisher: openindiana.org
  Version: 6.1.14.1
   Branch: 2020.0.1.0
   Packaging Date: 18 October 2020 at 09:28:52 am
Last Install Time: 19 October 2019 at 09:59:18 am
 Last Update Time: 18 October 2020 at 10:32:52 pm
 Size: 124.56 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.14.1-2020.0.1.0:20201018T092852Z
   Source URL: 
https://download.virtualbox.org/virtualbox/6.1.14/VirtualBox-6.1.14a.tar.bz2

  Project URL: https://www.virtualbox.org/

carl@hog:~$ VBoxManage list runningvms
"AvPlan Moodle" {bbb6d323-3a6f-4533-8d2a-bcb4ba9b5db1}
"YVA moodle" {c18dcc9e-c72b-4377-a35e-b29c693c66b1}
"tacos" {f0fdd516-7405-4d00-9a89-bf6b27d45642}


Carl


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Espen Martinsen]

> Let me know if you can install this:


$pfexec beadm create -d "test VB 6.1.8" VBtest
p$fexec reboot

uname -a
SunOS esmpc 5.11 illumos-d0b89bad7e i86pc i386 i86pc illumos
$ cat /etc/release
 OpenIndiana Hipster 2020.04 (powered by illumos)
    OpenIndiana Project, part of The Illumos Foundation (C) 2010-2020
    Use is subject to license terms.
   Assembled 03 May 2020

$ isalist
amd64 pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86

$prtdiag -v
System Configuration: LENOVO 24297XG
BIOS Configuration: LENOVO G4ET93WW (2.53 ) 02/22/2013

$pkg list -H virtualbox
system/virtualbox 6.1.6-2020.0.1.1   i--


$pfexec pkg uninstall system/virtualbox

$cd /var/tmp
$pfexec wget 
http://dlc-int.openindiana.org/users/aurelien/virtualbox/virtualbox_6.1.8.p5a

(( $pfexec pkg unset-publisher  "*" openindiana.org (not necessary???)


$pfexec pkg uninstall 
consolidation/userland/userland-incorporation@0.5.11-2020.0.1.12978 
entire@0.5.11-2020.0.1.0
$pfexec pkg install -g virtualbox_6.1.8.p5a virtualbox

$pfexec reboot
$pkg list -H virtualbox
 system/virtualbox (openindiana.org)   6.1.8-2020.0.1.0   
i--


-Quick tst:
   windows10 VM: OK, resizeDsiplay=OK, sound=OK,
   linux: VM: ok, sound ok, resizeDisplay=OK, RDP (remote console =OK
with extensions

-espen Martinsen
Norway








On 5/18/20 4:18 PM, Aurélien Larcher wrote:
> Let me know if you can install this:
>
> http://dlc-int.openindiana.org/users/aurelien/virtualbox/virtualbox_6.1.8.p5a
>
> pfexec pkg install -g virtualbox_6.1.8.p5a virtualbox
>
> (virtualbox-additions also provided for guests)
>
> On Sun, May 17, 2020 at 4:41 PM Carl Brewer  wrote:
>
>> On 17/05/2020 8:00 pm, Aurélien Larcher wrote:
>>
>>> Would you be able to give it shot?
>>> I can assist if there is any problem but currently there is still a lot
>> of
>>> work with the gcc-10 builds and rust/firefox update...
>> I can test, but I don't know how to do a build
>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>


-- 
Mvh
-
Espen Martinsen   Email :  e...@pogostick.net
dtrace -qn's*::ex*:ret*{printf("%d %s\n",uid,curpsinfo->pr_psargs);}'
-

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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Aurélien Larcher]

Let me know if you can install this:

http://dlc-int.openindiana.org/users/aurelien/virtualbox/virtualbox_6.1.8.p5a

pfexec pkg install -g virtualbox_6.1.8.p5a virtualbox

(virtualbox-additions also provided for guests)

On Sun, May 17, 2020 at 4:41 PM Carl Brewer  wrote:

> On 17/05/2020 8:00 pm, Aurélien Larcher wrote:
>
> > Would you be able to give it shot?
> > I can assist if there is any problem but currently there is still a lot
> of
> > work with the gcc-10 builds and rust/firefox update...
>
> I can test, but I don't know how to do a build
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Aurélien Larcher]

On Mon, May 18, 2020 at 12:03 PM Stephan Althaus <
stephan.alth...@duedinghausen.eu> wrote:

> Hello!
>
> I build and installed VB 6.1.8 in to a new BW, got some errors on startup.
> Patch #18 ist no more needed. Makefile ist attached.
>
> $ svcs -xv
> svc:/application/virtualbox/vboxservice:default (VirtualBox Service.)
>   State: maintenance since 18 May 2020 at 11:44:26 CEST
> Reason: Start method failed repeatedly, last exited with status 1.
> See: http://illumos.org/msg/SMF-8000-KS
> See: /var/svc/log/application-virtualbox-vboxservice:default.log
> Impact: This service is not running.
>
> svc:/application/virtualbox/vboxmslnk:default (VirtualBox Mouse module
> link.)
>   State: maintenance since 18 May 2020 at 11:44:26 CEST
> Reason: Start method failed repeatedly, last exited with status 1.
> See: http://illumos.org/msg/SMF-8000-KS
> See: /var/svc/log/application-virtualbox-vboxmslnk:default.log
> Impact: This service is not running.
> steven@dell6510:~$ cat
> /var/svc/log/application-virtualbox-vboxservice:default.log
> [ May 18 11:44:25 Enabled. ]
> [ May 18 11:44:25 Rereading configuration. ]
> [ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
> VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
> VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
> VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> steven@dell6510:~$ cat
> /var/svc/log/application-virtualbox-vboxmslnk:default.log
> [ May 18 11:44:25 Enabled. ]
> [ May 18 11:44:25 Rereading configuration. ]
> [ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
> Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
> integration Version 6.1.8
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> Failed to open /dev/vboxms - please make sure that the node exists and that
> you have permission to open it.  The error reported was:
> Invalid argument
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
> Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
> integration Version 6.1.8
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> Failed to open /dev/vboxms - please make sure that the node exists and that
> you have permission to open it.  The error reported was:
> Invalid argument
> [ May 18 11:44:26 Method "start" exited with status 1. ]
> [ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
> Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
> integration Version 6.1.8
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> Failed to open /dev/vboxms - please make sure that the node exists and that
> you have permission to open it.  The error reported was:
> Invalid argument
> [ May 18 11:44:26 Method "start" exited with status 1. ]
>
>
I do not understand... is it in the host or the guest?


>
> Greetings,
> Stephan
>
>
> On 05/17/20 12:00, Aurélien Larcher wrote:
> > On Sun, May 17, 2020 at 11:55 AM Carl Brewer 
> wrote:
> >
> >> On 16/05/2020 10:25 pm, Aurélien Larcher wrote:
> >>> This is now fixed in
> >>>
> >>>
> >>
> https://github.com/illumos/illumos-gate/commit/bd025ac2b6fbfbc59dfc0bd50a0e56dd56de9229
> >>> and will be published to the repository within 1 hour.
> >> Hot on its heels, 6.1.8 has just been released.
> >>
> > Would you be able to give it shot?
> > I can assist if there is any problem but currently there is still a lot
> of
> > work with the gcc-10 builds and rust/firefox update...
> > Thank you :)
> >
> >
> >> ___
> >> openindiana-discuss mailing list
> >> openindiana-discuss@openindiana.org
> >> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>
> >
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Stephan Althaus]

Hello!

I build and installed VB 6.1.8 in to a new BW, got some errors on startup.
Patch #18 ist no more needed. Makefile ist attached.

$ svcs -xv
svc:/application/virtualbox/vboxservice:default (VirtualBox Service.)
 State: maintenance since 18 May 2020 at 11:44:26 CEST
Reason: Start method failed repeatedly, last exited with status 1.
   See: http://illumos.org/msg/SMF-8000-KS
   See: /var/svc/log/application-virtualbox-vboxservice:default.log
Impact: This service is not running.

svc:/application/virtualbox/vboxmslnk:default (VirtualBox Mouse module 
link.)

 State: maintenance since 18 May 2020 at 11:44:26 CEST
Reason: Start method failed repeatedly, last exited with status 1.
   See: http://illumos.org/msg/SMF-8000-KS
   See: /var/svc/log/application-virtualbox-vboxmslnk:default.log
Impact: This service is not running.
steven@dell6510:~$ cat 
/var/svc/log/application-virtualbox-vboxservice:default.log

[ May 18 11:44:25 Enabled. ]
[ May 18 11:44:25 Rereading configuration. ]
[ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ May 18 11:44:26 Method "start" exited with status 1. ]
[ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ May 18 11:44:26 Method "start" exited with status 1. ]
[ May 18 11:44:26 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ May 18 11:44:26 Method "start" exited with status 1. ]
steven@dell6510:~$ cat 
/var/svc/log/application-virtualbox-vboxmslnk:default.log

[ May 18 11:44:25 Enabled. ]
[ May 18 11:44:25 Rereading configuration. ]
[ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
integration Version 6.1.8
(C) 2020 Oracle Corporation
All rights reserved.

Failed to open /dev/vboxms - please make sure that the node exists and that
you have permission to open it.  The error reported was:
Invalid argument
[ May 18 11:44:26 Method "start" exited with status 1. ]
[ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
integration Version 6.1.8
(C) 2020 Oracle Corporation
All rights reserved.

Failed to open /dev/vboxms - please make sure that the node exists and that
you have permission to open it.  The error reported was:
Invalid argument
[ May 18 11:44:26 Method "start" exited with status 1. ]
[ May 18 11:44:26 Executing start method ("/usr/sbin/vboxmslnk"). ]
Oracle VM VirtualBox Guest Additions enabling utility for Solaris pointer
integration Version 6.1.8
(C) 2020 Oracle Corporation
All rights reserved.

Failed to open /dev/vboxms - please make sure that the node exists and that
you have permission to open it.  The error reported was:
Invalid argument
[ May 18 11:44:26 Method "start" exited with status 1. ]


Greetings,
Stephan


On 05/17/20 12:00, Aurélien Larcher wrote:

On Sun, May 17, 2020 at 11:55 AM Carl Brewer  wrote:


On 16/05/2020 10:25 pm, Aurélien Larcher wrote:

This is now fixed in



https://github.com/illumos/illumos-gate/commit/bd025ac2b6fbfbc59dfc0bd50a0e56dd56de9229

and will be published to the repository within 1 hour.

Hot on its heels, 6.1.8 has just been released.


Would you be able to give it shot?
I can assist if there is any problem but currently there is still a lot of
work with the gcc-10 builds and rust/firefox update...
Thank you :)



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





#
# This file and its contents are supplied under the terms of the
# Common Development and Distribution License ("CDDL"). You may
# only use this file in accordance with the terms of the CDDL.
#
# A full copy of the text of the CDDL should have accompanied this
# source. A copy of the CDDL is also available via the Internet at
# http://www.illumos.org/license/CDDL.
#

#
# Copyright 2017 Aurelien Larcher
# Copyright 2020 Michal Nowak
# Copyright 2019 Tim Mooney
#

include ../../../make-rules/shared-macros.mk

COMPONENT_NAME= VirtualBox
COMPONENT_VERSION=  6.1.8
COMPONENT_REVISION= 1
COMPONENT_SUMMARY=  VirtualBox - general-purpose full virtualizer
COMPONENT_PROJECT_URL=  http://www.virtualbox.org/
COMPONENT_FMRI= system/virtualbox
COMPONENT_CLASSIFICATION= System/Virtualization
COMPONENT_SRC=  $(COMPONENT_NAME)-$(COMPONENT_VERSION)
COMPONENT_ARCHIVE=  $(COMPONENT_SRC).tar.bz2
COMPONENT_DOWNLOAD_URL= \
http://download.virtualbox.org/virtualbox/$(COMPONENT_VERSION)
COMPONENT_ARCHIVE_URL=  $(COMPONENT_DOWNLOAD_URL)/$(COMPONENT_ARCHIVE)
COMPONENT_ARCHIVE_HASH= \
sha256:426888f83036b6b1f79c272d317a4e8ecf43781f6a266fd7209c03dca504eefc
COMPONENT_LICENSE=  GPLv2

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Carl Brewer]

On 17/05/2020 8:00 pm, Aurélien Larcher wrote:


Would you be able to give it shot?
I can assist if there is any problem but currently there is still a lot of
work with the gcc-10 builds and rust/firefox update...


I can test, but I don't know how to do a build


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Aurélien Larcher]

On Sun, May 17, 2020 at 11:55 AM Carl Brewer  wrote:

> On 16/05/2020 10:25 pm, Aurélien Larcher wrote:
> > This is now fixed in
> >
> >
> https://github.com/illumos/illumos-gate/commit/bd025ac2b6fbfbc59dfc0bd50a0e56dd56de9229
> >
> > and will be published to the repository within 1 hour.
>
> Hot on its heels, 6.1.8 has just been released.
>

Would you be able to give it shot?
I can assist if there is any problem but currently there is still a lot of
work with the gcc-10 builds and rust/firefox update...
Thank you :)


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


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Carl Brewer]

On 16/05/2020 10:25 pm, Aurélien Larcher wrote:

This is now fixed in

https://github.com/illumos/illumos-gate/commit/bd025ac2b6fbfbc59dfc0bd50a0e56dd56de9229

and will be published to the repository within 1 hour.


Hot on its heels, 6.1.8 has just been released.


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Aurélien Larcher]

This is now fixed in

https://github.com/illumos/illumos-gate/commit/bd025ac2b6fbfbc59dfc0bd50a0e56dd56de9229

and will be published to the repository within 1 hour.

On Fri, May 15, 2020 at 4:32 PM Aurélien Larcher 
wrote:

> I have forwarded to the illumos-dev mailing list since a recent change in
> illumos involved mac_hcksum_set and mac_hcksum_get.
>
> Kind regards,
>
> Aurélien
>
> On Fri, May 15, 2020 at 4:05 PM russell 
> wrote:
>
>> Hi
>>
>> Just performed a "pkg update -v --be-name oihipster-20200515" and upon
>> reboot, the following errors were reported
>>
>> May 15 14:57:48 tesla pseudo: [ID 129642 kern.info] pseudo-device:
>> vboxusbmon0
>> May 15 14:57:48 tesla genunix: [ID 936769 kern.info] vboxusbmon0 is
>> /pseudo/vboxusbmon@0
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /kernel/misc/amd64/gld: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'mac_hcksum_set'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /kernel/misc/amd64/gld: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'mac_hcksum_get'
>> May 15 14:57:49 tesla genunix: [ID 472681 kern.notice] WARNING:
>> mod_load: cannot load module 'gld'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_mac_free'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_open'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_rsrv'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_wput'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_wsrv'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_mac_alloc'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_unregister'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_close'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_linkstate'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_register'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_getinfo'
>> May 15 14:57:49 tesla genunix: [ID 472681 kern.notice] WARNING:
>> mod_load: cannot load module 'vboxnet'
>> May 15 14:57:49 tesla genunix: [ID 749970 kern.notice] WARNING: vboxnet:
>> May 15 14:57:49 tesla genunix: [ID 225575 kern.notice] unable to resolve
>> dependency, module 'misc/gld' not found
>> May 15 14:57:49 tesla pseudo: [ID 129642 kern.info] pseudo-device:
>> vboxdrv0
>> May 15 14:57:49 tesla genunix: [ID 936769 kern.info] vboxdrv0 is
>> /pseudo/vboxdrv@0
>>
>> Virtual machines do start but immediately fail.
>>
>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
> --
> ---
> Praise the Caffeine embeddings
>


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Aurélien Larcher]

A fix was proposed by Robert Mustacchi: I am rebuilding now and if it
addresses the issue we'll push soonest.

On Fri, May 15, 2020 at 4:32 PM Aurélien Larcher 
wrote:

> I have forwarded to the illumos-dev mailing list since a recent change in
> illumos involved mac_hcksum_set and mac_hcksum_get.
>
> Kind regards,
>
> Aurélien
>
> On Fri, May 15, 2020 at 4:05 PM russell 
> wrote:
>
>> Hi
>>
>> Just performed a "pkg update -v --be-name oihipster-20200515" and upon
>> reboot, the following errors were reported
>>
>> May 15 14:57:48 tesla pseudo: [ID 129642 kern.info] pseudo-device:
>> vboxusbmon0
>> May 15 14:57:48 tesla genunix: [ID 936769 kern.info] vboxusbmon0 is
>> /pseudo/vboxusbmon@0
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /kernel/misc/amd64/gld: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'mac_hcksum_set'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /kernel/misc/amd64/gld: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'mac_hcksum_get'
>> May 15 14:57:49 tesla genunix: [ID 472681 kern.notice] WARNING:
>> mod_load: cannot load module 'gld'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_mac_free'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_open'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_rsrv'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_wput'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_wsrv'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_mac_alloc'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_unregister'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_close'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_linkstate'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_register'
>> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
>> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
>> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_getinfo'
>> May 15 14:57:49 tesla genunix: [ID 472681 kern.notice] WARNING:
>> mod_load: cannot load module 'vboxnet'
>> May 15 14:57:49 tesla genunix: [ID 749970 kern.notice] WARNING: vboxnet:
>> May 15 14:57:49 tesla genunix: [ID 225575 kern.notice] unable to resolve
>> dependency, module 'misc/gld' not found
>> May 15 14:57:49 tesla pseudo: [ID 129642 kern.info] pseudo-device:
>> vboxdrv0
>> May 15 14:57:49 tesla genunix: [ID 936769 kern.info] vboxdrv0 is
>> /pseudo/vboxdrv@0
>>
>> Virtual machines do start but immediately fail.
>>
>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
> --
> ---
> Praise the Caffeine embeddings
>


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 errors after OI Hipster upgrade

[Aurélien Larcher]

I have forwarded to the illumos-dev mailing list since a recent change in
illumos involved mac_hcksum_set and mac_hcksum_get.

Kind regards,

Aurélien

On Fri, May 15, 2020 at 4:05 PM russell  wrote:

> Hi
>
> Just performed a "pkg update -v --be-name oihipster-20200515" and upon
> reboot, the following errors were reported
>
> May 15 14:57:48 tesla pseudo: [ID 129642 kern.info] pseudo-device:
> vboxusbmon0
> May 15 14:57:48 tesla genunix: [ID 936769 kern.info] vboxusbmon0 is
> /pseudo/vboxusbmon@0
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /kernel/misc/amd64/gld: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'mac_hcksum_set'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /kernel/misc/amd64/gld: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'mac_hcksum_get'
> May 15 14:57:49 tesla genunix: [ID 472681 kern.notice] WARNING:
> mod_load: cannot load module 'gld'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_mac_free'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_open'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_rsrv'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_wput'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice]  'gld_wsrv'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_mac_alloc'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_unregister'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_close'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_linkstate'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_register'
> May 15 14:57:49 tesla genunix: [ID 819705 kern.notice]
> /platform/i86pc/kernel/drv/amd64/vboxnet: undefined symbol
> May 15 14:57:49 tesla genunix: [ID 826211 kern.notice] 'gld_getinfo'
> May 15 14:57:49 tesla genunix: [ID 472681 kern.notice] WARNING:
> mod_load: cannot load module 'vboxnet'
> May 15 14:57:49 tesla genunix: [ID 749970 kern.notice] WARNING: vboxnet:
> May 15 14:57:49 tesla genunix: [ID 225575 kern.notice] unable to resolve
> dependency, module 'misc/gld' not found
> May 15 14:57:49 tesla pseudo: [ID 129642 kern.info] pseudo-device:
> vboxdrv0
> May 15 14:57:49 tesla genunix: [ID 936769 kern.info] vboxdrv0 is
> /pseudo/vboxdrv@0
>
> Virtual machines do start but immediately fail.
>
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>


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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd May 2020 - update

[russell]

Hi

I can also report that    "modinfo | grep vm " does not return any 
module information



On 06/05/2020 22:19, russell wrote:


Hi

I have tried to start an existing VM using the cli command 
"/opt/VirtualBox/amd64VirtualBoxVM --startvm toucan" to start the 
toucan VM but this results in the following error


VirtualBox can't enable the AMD-V extension. Please close all other 
virtualization programs. (VERR_SVM_IN_USE).



Result Code:



NS_ERROR_FAILURE (0x80004005)

Component:



ConsoleWrap

Interface:



IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

No problems when I revert to previous BE.



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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd May 2020

[Stephan Althaus]

Hello!

Try this to see which vm modules are loaded:

modinfo | grep vm

Greetings,
Stephan

On 05/07/20 19:08, Apostolos Syropoulos via openindiana-discuss wrote:

still I see the same error message!

Στάλθηκε από το Ταχυδρομείο Yahoo σε Android
  
   Στις Πέμ, 7 Μαΐ, 2020 στις 3:15, ο χρήστηςAlexander Pyhalov έγραψε:   Yes.

https://github.com/OpenIndiana/oi-userland/commit/6ffaf19da9dfe774caf13b7409f0a59a994f4f6f

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



От: Till Wegmüller 
Отправлено: 7 мая 2020 г. 1:04
Кому: Alexander Pyhalov via openindiana-discuss
Тема: Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 
3rd May 2020

Did we import the mandatory Virtualbox Patch yet? Since a few days the
illumos kernel initialises hma_vmx for bHyve and kvm, Virtualbox needs a
patch otherwise this will occur.


-Till

On 06.05.20 21:01, Alexander Pyhalov via openindiana-discuss wrote:

Hi.
Do you have KVM VMs running?
Are there any errors in /var/adm/messages regarding hma_vmx_init?

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



От: russell 
Отправлено: 6 мая 2020 г. 21:13
Кому: Discussion list for OpenIndiana
Тема: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd 
May 2020

Hi

Just upgraded to latest OpenIndiana Hipster release this evening and now
when I attempt to start VirtualBox I get the following error

VirtualBox can't enable the AMD-V extension. Please close all other
virtualization programs. (VERR_SVM_IN_USE).

Result Code:



NS_ERROR_FAILURE (0x80004005)

Component:



ConsoleWrap

Interface:



IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

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

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


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

openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss




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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd May 2020

[Apostolos Syropoulos via openindiana-discuss]

still I see the same error message!

Στάλθηκε από το Ταχυδρομείο Yahoo σε Android 
 
  Στις Πέμ, 7 Μαΐ, 2020 στις 3:15, ο χρήστηςAlexander Pyhalov 
έγραψε:   Yes.
https://github.com/OpenIndiana/oi-userland/commit/6ffaf19da9dfe774caf13b7409f0a59a994f4f6f

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



От: Till Wegmüller 
Отправлено: 7 мая 2020 г. 1:04
Кому: Alexander Pyhalov via openindiana-discuss
Тема: Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 
3rd May 2020

Did we import the mandatory Virtualbox Patch yet? Since a few days the
illumos kernel initialises hma_vmx for bHyve and kvm, Virtualbox needs a
patch otherwise this will occur.


-Till

On 06.05.20 21:01, Alexander Pyhalov via openindiana-discuss wrote:
> Hi.
> Do you have KVM VMs running?
> Are there any errors in /var/adm/messages regarding hma_vmx_init?
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> 
> От: russell 
> Отправлено: 6 мая 2020 г. 21:13
> Кому: Discussion list for OpenIndiana
> Тема: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd 
> May 2020
>
> Hi
>
> Just upgraded to latest OpenIndiana Hipster release this evening and now
> when I attempt to start VirtualBox I get the following error
>
> VirtualBox can't enable the AMD-V extension. Please close all other
> virtualization programs. (VERR_SVM_IN_USE).
>
> Result Code:
>
>
>
> NS_ERROR_FAILURE (0x80004005)
>
> Component:
>
>
>
> ConsoleWrap
>
> Interface:
>
>
>
> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd May 2020

[Alexander Pyhalov]

Yes.
https://github.com/OpenIndiana/oi-userland/commit/6ffaf19da9dfe774caf13b7409f0a59a994f4f6f

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



От: Till Wegmüller 
Отправлено: 7 мая 2020 г. 1:04
Кому: Alexander Pyhalov via openindiana-discuss
Тема: Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 
3rd May 2020

Did we import the mandatory Virtualbox Patch yet? Since a few days the
illumos kernel initialises hma_vmx for bHyve and kvm, Virtualbox needs a
patch otherwise this will occur.


-Till

On 06.05.20 21:01, Alexander Pyhalov via openindiana-discuss wrote:
> Hi.
> Do you have KVM VMs running?
> Are there any errors in /var/adm/messages regarding hma_vmx_init?
>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> 
> От: russell 
> Отправлено: 6 мая 2020 г. 21:13
> Кому: Discussion list for OpenIndiana
> Тема: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd 
> May 2020
>
> Hi
>
> Just upgraded to latest OpenIndiana Hipster release this evening and now
> when I attempt to start VirtualBox I get the following error
>
> VirtualBox can't enable the AMD-V extension. Please close all other
> virtualization programs. (VERR_SVM_IN_USE).
>
> Result Code:
>
>
>
> NS_ERROR_FAILURE (0x80004005)
>
> Component:
>
>
>
> ConsoleWrap
>
> Interface:
>
>
>
> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>

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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd May 2020

[Till Wegmüller]

Did we import the mandatory Virtualbox Patch yet? Since a few days the
illumos kernel initialises hma_vmx for bHyve and kvm, Virtualbox needs a
patch otherwise this will occur.


-Till

On 06.05.20 21:01, Alexander Pyhalov via openindiana-discuss wrote:
> Hi.
> Do you have KVM VMs running?
> Are there any errors in /var/adm/messages regarding hma_vmx_init?
> 
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
> 
> 
> 
> От: russell 
> Отправлено: 6 мая 2020 г. 21:13
> Кому: Discussion list for OpenIndiana
> Тема: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd 
> May 2020
> 
> Hi
> 
> Just upgraded to latest OpenIndiana Hipster release this evening and now
> when I attempt to start VirtualBox I get the following error
> 
> VirtualBox can't enable the AMD-V extension. Please close all other
> virtualization programs. (VERR_SVM_IN_USE).
> 
> Result Code:
> 
> 
> 
> NS_ERROR_FAILURE (0x80004005)
> 
> Component:
> 
> 
> 
> ConsoleWrap
> 
> Interface:
> 
> 
> 
> IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 

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

Re: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd May 2020

[Alexander Pyhalov via openindiana-discuss]

Hi.
Do you have KVM VMs running?
Are there any errors in /var/adm/messages regarding hma_vmx_init?

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



От: russell 
Отправлено: 6 мая 2020 г. 21:13
Кому: Discussion list for OpenIndiana
Тема: [OpenIndiana-discuss] VirtualBox 6.1.6 on Hipster 2020.04 Assembled 3rd 
May 2020

Hi

Just upgraded to latest OpenIndiana Hipster release this evening and now
when I attempt to start VirtualBox I get the following error

VirtualBox can't enable the AMD-V extension. Please close all other
virtualization programs. (VERR_SVM_IN_USE).

Result Code:



NS_ERROR_FAILURE (0x80004005)

Component:



ConsoleWrap

Interface:



IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

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

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

Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

[Carl Brewer]

FWIW, I'm running 6.1.6 by hand, seems ok.  Not running it from any 
service manager though.


carl@hog:~$ VBoxManage list runningvms
"YVA conf" {8bbc8cba-675e-48aa-955c-48eda9f39cd9}

carl@hog:~$ pkg info virtualbox
 Name: system/virtualbox
  Summary: VirtualBox - general-purpose full virtualizer
 Category: System/Virtualization
State: Installed
Publisher: openindiana.org
  Version: 6.1.6
   Branch: 2020.0.1.0
   Packaging Date: 22 April 2020 at 06:40:43 am
Last Install Time: 19 October 2019 at 09:59:18 am
 Last Update Time: 22 April 2020 at 10:25:31 am
 Size: 124.20 MB
 FMRI: 
pkg://openindiana.org/system/virtualbox@6.1.6-2020.0.1.0:20200422T064043Z

  Project URL: http://www.virtualbox.org/
   Source URL: 
http://download.virtualbox.org/virtualbox/6.1.6/VirtualBox-6.1.6.tar.bz2

carl@hog:~$

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

Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

[Jim Klimov]

On April 30, 2020 1:47:14 PM UTC, Predrag Zecevic 
 wrote:
>On 29.04.2020 17:40, Jack Whitehead wrote:
>> Hi Alex,
>> 
>> Thanks for getting back to me.
>> 
>> I assume there are likely lots of changes being made now for the
>2020.04 
>> update so I have just done another "pkg update" and rebooted.
>> 
>> Then I reinstalled VirtualBox. Now I find that all of the vbox
>services 
>> are disabled initially so I enabled autostart. It failed and entered 
>> maintenance state. See below...
>> 
>> root@cascade:~# pkg install virtualbox
>>     Packages to install:  1
>>      Services to change:  5
>>     Create boot environment: No
>> Create backup boot environment: No
>> 
>> DOWNLOAD    PKGS FILES    XFER 
>> (MB)   SPEED
>> Completed    1/1   173/173 40.7/40.7 
>
>> 1.2M/s
>> 
>> PHASE  ITEMS
>> Installing new actions   219/219
>> Updating package state database Done
>> Updating package cache   0/0
>> Updating image state    Done
>> Creating fast lookup database   Done
>> root@cascade:~# svcs -a | grep virtu
>> disabled    8:54:24
>svc:/application/virtualbox/zoneaccess:default
>> disabled    8:54:24
>svc:/application/virtualbox/balloonctrl:default
>> disabled    8:54:24 svc:/application/virtualbox/autostart:default
>> disabled    8:54:24
>svc:/application/virtualbox/webservice:default
>> online  8:54:34 svc:/application/virtualbox/run-once:default
>> 
>> root@cascade:~# svcadm enable
>svc:/application/virtualbox/autostart:default
>> root@cascade:~# svcs -a | grep virtu
>> disabled    8:54:24
>svc:/application/virtualbox/zoneaccess:default
>> disabled    8:54:24
>svc:/application/virtualbox/balloonctrl:default
>> disabled    8:54:24
>svc:/application/virtualbox/webservice:default
>> online  8:54:34 svc:/application/virtualbox/run-once:default
>> maintenance 8:57:57 svc:/application/virtualbox/autostart:default
>> root@cascade:~# svcs -xv
>> svc:/application/virtualbox/autostart:default (VirtualBox Autostart)
>>   State: maintenance since April 29, 2020 at 08:57:57 AM MDT
>> Reason: Start method failed repeatedly, last exited with status 1.
>>     See: http://illumos.org/msg/SMF-8000-KS
>>     See: /var/svc/log/application-virtualbox-autostart:default.log
>> Impact: This service is not running.
>> 
>>  From the log 
>> (/var/svc/log/application-virtualbox-autostart:default.log) ...
>> 
>> [ Apr 29 08:54:24 Disabled. ]
>> [ Apr 29 08:54:24 Rereading configuration. ]
>> [ Apr 29 08:57:57 Enabled. ]
>> [ Apr 29 08:57:57 Executing start method 
>> ("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
>> The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
>> Oracle VM VirtualBox Autostart 6.1.6
>> (C) 2020 Oracle Corporation
>> All rights reserved.
>> 
>> VBoxAutostart failed with 1.
>> [ Apr 29 08:57:57 Method "start" exited with status 1. ]
>> [ Apr 29 08:57:57 Executing start method 
>> ("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
>> The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
>> Oracle VM VirtualBox Autostart 6.1.6
>> (C) 2020 Oracle Corporation
>> All rights reserved.
>> 
>> VBoxAutostart failed with 1.
>> [ Apr 29 08:57:57 Method "start" exited with status 1. ]
>> [ Apr 29 08:57:57 Executing start method 
>> ("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
>> The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
>> Oracle VM VirtualBox Autostart 6.1.6
>> (C) 2020 Oracle Corporation
>> All rights reserved.
>> 
>> VBoxAutostart failed with 1.
>> 
>> I tried enabling the services that are disabled and here's what I
>got...
>> 
>> root@cascade:~# svcs -a | grep virtu
>> disabled    8:54:24
>svc:/application/virtualbox/zoneaccess:default
>> disabled    8:54:24
>svc:/application/virtualbox/balloonctrl:default
>> disabled    8:54:24
>svc:/application/virtualbox/webservice:default
>> online  8:54:34 svc:/application/virtualbox/run-once:default
>> maintenance 8:57:57 svc:/application/virtualbox/autostart:default
>> root@cascade:~# svcadm enable 
>> svc:/application/virtualbox/zoneaccess:default 
>> svc:/application/virtualbox/balloonctrl:default 
>> svc:/application/virtualbox/webservice:default
>> root@cascade:~# svcs -a | grep virtu
>> online  8:54:34 svc:/application/virtualbox/run-once:default
>> online  9:32:08
>svc:/application/virtualbox/balloonctrl:default
>> online  9:32:08
>svc:/application/virtualbox/webservice:default
>> maintenance 8:57:57 svc:/application/virtualbox/autostart:default
>> maintenance 9:32:08
>svc:/application/virtualbox/zoneaccess:default
>> root@cascade:~# svcadm clear
>svc:/application/virtualbox/autostart:default
>> root@cascade:~# svcadm clear
>svc:/application/virtualbox/zoneaccess:default
>> 

Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

[Jack Whitehead]

I had not tried running autostart from the command line. I just did...

root@cascade:~# /opt/VirtualBox/64/VBoxAutostart --start --config 
/etc/vbox/autostart.conf --logrotate 10 --logsize 104857600 
--loginterval 86400

Oracle VM VirtualBox Autostart 6.1.6
(C) 2020 Oracle Corporation
All rights reserved.

root@cascade:~# ps -ef | grep -i virt
    root   950 1   0 09:59:39 ?   0:01 
/opt/VirtualBox/amd64/VBoxSVC --auto-shutdown

    root  3346  3308   0 10:16:57 pts/2   0:00 grep -i virt
 jcw0624  3342 1   0 10:16:30 ?   0:00 
/opt/VirtualBox/amd64/VBoxSVC --auto-shutdown
    root   942 1   0 09:59:39 ?   0:00 
/opt/VirtualBox/amd64/VBoxXPCOMIPCD
    root  3301 1   0 10:01:33 ?   0:00 
/opt/VirtualBox/64/vboxwebsrv --background --host localhost --port 18083 
--time
 jcw0624  3340 1   0 10:16:30 ?   0:00 
/opt/VirtualBox/amd64/VBoxXPCOMIPCD
 jcw0624  3336  2078   0 10:16:29 ?   0:01 
/opt/VirtualBox/amd64/VirtualBox
    root  3299 1   0 10:01:33 ?   0:00 
/opt/VirtualBox/64/VBoxBalloonCtrl --background

root@cascade:~#

After doing this the VB management GUI has functioning menus; it ran but 
had no menus function when the daemons were down.


/etc/vbox/autostart.conf does not exist on my system.


On 04/30/20 08:20 AM, Alexander Pyhalov wrote:

/opt/VirtualBox/64/VBoxAutostart --start --config /etc/vbox/autostart.conf 
--logrotate 10 --logsize 104857600 --loginterval 86400



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

Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

[Alexander Pyhalov]

As for web service, it's SOAP interface, it's not intended to be used by 
browser directly.

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



От: Predrag Zecevic 
Отправлено: 30 апреля 2020 г. 16:47
Кому: openindiana-discuss@openindiana.org
Тема: Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

On 29.04.2020 17:40, Jack Whitehead wrote:
> Hi Alex,
>
> Thanks for getting back to me.
>
> I assume there are likely lots of changes being made now for the 2020.04
> update so I have just done another "pkg update" and rebooted.
>
> Then I reinstalled VirtualBox. Now I find that all of the vbox services
> are disabled initially so I enabled autostart. It failed and entered
> maintenance state. See below...
>
> root@cascade:~# pkg install virtualbox
> Packages to install:  1
>  Services to change:  5
> Create boot environment: No
> Create backup boot environment: No
>
> DOWNLOADPKGS FILESXFER
> (MB)   SPEED
> Completed1/1   173/173 40.7/40.7
> 1.2M/s
>
> PHASE  ITEMS
> Installing new actions   219/219
> Updating package state database Done
> Updating package cache   0/0
> Updating image stateDone
> Creating fast lookup database   Done
> root@cascade:~# svcs -a | grep virtu
> disabled8:54:24 svc:/application/virtualbox/zoneaccess:default
> disabled8:54:24 svc:/application/virtualbox/balloonctrl:default
> disabled8:54:24 svc:/application/virtualbox/autostart:default
> disabled8:54:24 svc:/application/virtualbox/webservice:default
> online  8:54:34 svc:/application/virtualbox/run-once:default
>
> root@cascade:~# svcadm enable svc:/application/virtualbox/autostart:default
> root@cascade:~# svcs -a | grep virtu
> disabled8:54:24 svc:/application/virtualbox/zoneaccess:default
> disabled8:54:24 svc:/application/virtualbox/balloonctrl:default
> disabled8:54:24 svc:/application/virtualbox/webservice:default
> online  8:54:34 svc:/application/virtualbox/run-once:default
> maintenance 8:57:57 svc:/application/virtualbox/autostart:default
> root@cascade:~# svcs -xv
> svc:/application/virtualbox/autostart:default (VirtualBox Autostart)
>   State: maintenance since April 29, 2020 at 08:57:57 AM MDT
> Reason: Start method failed repeatedly, last exited with status 1.
> See: http://illumos.org/msg/SMF-8000-KS
> See: /var/svc/log/application-virtualbox-autostart:default.log
> Impact: This service is not running.
>
>  From the log
> (/var/svc/log/application-virtualbox-autostart:default.log) ...
>
> [ Apr 29 08:54:24 Disabled. ]
> [ Apr 29 08:54:24 Rereading configuration. ]
> [ Apr 29 08:57:57 Enabled. ]
> [ Apr 29 08:57:57 Executing start method
> ("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
> The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
> Oracle VM VirtualBox Autostart 6.1.6
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> VBoxAutostart failed with 1.
> [ Apr 29 08:57:57 Method "start" exited with status 1. ]
> [ Apr 29 08:57:57 Executing start method
> ("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
> The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
> Oracle VM VirtualBox Autostart 6.1.6
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> VBoxAutostart failed with 1.
> [ Apr 29 08:57:57 Method "start" exited with status 1. ]
> [ Apr 29 08:57:57 Executing start method
> ("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
> The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
> Oracle VM VirtualBox Autostart 6.1.6
> (C) 2020 Oracle Corporation
> All rights reserved.
>
> VBoxAutostart failed with 1.
>
> I tried enabling the services that are disabled and here's what I got...
>
> root@cascade:~# svcs -a | grep virtu
> disabled8:54:24 svc:/application/virtualbox/zoneaccess:default
> disabled8:54:24 svc:/application/virtualbox/balloonctrl:default
> disabled8:54:24 svc:/application/virtualbox/webservice:default
> online  8:54:34 svc:/application/virtualbox/run-once:default
> maintenance 8:57:57 svc:/application/virtualbox/autostart:default
> root@cascade:~# svcadm enable
> svc:/application/virtualbox/zoneaccess:default
> svc:/application/virtualbox/balloonctrl:default
> svc:/applica

Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

[Alexander Pyhalov via openindiana-discuss]

Have you tried running
/opt/VirtualBox/64/VBoxAutostart --start --config /etc/vbox/autostart.conf 
--logrotate 10 --logsize 104857600 --loginterval 86400
manually?

What is the contents of your   /etc/vbox/autostart.conf ?

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



От: Jack Whitehead <8910...@telus.net>
Отправлено: 29 апреля 2020 г. 18:40
Кому: openindiana-discuss@openindiana.org; Alexander Pyhalov
Тема: Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

Hi Alex,

Thanks for getting back to me.

I assume there are likely lots of changes being made now for the 2020.04
update so I have just done another "pkg update" and rebooted.

Then I reinstalled VirtualBox. Now I find that all of the vbox services
are disabled initially so I enabled autostart. It failed and entered
maintenance state. See below...

root@cascade:~# pkg install virtualbox
Packages to install:  1
 Services to change:  5
Create boot environment: No
Create backup boot environment: No

DOWNLOADPKGS FILESXFER
(MB)   SPEED
Completed1/1   173/173 40.7/40.7  1.2M/s

PHASE  ITEMS
Installing new actions   219/219
Updating package state database Done
Updating package cache   0/0
Updating image stateDone
Creating fast lookup database   Done
root@cascade:~# svcs -a | grep virtu
disabled8:54:24 svc:/application/virtualbox/zoneaccess:default
disabled8:54:24 svc:/application/virtualbox/balloonctrl:default
disabled8:54:24 svc:/application/virtualbox/autostart:default
disabled8:54:24 svc:/application/virtualbox/webservice:default
online  8:54:34 svc:/application/virtualbox/run-once:default

root@cascade:~# svcadm enable svc:/application/virtualbox/autostart:default
root@cascade:~# svcs -a | grep virtu
disabled8:54:24 svc:/application/virtualbox/zoneaccess:default
disabled8:54:24 svc:/application/virtualbox/balloonctrl:default
disabled8:54:24 svc:/application/virtualbox/webservice:default
online  8:54:34 svc:/application/virtualbox/run-once:default
maintenance 8:57:57 svc:/application/virtualbox/autostart:default
root@cascade:~# svcs -xv
svc:/application/virtualbox/autostart:default (VirtualBox Autostart)
  State: maintenance since April 29, 2020 at 08:57:57 AM MDT
Reason: Start method failed repeatedly, last exited with status 1.
See: http://illumos.org/msg/SMF-8000-KS
See: /var/svc/log/application-virtualbox-autostart:default.log
Impact: This service is not running.

 From the log
(/var/svc/log/application-virtualbox-autostart:default.log) ...

[ Apr 29 08:54:24 Disabled. ]
[ Apr 29 08:54:24 Rereading configuration. ]
[ Apr 29 08:57:57 Enabled. ]
[ Apr 29 08:57:57 Executing start method
("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
Oracle VM VirtualBox Autostart 6.1.6
(C) 2020 Oracle Corporation
All rights reserved.

VBoxAutostart failed with 1.
[ Apr 29 08:57:57 Method "start" exited with status 1. ]
[ Apr 29 08:57:57 Executing start method
("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
Oracle VM VirtualBox Autostart 6.1.6
(C) 2020 Oracle Corporation
All rights reserved.

VBoxAutostart failed with 1.
[ Apr 29 08:57:57 Method "start" exited with status 1. ]
[ Apr 29 08:57:57 Executing start method
("/opt/VirtualBox/smf-vboxautostart.sh start"). ]
The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
Oracle VM VirtualBox Autostart 6.1.6
(C) 2020 Oracle Corporation
All rights reserved.

VBoxAutostart failed with 1.

I tried enabling the services that are disabled and here's what I got...

root@cascade:~# svcs -a | grep virtu
disabled8:54:24 svc:/application/virtualbox/zoneaccess:default
disabled8:54:24 svc:/application/virtualbox/balloonctrl:default
disabled8:54:24 svc:/application/virtualbox/webservice:default
online  8:54:34 svc:/application/virtualbox/run-once:default
maintenance 8:57:57 svc:/application/virtualbox/autostart:default
root@cascade:~# svcadm enable
svc:/application/virtualbox/zoneaccess:default
svc:/application/virtualbox/balloonctrl:default
svc:/application/virtualbox/webservice:default
root@cascade:~# svcs -a | grep virtu
online  8:54:34 svc:/application/virtualbox/run-once:default
online  9:32:08 svc:/application/virtualbox/balloonctrl:default
online  9:32:08 svc:/application/virtualbox/webservice:default
maintenance 8:57:57 svc:/application/virtualbox/aut

Re: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not

[Predrag Zecevic]

On 29.04.2020 17:40, Jack Whitehead wrote:

Hi Alex,

Thanks for getting back to me.

I assume there are likely lots of changes being made now for the 2020.04 
update so I have just done another "pkg update" and rebooted.


Then I reinstalled VirtualBox. Now I find that all of the vbox services 
are disabled initially so I enabled autostart. It failed and entered 
maintenance state. See below...


root@cascade:~# pkg install virtualbox
    Packages to install:  1
     Services to change:  5
    Create boot environment: No
Create backup boot environment: No

DOWNLOAD    PKGS FILES    XFER 
(MB)   SPEED
Completed    1/1   173/173 40.7/40.7  
1.2M/s


PHASE  ITEMS
Installing new actions   219/219
Updating package state database Done
Updating package cache   0/0
Updating image state    Done
Creating fast lookup database   Done
root@cascade:~# svcs -a | grep virtu
disabled    8:54:24 svc:/application/virtualbox/zoneaccess:default
disabled    8:54:24 svc:/application/virtualbox/balloonctrl:default
disabled    8:54:24 svc:/application/virtualbox/autostart:default
disabled    8:54:24 svc:/application/virtualbox/webservice:default
online  8:54:34 svc:/application/virtualbox/run-once:default

root@cascade:~# svcadm enable svc:/application/virtualbox/autostart:default
root@cascade:~# svcs -a | grep virtu
disabled    8:54:24 svc:/application/virtualbox/zoneaccess:default
disabled    8:54:24 svc:/application/virtualbox/balloonctrl:default
disabled    8:54:24 svc:/application/virtualbox/webservice:default
online  8:54:34 svc:/application/virtualbox/run-once:default
maintenance 8:57:57 svc:/application/virtualbox/autostart:default
root@cascade:~# svcs -xv
svc:/application/virtualbox/autostart:default (VirtualBox Autostart)
  State: maintenance since April 29, 2020 at 08:57:57 AM MDT
Reason: Start method failed repeatedly, last exited with status 1.
    See: http://illumos.org/msg/SMF-8000-KS
    See: /var/svc/log/application-virtualbox-autostart:default.log
Impact: This service is not running.

 From the log 
(/var/svc/log/application-virtualbox-autostart:default.log) ...


[ Apr 29 08:54:24 Disabled. ]
[ Apr 29 08:54:24 Rereading configuration. ]
[ Apr 29 08:57:57 Enabled. ]
[ Apr 29 08:57:57 Executing start method 
("/opt/VirtualBox/smf-vboxautostart.sh start"). ]

The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
Oracle VM VirtualBox Autostart 6.1.6
(C) 2020 Oracle Corporation
All rights reserved.

VBoxAutostart failed with 1.
[ Apr 29 08:57:57 Method "start" exited with status 1. ]
[ Apr 29 08:57:57 Executing start method 
("/opt/VirtualBox/smf-vboxautostart.sh start"). ]

The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
Oracle VM VirtualBox Autostart 6.1.6
(C) 2020 Oracle Corporation
All rights reserved.

VBoxAutostart failed with 1.
[ Apr 29 08:57:57 Method "start" exited with status 1. ]
[ Apr 29 08:57:57 Executing start method 
("/opt/VirtualBox/smf-vboxautostart.sh start"). ]

The Illumos Project SunOS 5.11  illumos-454f0c49f9 April 2020
Oracle VM VirtualBox Autostart 6.1.6
(C) 2020 Oracle Corporation
All rights reserved.

VBoxAutostart failed with 1.

I tried enabling the services that are disabled and here's what I got...

root@cascade:~# svcs -a | grep virtu
disabled    8:54:24 svc:/application/virtualbox/zoneaccess:default
disabled    8:54:24 svc:/application/virtualbox/balloonctrl:default
disabled    8:54:24 svc:/application/virtualbox/webservice:default
online  8:54:34 svc:/application/virtualbox/run-once:default
maintenance 8:57:57 svc:/application/virtualbox/autostart:default
root@cascade:~# svcadm enable 
svc:/application/virtualbox/zoneaccess:default 
svc:/application/virtualbox/balloonctrl:default 
svc:/application/virtualbox/webservice:default

root@cascade:~# svcs -a | grep virtu
online  8:54:34 svc:/application/virtualbox/run-once:default
online  9:32:08 svc:/application/virtualbox/balloonctrl:default
online  9:32:08 svc:/application/virtualbox/webservice:default
maintenance 8:57:57 svc:/application/virtualbox/autostart:default
maintenance 9:32:08 svc:/application/virtualbox/zoneaccess:default
root@cascade:~# svcadm clear svc:/application/virtualbox/autostart:default
root@cascade:~# svcadm clear svc:/application/virtualbox/zoneaccess:default
root@cascade:~# svcs -a | grep virtu
online  8:54:34 svc:/application/virtualbox/run-once:default
online  9:32:08 svc:/application/virtualbox/balloonctrl:default
online  9:32:08 svc:/application/virtualbox/webservice:default
maintenance 9:32:35 svc:/application/virtualbox/autostart:default
maintenance 9:32:54