On April 30, 2020 1:47:14 PM UTC, Predrag Zecevic 
<predrag.zece...@2e-systems.com> 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
>> 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
>svc:/application/virtualbox/zoneaccess:default
>> root@cascade:~#
>> [ Apr 29 08:57:57 Method "start" exited with status 1. ]
>
>Hi all,
>
>I want to add some more ifor, just regarding WebService 
>(https://www.virtualbox.org/manual/ch09.html#vboxwebsrv-daemon):
>
>:; svcprop -p config svc:/application/virtualbox/webservice:default
>config/keyfile astring ""
>config/port integer 18083
>config/user astring root
>config/host astring solarix
>
>:; pfexec svcadm enable svc:/application/virtualbox/webservice:default
>:; svcs -a | grep virtualbox
>disabled       Apr_28   svc:/application/virtualbox/autostart:default
>disabled       Apr_28   svc:/application/virtualbox/balloonctrl:default
>disabled       Apr_28   svc:/application/virtualbox/zoneaccess:default
>online         Apr_28   svc:/application/virtualbox/run-once:default
>online         15:42:55 svc:/application/virtualbox/webservice:default
>
># BUT, I get error when trying to access solarix:18083 on browser. Log 
>extract:
>:; uname -rosv
>SunOS 5.11 illumos-5eadbc3070 illumos
>
>:; tail -19 $(svcs -L svc:/application/virtualbox/webservice:default)
>[ Apr 30 15:42:55 Enabled. ]
>[ Apr 30 15:42:55 Executing start method 
>("/opt/VirtualBox/smf-vboxwebsrv.sh start"). ]
>Oracle VM VirtualBox web service Version 6.1.6
>(C) 2007-2020 Oracle Corporation
>All rights reserved.
>00:00:00.000250 main     VirtualBox web service 6.1.6 r137129 
>solaris.amd64 (Apr 22 2020 06:29:13) release log
>00:00:00.000264 main     Log opened 2020-04-30T13:42:55.983209000Z
>00:00:00.000265 main     Build Type: release
>00:00:00.000269 main     OS Product: SunOS
>00:00:00.000270 main     OS Release: 5.11
>00:00:00.000271 main     OS Version: illumos-5eadbc3070
>00:00:00.000365 main     DMI Product Name: To Be Filled By O.E.M.
>00:00:00.000391 main     DMI Product Version: To Be Filled By O.E.M.
>00:00:00.000398 main     Firmware type: failed - VERR_NOT_SUPPORTED
>00:00:00.001149 main     Host RAM: 16309MB (15.9GB) total, 11316MB 
>(11.0GB) available
>00:00:00.001158 main     Executable: /opt/VirtualBox/amd64/vboxwebsrv
>00:00:00.001159 main     Process ID: 16246
>00:00:00.001159 main     Package type: SOLARIS_64BITS_GENERIC (OSE)
>[ Apr 30 15:42:55 Method "start" exited with status 0. ]
>
>
>No idea what error "Firmware type: failed - VERR_NOT_SUPPORTED" means. 
>Error from browser:
>---<snip> --- <XML>---
>This XML file does not appear to have any style information associated 
>with it. The document tree is shown below.
><SOAP-ENV:Envelope 
>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; 
>xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; 
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
>xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
>xmlns:vbox="http://www.virtualbox.org/";>
><SOAP-ENV:Body>
><SOAP-ENV:Fault>
><faultcode>SOAP-ENV:Client</faultcode>
><faultstring>HTTP GET method not implemented</faultstring>
></SOAP-ENV:Fault>
></SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>---<snip> --- <XML>---
>
>Regards.
>> 
>> On 04/28/20 11:38 PM, Alexander Pyhalov via openindiana-discuss
>wrote:
>>> Hi.
>>> What exact service does enter maintenance mode?
>>> Can you share its logs?
>>>
>>> С уважением,
>>> Александр Пыхалов,
>>> программист отдела телекоммуникационной инфраструктуры
>>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>>
>>>
>>> ________________________________________
>>> От: Jack Whitehead <8910...@telus.net>
>>> Отправлено: 29 апреля 2020 г. 1:52
>>> Кому: openindiana-discuss@openindiana.org
>>> Тема: [OpenIndiana-discuss] VirtualBox 6.1.4 worked, 6.1.6 does not
>>>
>>> I posted yesterday regarding problems I'm having getting VirtualBox
>>> working on a new OI install.
>>>
>>> I had an up to date OI install on an older machine that was running
>>> 6.1.4 without problems.
>>>
>>> Older machine...
>>>
>>> Gigabyte GA-890GPA-UD3H
>>>
>>> AMD Phenom II X4 965
>>>
>>> 8GB memory
>>>
>>> Classic BIOS
>>>
>>> VirtualBox 6.1.4 installs from repository and runs
>>>
>>>
>>> Newer machine...
>>>
>>> ASUS Sabertooth 990FX
>>>
>>> AMD FX8350
>>>
>>> 32GB memory
>>>
>>> UEFI BIOS
>>>
>>> VirtualBox 6.1.6 installs but does not run - enters maintenance
>mode.
>>>
>>>
>>> I tried installing 6.1.4 on the newer machine. It seems it's no
>longer
>>> available in the repositories...
>>>
>>> root@cascade:~# pkg install virtualbox@6.1.4-2020.0.1.0
>>> Creating Plan (Solver setup): /
>>> pkg install: No matching version of system/virtualbox can be
>installed:
>>>     Reject: pkg://openindiana.org/system/virtualbox@6.1.4-2020.0.1.0
>>> pkg://openindiana.org/system/virtualbox@6.1.4-2020.0.1.0
>>>     Reason:  This version is excluded by installed incorporation
>>> consolidation/userland/userland-incorporation@0.5.11-2020.0.1.12890
>>> root@cascade:~#
>>>
>>>
>>> Is anyone running 6.1.6 successfully? Any help or suggestions would
>be
>>> appreciated.
>>>
>>> Thanks, Jack
>>>
>>> _______________________________________________
>>> 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
>
>-- 
>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

For running virtualboxes as an smf service each try 
https://github.com/jimklimov/vboxsvc ;) 

Until at least 6.0 it worked, did not have a 6.1.x solarish server yet :(

The web-service goes well with phpVirtualbox project that gives a web-UI to 
manage your boxes (but rdp/vnc to console is your concern).

Jim

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

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

Reply via email to