Ah Thanks. I was close.
The Loaded Modules look ok though.
modinfo | grep vbox
200 fffffffff7b645a8 d08 308 1 vboxnet (VirtualBox NetAdp
5.2.22r126257)
202 fffffffff88a6000 55b48 306 1 vboxdrv (VirtualBox HostDrv
5.2.22r12625)
248 fffffffff8aa7000 77e8 307 1 vboxflt (VirtualBox NetDrv
5.2.22r126257)
248 fffffffff8aa7000 77e8 - 1 vboxflt (VirtualBox NetMod
5.2.22r126257)
250 fffffffff8ab6000 48d8 310 1 vboxusbmon (VirtualBox USBMon
5.2.22r126257
Sidenote we have a smf service called
svc:/application/virtualbox/balloonctrl:default which cannot run because
that component does not exist in our install.
[ Dec 8 15:42:56 Disabled. ]
[ Dec 8 15:42:56 Rereading configuration. ]
[ Dec 9 20:54:45 Enabled. ]
[ Dec 9 20:54:45 Executing start method
("/opt/VirtualBox/smf-vboxballoonctrl.sh start"). ]
ERROR: /opt/VirtualBox/VBoxBalloonCtrl does not exist.
[ Dec 9 20:54:45 Method "start" exited with status 96. ]
On 12/09/18 09:01 PM, Richard L. Hamilton wrote:
> The command to list loaded kernel modules is "modinfo".
>
>> On Dec 9, 2018, at 14:51, Till Wegmüller <toaster...@gmail.com> wrote:
>>
>> Hi Aurelian
>>
>> Good Question. How can I check the the Modules are loaded? I only know
>> lsmod from linux but I know that command does not exist in illumos.
>>
>> I rebooted multiple times. After each Panic et least :) and after that I
>> checked if something may have gotten stuck in an update so I Updated and
>> rebooted. So if it is a missing module it wont be solved by rebooting.
>>
>>
>> Greetings
>> Toast
>>
>> On 12/09/18 08:47 PM, Aurélien Larcher wrote:
>>> Did you reboot after installing, just to make sure the right modules are
>>> loaded?
>>>
>>> On Sun, Dec 9, 2018 at 8:44 PM Till Wegmüller <toaster...@gmail.com> wrote:
>>>
>>>> Hi
>>>>
>>>> Thanks for that work guys. Unfortunately I does not work for me.
>>>> My System Panics.
>>>> I updated to the latest release this morning and still get panics every
>>>> time I want to boot a VM.
>>>>
>>>> Does anybody know a thing I am missing or should I open a bug report?
>>>>
>>>> MDB output:
>>>> sudo mdb vmcore.1
>>>> Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc apix
>>>> scsi_vhci zfs sata ip hook neti sockfs arp usba xhci mm fctl stmf
>>>> stmf_sbd lofs random sd idm cpc crypto fcip fcp ufs logindmux nsmb ptm
>>>> smbsrv nfs sppp ipc ]
>>>>> $C
>>>> ffffff003e31ba00 0xfffffffff8d72b66()
>>>> ffffff003e31ba70 0xfffffffff8d6ddd4()
>>>> ffffff003e31ba90 0xfffffffff8d6e5c5()
>>>> ffffff003e31bb30 0xfffffffff8e0e1a6()
>>>> ffffff003e31bbb0 0xfffffffff8d6f1d7()
>>>> ffffff003e31bc30 supdrvIOCtl+0x148a()
>>>> ffffff003e31bcc0 VBoxDrvSolarisIOCtl+0x361()
>>>> ffffff003e31bd00 cdev_ioctl+0x39(13200000000, c0185687,
>>>> fffffd7fec8ced50, 202003, ffffff0d2200f0f8, ffffff003e31bea8)
>>>> ffffff003e31bd50 spec_ioctl+0x60(ffffff0d20eeec00, c0185687,
>>>> fffffd7fec8ced50, 202003, ffffff0d2200f0f8, ffffff003e31bea8, 0)
>>>> ffffff003e31bde0 fop_ioctl+0x55(ffffff0d20eeec00, c0185687,
>>>> fffffd7fec8ced50, 202003, ffffff0d2200f0f8, ffffff003e31bea8, 0)
>>>> ffffff003e31bf00 ioctl+0x9b(15, ffffffffc0185687, fffffd7fec8ced50)
>>>> ffffff003e31bf10 sys_syscall+0x177()
>>>>> ::status
>>>> debugging crash dump vmcore.1 (64-bit) from Hephaistos
>>>> operating system: 5.11 illumos-863275a46b (i86pc)
>>>> image uuid: db6faf9c-3db4-ca4b-d83a-960dbb5e6e16
>>>> panic message: BAD TRAP: type=e (#pf Page fault) rp=ffffff003e31b8e0
>>>> addr=fffffd7feba20640 occurred in module "<unknown>" due to an illegal
>>>> access to a user address
>>>> dump content: kernel pages only
>>>>>
>>>>
>>>> Tanks for any advice
>>>> Toast.
>>>>
>>>> On 12/07/18 07:10 PM, Geoff Nordli wrote:
>>>>> I was just told there is now a vbox package for omnios.
>>>>>
>>>>> That is awesome news and kudos to the Omnios and OI community for
>>>>> getting vbox to work on illumos.
>>>>>
>>>>>
>>>>> On 2018-12-07 9:31 a.m., Geoff Nordli wrote:
>>>>>> Hi.
>>>>>>
>>>>>> Any ideas on how I could convert the OI package to install on
>>>>>> Omnios? I know the GUI part won't work. I am just looking for the
>>>>>> command line part.
>>>>>>
>>>>>> thanks,
>>>>>>
>>>>>> Geoff
>>>>>>
>>>>>> On 2018-12-06 10:11 a.m., Alexander Pyhalov via openindiana-discuss
>>>>>> wrote:
>>>>>>> Hello.
>>>>>>> VirtualBox 5.2.22 is available from /hipster repository as
>>>>>>> system/virtualbox .
>>>>>>> GUI works as expected.
>>>>>>>
>>>>>>> The package is installable in zone, but is not tested there and
>>>>>>> likely additional work is needed to make it functioning in NGZ.
>>>>>>>
>>>>>>>
>>>>>>> С уважением,
>>>>>>> Александр Пыхалов,
>>>>>>> программист отдела телекоммуникационной инфраструктуры
>>>>>>> управления информационно-коммуникационной инфраструктуры ЮФУ
>>>>>>>
>>>>>>>
>>>>>>> ________________________________________
>>>>>>> От: Stephan Althaus <stephan.alth...@duedinghausen.eu>
>>>>>>> Отправлено: 18 ноября 2018 г. 23:47:03
>>>>>>> Кому: openindiana-discuss@openindiana.org
>>>>>>> Тема: Re: [OpenIndiana-discuss] VirtualBox
>>>>>>>
>>>>>>> Hello!
>>>>>>>
>>>>>>> Just to confirm the current state,
>>>>>>>
>>>>>>> We are able to run VirtualBox virtual machines as user in Background by
>>>>>>> this:
>>>>>>> VBoxHeadless -s <vmName>
>>>>>>> and use the graphical frontend via RDP for example or SSH dependant of
>>>>>>> the guest OS,
>>>>>>> save the current state of the VM to disk with
>>>>>>> VBoxManage controlvm <vmName> savestate
>>>>>>> as i am used to do with closing the virtualbox GUI
>>>>>>>
>>>>>>> I tested one existing Win XP VM and one existent VM with recent Debian
>>>>>>> guest OS
>>>>>>>
>>>>>>> if you like to see the gui do "sudo 'VirtualBox' " and a "machine->add"
>>>>>>>
>>>>>>> Thanks again for your work, Aurélien
>>>>>>>
>>>>>>> Greetings,
>>>>>>> Stephan
>>>>>>>
>>>>>>> On 17.11.18 07:24, Aurélien Larcher wrote:
>>>>>>>> To be clear, Virtualbox's GUI does not run as non-root if hardening is
>>>>>>>> enabled seemingly due to some loading security mechanism.
>>>>>>>> The GUI runs as root.
>>>>>>>> Headless runs as expected.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 11/16/18, Stephan Althaus <stephan.alth...@duedinghausen.eu>
>>>> wrote:
>>>>>>>>> Hello!
>>>>>>>>>
>>>>>>>>> Short story:
>>>>>>>>>
>>>>>>>>> I managed to build VirtualBox successfully. The target system is on
>>>>>>>>> SunOS dell 5.11 illumos-b75eb7e6b5 i86pc i386 i86pc
>>>>>>>>>
>>>>>>>>> VirtualBox does not run on my target machine complaining about
>>>>>>>>>
>>>>>>>>> ld.so.1: VirtualBox: fatal: libQt5XcbQpa.so.5: open failed: No such
>>>>>>>>> file
>>>>>>>>> or directory
>>>>>>>>> ld.so.1: VirtualBox: fatal: relocation error: file
>>>>>>>>> /usr/lib/qt/5.8/plugins/amd64/platforms/libqxcb.so: symbol
>>>>>>>>> _ZN15QXcbIntegrationC1ERK11QStringListRiPPc: referenced symbol not
>>>>>>>>> found
>>>>>>>>>
>>>>>>>>> I will investigate further - tomorrow evening maybe..
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> LONG story
>>>>>>>>>
>>>>>>>>> My Package can be found and installed by doing this:
>>>>>>>>> #pkg unset-publisher userland
>>>>>>>>> #pkg set-publisher -g http://duedinghausen.eu:10000/userland
>>>> userland
>>>>>>>>> #pkg refresh
>>>>>>>>> #pkg install
>>>>>>>>> pkg://userland/system/virtualbox@5.2.22
>>>> ,5.11-2018.0.0.0:20181116T220242Z
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> i tried and managed to get the sources of oi-userland virtualbox with
>>>>>>>>> date 2018/11/13
>>>>>>>>>
>>>>>>>>>
>>>> https://codeload.github.com/OpenIndiana/oi-userland/zip/e3d92fa79d298d84ba67a8b46c042a647841c6cb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> First error when building:
>>>>>>>>>
>>>>>>>>>
>>>> /tank/src/oi-userland/components/sysutils/virtualbox/build/amd64/src/VBox/Devices/Audio/DrvHostOSSAudio.cpp:22:27:
>>>>>>>>>
>>>>>>>>> fatal error: sys/soundcard.h: No such file or directory
>>>>>>>>> #include <sys/soundcard.h>
>>>>>>>>> ^
>>>>>>>>> i installed
>>>>>>>>>
>>>>>>>>> #pkg install pkg:/system/header/header-audio
>>>>>>>>>
>>>>>>>>> to fix that.
>>>>>>>>>
>>>>>>>>> Then, qt5 was not found. In the output i found a hint to do
>>>>>>>>> source ./build/amd64/env.sh
>>>>>>>>>
>>>>>>>>> But, QT5 was still not found. The directory stated in the env.sh
>>>>>>>>> was not
>>>>>>>>> correct for my system.
>>>>>>>>> The QT PATH in the Makefile was set to /usr/qt/5, i changed that to
>>>>>>>>> /usr/lib/qt/5.8
>>>>>>>>>
>>>>>>>>> next missing packages:
>>>>>>>>> #pkg install pkg:/system/header/header-usb
>>>>>>>>> #pkg install pkg:/system/header/header-ugen
>>>>>>>>>
>>>>>>>>> -- maybe i forgot to gmake env-prep before this all..
>>>>>>>>>
>>>>>>>>> Finally, after install on the target system,
>>>>>>>>> it does not run complaining about libQt5X11Extras.so.5
>>>>>>>>> #pkg install qt5
>>>>>>>>> :-D
>>>>>>>>>
>>>>>>>>> Greetings,
>>>>>>>>> Stephan
>>>>>>>>>
>>>>>>>>> On 14.11.18 20:40, Till Wegmüller wrote:
>>>>>>>>>> Hi Tim
>>>>>>>>>>
>>>>>>>>>> It is quite hard to get to Feature parity with Virtualbox when it
>>>>>>>>>> comes
>>>>>>>>>> to Desktop Features. Both KVM and bHyve have traditionally been more
>>>>>>>>>> used in the Server and Cloud Market. However I believe some
>>>>>>>>>> workarounds
>>>>>>>>>> can be made.
>>>>>>>>>>
>>>>>>>>>> First Proper Graphics Integration. I have since long ago stopped
>>>>>>>>>> using
>>>>>>>>>> any Virtualmachine Console for something like daily work with a GUI
>>>>>>>>>> (Windows) The Built in RDP Server available in almost any Windows
>>>>>>>>>> Version is massively Powerfull and the FOSS Implementation xfreerdp
>>>>>>>>>> works well for many Use cases. Including Clipbord sharing any much
>>>>>>>>>> more.
>>>>>>>>>> Using the Virtual Machines Remote Desktop Capability is what you
>>>>>>>>>> want in
>>>>>>>>>> most cases.
>>>>>>>>>>
>>>>>>>>>> RedHat tried to offer a competing Product to Microsofts RDP with
>>>>>>>>>> Spice
>>>>>>>>>> but did not succeed that much. And as is unfortunately common with
>>>>>>>>>> RedHat Software it makes heavy use of Linux exclusive functionality.
>>>>>>>>>>
>>>>>>>>>> Both bHyve and QEMU use VNC as default. TigerVNC which we have
>>>>>>>>>> packaged
>>>>>>>>>> should allow for Good resolution and Clipboard Sharing. You may
>>>>>>>>>> need the
>>>>>>>>>> Virtio Windows Dirvers and the Quemu Guest Agent though. I would
>>>>>>>>>> guess
>>>>>>>>>> since Virtualbox also uses software on the Guest for this purpose.
>>>>>>>>>>
>>>>>>>>>> bHyve looks like to be a step Back when it comes to Desktop
>>>> features.
>>>>>>>>>>
>>>>>>>>>> As for Resolution. This depends very much on the Graphics device
>>>> Qemu
>>>>>>>>>> presents to the VM. We seem to have cirrus, qxl, vmware and std
>>>>>>>>>> available. I believe std is vesa. At least qxl, cirrus and vmware
>>>>>>>>>> should
>>>>>>>>>> be able to support 1080p Dsktop resolutions. You will need to pass
>>>>>>>>>> the
>>>>>>>>>> correct -vga option when starting the VM.
>>>>>>>>>>
>>>>>>>>>> As for shared Folders. The situation seems a lot better here for
>>>> both
>>>>>>>>>> KVM and bHyve. Both Support virtio-9p aka VirtFS. Which has kernel
>>>>>>>>>> drivers for at least Linux which can use the Filesystem as Root
>>>>>>>>>> apparently. Unfortunatly Windows Driver Work is not yet that
>>>> complete
>>>>>>>>>> see [0]. But with some Poking of both the ReactOS and the virtio-win
>>>>>>>>>> Community this will be the way to go for shared folders. What
>>>>>>>>>> remains as
>>>>>>>>>> a question is if we have virtio-9p support compiled with our
>>>>>>>>>> version of
>>>>>>>>>> Qemu as it is quite recent. See [1] for examples of usage.
>>>>>>>>>>
>>>>>>>>>> While finishing this mail I noticed the Features list on freerdp
>>>>>>>>>> [2]. It
>>>>>>>>>> has everything you wanted. Given the feature compiles in Illumos. I
>>>>>>>>>> think the Quickest way to get to feature parity is using Windows RDP
>>>>>>>>>> server and Freedrp.
>>>>>>>>>>
>>>>>>>>>> [0]
>>>>>>>>>> https://github.com/virtio-win/kvm-guest-drivers-windows/issues/126
>>>>>>>>>> [1] https://github.com/FreeRDP/FreeRDP/wiki/CommandLineInterface
>>>>>>>>>> [2] https://github.com/FreeRDP/FreeRDP/wiki/CommandLineInterface
>>>>>>>>>>
>>>>>>>>>> Researching Greetings
>>>>>>>>>> Till
>>>>>>>>>> On 11/14/18 07:37 PM, Tim Mooney wrote:
>>>>>>>>>>> In regard to: Re: [OpenIndiana-discuss] VirtualBox, Stephan Althaus
>>>>>>>>>>> said...:
>>>>>>>>>>>
>>>>>>>>>>>> If you are on OmniOs / Omniosce, you have Bhyve.
>>>>>>>>>>>> You can use that instead of virtualbox.
>>>>>>>>>>>>
>>>>>>>>>>>> With Openindiana, you could use QEMU-KVM as well..
>>>>>>>>>>>> What are your personal reasons not to do so?
>>>>>>>>>>> There was a thread a couple weeks ago where some people, myself
>>>>>>>>>>> included,
>>>>>>>>>>> posted some of the reasons why they had previously found VirtualBox
>>>>>>>>>>> preferrable to KVM. The "feature parity" part of the thread kind
>>>> of
>>>>>>>>>>> starts with my post:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>> https://openindiana.org/pipermail/openindiana-discuss/2018-October/022445.html
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Tim
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>
>>>
>>>
>>
>> _______________________________________________
>> 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
