Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 26/10/2019 6:12 am, Geoff Nordli wrote: Hi Michal. You could be on to something there. I don't have a cpuid tool. Any suggestions on getting the cpu information. Likewise, happy to help. My machine is running on an Intel i5 8400 and the H370 chipset, if that helps? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 2019-10-25 10:49 a.m., Michal Nowak wrote: On 10/25/19 06:53 PM, Geoff Nordli wrote: On 2019-10-23 10:31 p.m., Michal Nowak wrote: Please, run the long mdb command on the dump file from the https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump document echo '::panicinfo\n::cpuinfo -v\n::threadlist -v 10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 0 > ~/crash.0 and attach the resulting text file somewhere. Email or some paste service should do fine. Thanks, Michal On 10/24/19 05:53 AM, Carl Brewer wrote: On 24/10/2019 2:19 pm, Carl Brewer wrote: I can pop these files on a webserver if that helps anyone to have a look, and see what might be going wrong. here they are : http://nr1.aboc.net.au/testy/ Hi Michal. We know that setting the disable_smap fixes the crash part. I guess the part I don't understand is why some systems don't need to disable smap. It concerns me that there is something wrong. thanks, Geoff I don't know, but one possibility is that folks run OpenIndiana on older systems where SMAP is not available, or do not run VirtualBox. For example according to `cpuid` utility my Lenovo 230 laptop with Ivy Bridge gen CPU does not have SMAP (Supervisor Mode Access Prevention), only SMEP (Supervisor Mode Execution Protection) and I run VirtualBox without problems. Can someone who runs VirtualBox on Broadwell or newer CPU check `cpuid`, if they have SMAP? If there's something wrong it's likely something in the VirtualBox kernel code trying to access memory the SMAP-aware kernel does not want it to have. I found a VirtualBox bug report on this topic but no response from VirtualBox devs for more than a year: https://www.virtualbox.org/ticket/17958. Even Oracle acknowledges this problem with Solaris 11.4: https://docs.oracle.com/cd/E37838_01/html/E60973/appcompat.html#SERNSgtaji. Their workaround is to disable SMAP. In the ticket 17958 I mention other SMAP fixes for Linux and macOS, someone motivated enough might want to go thru them and have a look if they are applicable to Solaris kernel code as well. Fixes went 4 years ago to VirtualBox 5.0.2 and 5.0.4: https://www.virtualbox.org/wiki/Changelog-5.0. Hi Michal. You could be on to something there. I don't have a cpuid tool. Any suggestions on getting the cpu information. thanks, Geoff ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 10/25/19 06:53 PM, Geoff Nordli wrote: On 2019-10-23 10:31 p.m., Michal Nowak wrote: Please, run the long mdb command on the dump file from the https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump document echo '::panicinfo\n::cpuinfo -v\n::threadlist -v 10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 0 > ~/crash.0 and attach the resulting text file somewhere. Email or some paste service should do fine. Thanks, Michal On 10/24/19 05:53 AM, Carl Brewer wrote: On 24/10/2019 2:19 pm, Carl Brewer wrote: I can pop these files on a webserver if that helps anyone to have a look, and see what might be going wrong. here they are : http://nr1.aboc.net.au/testy/ Hi Michal. We know that setting the disable_smap fixes the crash part. I guess the part I don't understand is why some systems don't need to disable smap. It concerns me that there is something wrong. thanks, Geoff I don't know, but one possibility is that folks run OpenIndiana on older systems where SMAP is not available, or do not run VirtualBox. For example according to `cpuid` utility my Lenovo 230 laptop with Ivy Bridge gen CPU does not have SMAP (Supervisor Mode Access Prevention), only SMEP (Supervisor Mode Execution Protection) and I run VirtualBox without problems. Can someone who runs VirtualBox on Broadwell or newer CPU check `cpuid`, if they have SMAP? If there's something wrong it's likely something in the VirtualBox kernel code trying to access memory the SMAP-aware kernel does not want it to have. I found a VirtualBox bug report on this topic but no response from VirtualBox devs for more than a year: https://www.virtualbox.org/ticket/17958. Even Oracle acknowledges this problem with Solaris 11.4: https://docs.oracle.com/cd/E37838_01/html/E60973/appcompat.html#SERNSgtaji. Their workaround is to disable SMAP. In the ticket 17958 I mention other SMAP fixes for Linux and macOS, someone motivated enough might want to go thru them and have a look if they are applicable to Solaris kernel code as well. Fixes went 4 years ago to VirtualBox 5.0.2 and 5.0.4: https://www.virtualbox.org/wiki/Changelog-5.0. Michal ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 2019-10-23 10:31 p.m., Michal Nowak wrote: Please, run the long mdb command on the dump file from the https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump document echo '::panicinfo\n::cpuinfo -v\n::threadlist -v 10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 0 > ~/crash.0 and attach the resulting text file somewhere. Email or some paste service should do fine. Thanks, Michal On 10/24/19 05:53 AM, Carl Brewer wrote: On 24/10/2019 2:19 pm, Carl Brewer wrote: I can pop these files on a webserver if that helps anyone to have a look, and see what might be going wrong. here they are : http://nr1.aboc.net.au/testy/ Hi Michal. We know that setting the disable_smap fixes the crash part. I guess the part I don't understand is why some systems don't need to disable smap. It concerns me that there is something wrong. thanks, Geoff ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 24/10/2019 4:31 pm, Michal Nowak wrote: Please, run the long mdb command on the dump file from the https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump document echo '::panicinfo\n::cpuinfo -v\n::threadlist -v 10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 0 > ~/crash.0 and attach the resulting text file somewhere. Email or some paste service should do fine. I did, it's here : http://nr1.aboc.net.au/testy/crash.0.bz2 setting disable_smap to 1 solved the problem in the first instance though. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
Please, run the long mdb command on the dump file from the https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump document echo '::panicinfo\n::cpuinfo -v\n::threadlist -v 10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 0 > ~/crash.0 and attach the resulting text file somewhere. Email or some paste service should do fine. Thanks, Michal On 10/24/19 05:53 AM, Carl Brewer wrote: On 24/10/2019 2:19 pm, Carl Brewer wrote: I can pop these files on a webserver if that helps anyone to have a look, and see what might be going wrong. here they are : http://nr1.aboc.net.au/testy/ ___ 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 kernel module not loading - mixed version?
Thank you Geoff Nordli, setting set disable_smap=1 in /etc/system stopped the host server crash. Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 24/10/2019 2:19 pm, Carl Brewer wrote: I can pop these files on a webserver if that helps anyone to have a look, and see what might be going wrong. here they are : http://nr1.aboc.net.au/testy/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 24/10/2019 1:53 pm, Carl Brewer wrote: Doing that now, but the log file is too large to go flinging around in emails on lists. What's the best way to share it here? i did a pkg update -v today, then retried running virtualbox through a VNC session to the console of the server. It crashed the host server just after displaying an initial screen warning that the mouse integration wasn't working. I have a screen shot. crash dumps following your instructions, I have : root@testy:~# ls -la /var/crash/testy/ total 3766974 drwxr-xr-x 2 root root 6 Oct. 24 14:14 . drwxr-xr-x 3 root root 3 Oct. 18 14:40 .. -rw-r--r-- 1 root root 2 Oct. 24 14:14 bounds -rw-r--r-- 1 root root 2211199 Oct. 24 14:14 unix.0 -rw-r--r-- 1 root root 1597566976 Oct. 24 14:14 vmcore.0 -rw-r--r-- 1 root root 332726272 Oct. 24 14:14 vmdump.0 root@testy:~# ls -la ~/crash.0 -rw-r--r-- 1 root root 619102 Oct. 24 14:15 /root/crash.0 I can pop these files on a webserver if that helps anyone to have a look, and see what might be going wrong. Thank you again, Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
Hey Michal, On 20/10/2019 7:12 am, Michal Nowak wrote: If it crashes, can you gather more information from the crash dump? How to do it is described here: https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump. It could be the same thing Geoff reported recently... Doing that now, but the log file is too large to go flinging around in emails on lists. What's the best way to share it here? Thank you, Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 10/19/19 09:21 PM, Carl Brewer wrote: On 20/10/2019 5:08 am, Michal Nowak wrote: Those two failing services are from the system/virtualbox/virtualbox-additions package which is meant to be installed only on VirtualBox guest. Since this is a physical machine (right?), remove it please, restart and retry the VM start. Done, and yes, this is the physical machine that is the host. Now the kernel module not showing up warning has gone away, but it still crashes the server when I start a guest VM. If it crashes, can you gather more information from the crash dump? How to do it is described here: https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump. It could be the same thing Geoff reported recently... Michal I'm away for two days as of today, will resume working on this when I get back. Thank you for your help, Michal. Please, install diagnostic/cpuid package and attach output of `cpuid` as a file. CPU 0: Maximum basic CPUID leaf: 0x0016 CPU vendor string: 'GenuineIntel' Signature: 0x000906ea Family: 0x06 (6) Model: 0x9e (158) Stepping: 0x0a (10) Local APIC: 0 Maximum number of APIC IDs per package: 16 CLFLUSH size: 64 Brand ID: 0 Base features, edx: x87 FPU on chip virtual-8086 mode enhancement debugging extensions page size extensions time stamp counter RDMSR and WRMSR support physical address extensions machine check exception CMPXCHG8B instruction APIC on chip SYSENTER and SYSEXIT instructions memory type range registers PTE global bit machine check architecture conditional move instruction page attribute table 36-bit page size extension CLFLUSH instruction debug store ACPI MMX instruction set FXSAVE/FXRSTOR instructions SSE instructions SSE2 instructions self snoop max APIC IDs reserved field is valid thermal monitor pending break enable Base features, ecx: SSE3 instructions PCLMULQDQ instruction 64-bit DS area MONITOR/MWAIT instructions CPL qualified debug store virtual machine extensions Enhanced Intel SpeedStep thermal monitor 2 SSSE3 instructions silicon debug fused multiply-add AVX instructions CMPXCHG16B instruction xTPR update control perfmon and debug capability process-context identifiers SSE4.1 instructions SSE4.2 instructions x2APIC MOVBE instruction POPCNT instruction TSC deadline AES instructions XSAVE/XRSTOR instructions OS-enabled XSAVE/XRSTOR AVX instructions 16-bit FP conversion instructions RDRAND instruction Cache descriptors: [NOTICE] For cache data, see Deterministic Cache Parameters leaf instead Code TLB: 2MB or 4MB pages fully associative 8 entries Write-back invalidates lower level caches Code TLB: 4KB pages 8-way set associative 128 entries Write-back invalidates lower level caches Data TLB: 1GB pages 4-way set associative 4 entries Write-back invalidates lower level caches Undocumented descriptor Data TLB: 2MB or 4MB pages 4-way set associative 32 entries Write-back invalidates lower level caches Undocumented descriptor Data TLB: 4KB pages 4-way set associative 64 entries Write-back invalidates lower level caches Shared TLB: 1GB pages 4-way set associative 16 entries Write-back invalidates lower level caches Undocumented descriptor Shared TLB: 4KB or 2MB pages 4-way set associative 1536 entries Write-back invalidates lower level caches Undocumented descriptor 64-byte prefetching Processor serial number: disabled (or not supported) Deterministic Cache Parameters: 32KB L1 data cache 8-way set associative 64 byte line size Self-initializing Write-back invalidates lower level caches Shared by max 2 threads 32KB L1 code cache 8-way set associative 64 byte line size Self-initializing Write-back invalidates lower level caches Shared by max 2 threads 256KB L2 unified cache 4-way set associative 64 byte line size Self-initializing Write-back invalidates lower level caches Shared by max 2 threads 9MB L3 unified cache 12-way set associative 64 byte line size Self-initializing Inclusive of lower cache levels Complex indexing Write-back invalidates lower level caches Shared by max 16 threads MONITOR/MWAIT features: Smallest monitor-line size
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 20/10/2019 5:08 am, Michal Nowak wrote: Those two failing services are from the system/virtualbox/virtualbox-additions package which is meant to be installed only on VirtualBox guest. Since this is a physical machine (right?), remove it please, restart and retry the VM start. Done, and yes, this is the physical machine that is the host. Now the kernel module not showing up warning has gone away, but it still crashes the server when I start a guest VM. I'm away for two days as of today, will resume working on this when I get back. Thank you for your help, Michal. Please, install diagnostic/cpuid package and attach output of `cpuid` as a file. CPU 0: Maximum basic CPUID leaf: 0x0016 CPU vendor string: 'GenuineIntel' Signature: 0x000906ea Family: 0x06 (6) Model:0x9e (158) Stepping: 0x0a (10) Local APIC: 0 Maximum number of APIC IDs per package: 16 CLFLUSH size: 64 Brand ID: 0 Base features, edx: x87 FPU on chip virtual-8086 mode enhancement debugging extensions page size extensions time stamp counter RDMSR and WRMSR support physical address extensions machine check exception CMPXCHG8B instruction APIC on chip SYSENTER and SYSEXIT instructions memory type range registers PTE global bit machine check architecture conditional move instruction page attribute table 36-bit page size extension CLFLUSH instruction debug store ACPI MMX instruction set FXSAVE/FXRSTOR instructions SSE instructions SSE2 instructions self snoop max APIC IDs reserved field is valid thermal monitor pending break enable Base features, ecx: SSE3 instructions PCLMULQDQ instruction 64-bit DS area MONITOR/MWAIT instructions CPL qualified debug store virtual machine extensions Enhanced Intel SpeedStep thermal monitor 2 SSSE3 instructions silicon debug fused multiply-add AVX instructions CMPXCHG16B instruction xTPR update control perfmon and debug capability process-context identifiers SSE4.1 instructions SSE4.2 instructions x2APIC MOVBE instruction POPCNT instruction TSC deadline AES instructions XSAVE/XRSTOR instructions OS-enabled XSAVE/XRSTOR AVX instructions 16-bit FP conversion instructions RDRAND instruction Cache descriptors: [NOTICE] For cache data, see Deterministic Cache Parameters leaf instead Code TLB: 2MB or 4MB pages fully associative 8 entries Write-back invalidates lower level caches Code TLB: 4KB pages 8-way set associative 128 entries Write-back invalidates lower level caches Data TLB: 1GB pages 4-way set associative 4 entries Write-back invalidates lower level caches Undocumented descriptor Data TLB: 2MB or 4MB pages 4-way set associative 32 entries Write-back invalidates lower level caches Undocumented descriptor Data TLB: 4KB pages 4-way set associative 64 entries Write-back invalidates lower level caches Shared TLB: 1GB pages 4-way set associative 16 entries Write-back invalidates lower level caches Undocumented descriptor Shared TLB: 4KB or 2MB pages 4-way set associative 1536 entries Write-back invalidates lower level caches Undocumented descriptor 64-byte prefetching Processor serial number: disabled (or not supported) Deterministic Cache Parameters: 32KB L1 data cache 8-way set associative 64 byte line size Self-initializing Write-back invalidates lower level caches Shared by max 2 threads 32KB L1 code cache 8-way set associative 64 byte line size Self-initializing Write-back invalidates lower level caches Shared by max 2 threads 256KB L2 unified cache 4-way set associative 64 byte line size Self-initializing Write-back invalidates lower level caches Shared by max 2 threads 9MB L3 unified cache 12-way set associative 64 byte line size Self-initializing Inclusive of lower cache levels Complex indexing Write-back invalidates lower level caches Shared by max 16 threads MONITOR/MWAIT features: Smallest monitor-line size: 64 bytes Largest monitor-line size: 64 bytes Interrupts as break-event for MWAIT, even when interrupts off C1 sub C-states supported by MWAIT: 2 C2 sub C-states supported by MWAIT: 1 C3 sub C-states supported by MWAIT: 2 C4 sub C-states supported by MWAIT: 4 Intel Thermal and Power Management Features: Digital temperature sensor Intel Turbo Boost Technology Always running APIC timer (ARAT) Power
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 10/19/19 01:21 PM, Carl Brewer wrote:
On 19/10/2019 9:10 pm, Michal Nowak wrote:
I am still slightly confused whether you have KVM installed or not and
what is your illumos version. Show us:
pkg list '*kvm*'
pkg list '*kvm*'
pkg list: no packages matching the following patterns are installed:
*kvm*
modinfo | grep -i -e kvm -e vbox
modinfo | grep -i -e kvm -e vbox
274 f82d4000 58848 78 1 vboxdrv (VirtualBox HostDrv
6.0.12r13205)
275 f8a28000 77d8 307 1 vboxflt (VirtualBox NetDrv
6.0.12r132055)
275 f8a28000 77d8 - 1 vboxflt (VirtualBox NetMod
6.0.12r132055)
276 f8026568 d08 308 1 vboxnet (VirtualBox NetAdp
6.0.12r132055)
279 f7cef000 48d8 310 1 vboxusbmon (VirtualBox USBMon
6.0.12r132055
280 f8a3 45d8 313 1 vboxms (VBoxMouseIntegr 6.0.12r132055)
281 f7dfa000 33158 311 1 vboxguest (VirtualBox GstDrv
6.0.12r132055)
root@testy:~#
uname -a
root@testy:~# uname -a
SunOS testy 5.11 illumos-233f6c4995 i86pc i386 i86pc
svcs -a | grep -i virtualbox
root@testy:~# svcs -a | grep -i virtualbox
disabled 20:59:23 svc:/application/virtualbox/balloonctrl:default
disabled 20:59:23 svc:/application/virtualbox/autostart:default
disabled 20:59:23 svc:/application/virtualbox/webservice:default
disabled 20:59:23 svc:/application/virtualbox/zoneaccess:default
online 21:00:04 svc:/application/virtualbox/run-once:default
maintenance 21:04:40 svc:/application/virtualbox/vboxmslnk:default
maintenance 21:04:40 svc:/application/virtualbox/vboxservice:default
svcs -xv
root@testy:~# svcs -xv
svc:/application/virtualbox/vboxservice:default (VirtualBox Service.)
State: maintenance since 19 October 2019 at 09:04:40 pm AEDT
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 19 October 2019 at 09:04:40 pm AEDT
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.
The log shows :
[ Oct. 19 21:04:40 Enabled. ]
[ Oct. 19 21:04:40 Rereading configuration. ]
[ Oct. 19 21:04:40 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ Oct. 19 21:04:40 Method "start" exited with status 1. ]
[ Oct. 19 21:04:40 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ Oct. 19 21:04:40 Method "start" exited with status 1. ]
[ Oct. 19 21:04:40 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ Oct. 19 21:04:40 Method "start" exited with status 1. ]
but :
root@testy:~# ls -la /usr/bin/VBoxService
-r-xr-xr-x 1 root bin 10353240 Oct. 19 21:04
/usr/bin/VBoxService
Those two failing services are from the
system/virtualbox/virtualbox-additions package which is meant to be
installed only on VirtualBox guest. Since this is a physical machine
(right?), remove it please, restart and retry the VM start.
Please, install diagnostic/cpuid package and attach output of `cpuid` as
a file.
Where do you see the "VBoxClient: the VirtualBox kernel service is not
running. Exiting" error message? In the VirtualBox interface?
When I log in using a VNC client, it shows up as a banner in the GUI,
stays for maybe 20s then goes away.
Please, provide a screenshot, I still don't get the context.
Thanks,
Michal
What is your CPU? Either `ddu` or `prtconf -v` will tell you. E.g.:
It's an 8th gen intel i5-8400
cpu, instance #0
...
name='brand-string' type=string items=1
value='Intel(r) Core(tm) i5-3320M CPU @ 2.60GHz'
cpu, instance #0
Driver properties:
name='ddi-no-autodetach' type=int items=1 dev=none
value=0001
name='pm-class' type=string items=1 dev=none
value='CPU'
name='pm-components' type=string items=17 dev=none
value='NAME=CPU Speed' + '1=800MHz' +
'2=900MHz' + '3=1100MHz' + '4=1200MHz' + '5=1400MHz' + '6=1500MHz' +
'7=1700MHz' + '8=1800MHz' + '9=1900MHz' + '10=2100MHz' + '11=2200MHz' +
'12=2400MHz' + '13=2500MHz' + '14=2700MHz' + '15=2800MHz' + '16=2801MHz'
Hardware properties:
name='dtlb-4K-size' type=int items=1
value=0040
name='dtlb-4K-associativity' type=int items=1
value=0004
name='brand-string' type=s
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 19/10/2019 9:10 pm, Michal Nowak wrote:
I am still slightly confused whether you have KVM installed or not and
what is your illumos version. Show us:
pkg list '*kvm*'
pkg list '*kvm*'
pkg list: no packages matching the following patterns are installed:
*kvm*
modinfo | grep -i -e kvm -e vbox
modinfo | grep -i -e kvm -e vbox
274 f82d4000 58848 78 1 vboxdrv (VirtualBox HostDrv
6.0.12r13205)
275 f8a28000 77d8 307 1 vboxflt (VirtualBox NetDrv
6.0.12r132055)
275 f8a28000 77d8 - 1 vboxflt (VirtualBox NetMod
6.0.12r132055)
276 f8026568d08 308 1 vboxnet (VirtualBox NetAdp
6.0.12r132055)
279 f7cef000 48d8 310 1 vboxusbmon (VirtualBox USBMon
6.0.12r132055
280 f8a3 45d8 313 1 vboxms (VBoxMouseIntegr 6.0.12r132055)
281 f7dfa000 33158 311 1 vboxguest (VirtualBox GstDrv
6.0.12r132055)
root@testy:~#
uname -a
root@testy:~# uname -a
SunOS testy 5.11 illumos-233f6c4995 i86pc i386 i86pc
svcs -a | grep -i virtualbox
root@testy:~# svcs -a | grep -i virtualbox
disabled 20:59:23 svc:/application/virtualbox/balloonctrl:default
disabled 20:59:23 svc:/application/virtualbox/autostart:default
disabled 20:59:23 svc:/application/virtualbox/webservice:default
disabled 20:59:23 svc:/application/virtualbox/zoneaccess:default
online 21:00:04 svc:/application/virtualbox/run-once:default
maintenance21:04:40 svc:/application/virtualbox/vboxmslnk:default
maintenance21:04:40 svc:/application/virtualbox/vboxservice:default
svcs -xv
root@testy:~# svcs -xv
svc:/application/virtualbox/vboxservice:default (VirtualBox Service.)
State: maintenance since 19 October 2019 at 09:04:40 pm AEDT
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 19 October 2019 at 09:04:40 pm AEDT
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.
The log shows :
[ Oct. 19 21:04:40 Enabled. ]
[ Oct. 19 21:04:40 Rereading configuration. ]
[ Oct. 19 21:04:40 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ Oct. 19 21:04:40 Method "start" exited with status 1. ]
[ Oct. 19 21:04:40 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ Oct. 19 21:04:40 Method "start" exited with status 1. ]
[ Oct. 19 21:04:40 Executing start method ("/usr/bin/VBoxService"). ]
VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
[ Oct. 19 21:04:40 Method "start" exited with status 1. ]
but :
root@testy:~# ls -la /usr/bin/VBoxService
-r-xr-xr-x 1 root bin 10353240 Oct. 19 21:04 /usr/bin/VBoxService
Where do you see the "VBoxClient: the VirtualBox kernel service is not
running. Exiting" error message? In the VirtualBox interface?
When I log in using a VNC client, it shows up as a banner in the GUI,
stays for maybe 20s then goes away.
What is your CPU? Either `ddu` or `prtconf -v` will tell you. E.g.:
It's an 8th gen intel i5-8400
cpu, instance #0
...
name='brand-string' type=string items=1
value='Intel(r) Core(tm) i5-3320M CPU @ 2.60GHz'
cpu, instance #0
Driver properties:
name='ddi-no-autodetach' type=int items=1 dev=none
value=0001
name='pm-class' type=string items=1 dev=none
value='CPU'
name='pm-components' type=string items=17 dev=none
value='NAME=CPU Speed' + '1=800MHz' +
'2=900MHz' + '3=1100MHz' + '4=1200MHz' + '5=1400MHz' + '6=1500MHz' +
'7=1700MHz' + '8=1800MHz' + '9=1900MHz' + '10=2100MHz' + '11=2200MHz' +
'12=2400MHz' + '13=2500MHz' + '14=2700MHz' + '15=2800MHz' + '16=2801MHz'
Hardware properties:
name='dtlb-4K-size' type=int items=1
value=0040
name='dtlb-4K-associativity' type=int items=1
value=0004
name='brand-string' type=string items=1
value='Intel(r) Core(tm) i5-8400 CPU @ 2.80GHz'
Did VirtualBox worked on any other platform for this CPU?
I haven't tried
Make sure you are running the latest bits by `pkg update -v`.
As of about 3 hours ago!
pkg update -v
No updates available for this image.
root@testy:~# pkg publisher
PUBLISHER TYPE STATUS P LOCATION
openindiana.org origin online F
http://pkg.openindiana.org/hips
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
I am still slightly confused whether you have KVM installed or not and what is your illumos version. Show us: pkg list '*kvm*' modinfo | grep -i -e kvm -e vbox uname -a svcs -a | grep -i virtualbox svcs -xv Where do you see the "VBoxClient: the VirtualBox kernel service is not running. Exiting" error message? In the VirtualBox interface? What is your CPU? Either `ddu` or `prtconf -v` will tell you. E.g.: cpu, instance #0 ... name='brand-string' type=string items=1 value='Intel(r) Core(tm) i5-3320M CPU @ 2.60GHz' Did VirtualBox worked on any other platform for this CPU? Make sure you are running the latest bits by `pkg update -v`. Thanks, Michal ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
further on the quest to get this sorted, randomly groveling for Vm stuff that may be clashing? pkg info shows these that look interesting : Name: driver/xvm/pv Summary: xVM Paravirtualized Drivers Description: xVM Paravirtualized Drivers Category: System/Virtualization State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2019.0.0.19122 Packaging Date: 17 October 2019 at 01:20:38 am Last Install Time: 8 August 2019 at 12:21:28 pm Last Update Time: 17 October 2019 at 11:11:15 pm Size: 337.25 kB FMRI: pkg://openindiana.org/driver/xvm/pv@0.5.11-2019.0.0.19122:20191017T012038Z Name: system/xvm/xvmstore Summary: Hypervisor Domain Tools Description: Hypervisor domain tools Category: System/Virtualization State: Installed Publisher: userland Version: 3.4.2 Branch: 2013.0.0.0 Packaging Date: 24 October 2018 at 01:15:13 pm Size: 113.11 kB FMRI: pkg://userland/system/xvm/xvmstore@3.4.2-2013.0.0.0:20181024T131513Z Name: driver/network/vioif Summary: VirtIO network driver Description: VirtIO network driver Category: Drivers/Networking State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2019.0.0.19122 Packaging Date: 17 October 2019 at 01:16:35 am Last Install Time: 8 August 2019 at 12:21:28 pm Last Update Time: 17 October 2019 at 11:11:15 pm Size: 38.47 kB FMRI: pkg://openindiana.org/driver/network/vioif@0.5.11-2019.0.0.19122:20191017T011635Z Name: driver/network/vmxnet3s Summary: VMware paravirtualized NIC driver Description: VMware paravirtualized NIC driver Category: Drivers/Networking State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2019.0.0.19122 Packaging Date: 17 October 2019 at 01:16:40 am Last Install Time: 8 August 2019 at 12:21:28 pm Last Update Time: 17 October 2019 at 11:11:15 pm Size: 46.96 kB FMRI: pkg://openindiana.org/driver/network/vmxnet3s@0.5.11-2019.0.0.19122:20191017T011640Z I don't want to go randomly removing pkgs that might then break the box, but these? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 19/10/2019 4:04 pm, Carl Brewer wrote: FWIW, I've just built 6.0.14 (all I did was change the Makefile, updated the hashes and the versions for the src). It compiles ok so far. Will see if it behaves any better - I'm guessing if the kernel module warning goes away, it's probably an improvement. Nope, it crashes as soon as I try to start a VM, just after saying it can't catch the mouse. Anyone here who's familiar with debugging this stuff? I'm out of my depth. Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
FWIW, I've just built 6.0.14 (all I did was change the Makefile, updated the hashes and the versions for the src). It compiles ok so far. Will see if it behaves any better - I'm guessing if the kernel module warning goes away, it's probably an improvement. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 18/10/2019 6:36 pm, Predrag Zecevic - Unix Systems Administrator wrote: Hi Carl, do you have kvm installed too? I don't think so : root@testy:/var/crash/testy# pkg info | grep -i kvm Summary: Core Architecture, (Kvm) root@testy:/var/crash/testy# pkg info kvm pkg: info: no packages matching the following patterns you specified are installed on the system. Try querying remotely instead: kvm root@testy:/var/crash/testy# pkg info Kvm pkg: info: no packages matching the following patterns you specified are installed on the system. Try querying remotely instead: Kvm root@testy:/var/crash/testy# pkg info does show : Name: system/library/platform Summary: Core Architecture, (Kvm) Description: core software for a specific hardware platform group Category: System/Core State: Installed Publisher: openindiana.org Version: 0.5.11 Branch: 2019.0.0.19122 Packaging Date: 17 October 2019 at 01:43:06 am Last Install Time: 8 August 2019 at 12:21:28 pm Last Update Time: 17 October 2019 at 11:11:15 pm Size: 23.91 kB FMRI: pkg://openindiana.org/system/library/platform@0.5.11-2019.0.0.19122:20191017T014306Z ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 10/18/19 01:33, Carl Brewer wrote: G'day, Trying to get a VM running on a test server, OI pkg updated from about a month ago, I see this : "VBoxClient: the VirtualBox kernel service is not running. Exiting" I suspect I have a version of the kernel that's been updated, but VB is from an older build. pkg info shows virtualbox v 6.0.12, from 2019.0.0.0 packaged on Sept 14 The kernel : v 0.5.11 branch 2019.0.0.18919 When I try to start a VM it crashes the whole machine and it reboots. Ouch! Is there an easy way to sync them up again? Hints? Thank you, Carl Hi Carl, do you have kvm installed too? That happen to me when I had both virtualization installed at the same time (there is hack to have them both running, but in general - IMHO - one should pick-up one to avoid problems) 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. 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 kernel module not loading - mixed version?
In regard to: Re: [OpenIndiana-discuss] Virtualbox kernel module not...: On 18/10/2019 3:24 pm, Aur?lien Larcher wrote: gmake setup at the root directory. I think this is described in the docs. Not that I noticed, but I was scanning. That's created the repo, thank you The docs are a separate repo, and the published version for how to build and package components from oi-userland is at http://docs.openindiana.org/dev/userland/ The 'gmake setup' step is a one-time "prepare your environment" step, and is outlined in those docs. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure / Division of Information Technology/701-231-1076 (Voice) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 18/10/2019 4:48 pm, Carl Brewer wrote: On 18/10/2019 4:23 pm, Geoff Nordli wrote: Hi Carl. I am having problems with Virtualbox core dumping as well. There was a thread on it recently. https://openindiana.org/pipermail/openindiana-discuss/2019-October/022816.html Here's my dump from those instructions : Oh, the list stripped the file I hate dropbox! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 18/10/2019 4:23 pm, Geoff Nordli wrote: Hi Carl. I am having problems with Virtualbox core dumping as well. There was a thread on it recently. https://openindiana.org/pipermail/openindiana-discuss/2019-October/022816.html Here's my dump from those instructions : Wonder if your kernel dump is similar to mine. Geoff ___ 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 kernel module not loading - mixed version?
On 2019-10-17 4:33 p.m., Carl Brewer wrote: G'day, Trying to get a VM running on a test server, OI pkg updated from about a month ago, I see this : "VBoxClient: the VirtualBox kernel service is not running. Exiting" I suspect I have a version of the kernel that's been updated, but VB is from an older build. pkg info shows virtualbox v 6.0.12, from 2019.0.0.0 packaged on Sept 14 The kernel : v 0.5.11 branch 2019.0.0.18919 When I try to start a VM it crashes the whole machine and it reboots. Ouch! Is there an easy way to sync them up again? Hints? Thank you, Carl Hi Carl. I am having problems with Virtualbox core dumping as well. There was a thread on it recently. https://openindiana.org/pipermail/openindiana-discuss/2019-October/022816.html Wonder if your kernel dump is similar to mine. Geoff ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
Built a repo, grabbed my build of VBX, installed it. Still seeing the error: "VBoxClient: the VirtualBox kernel service is not running. Exiting" pkg info virtualbox Name: system/virtualbox Summary: VirtualBox - general-purpose full virtualizer Category: System/Virtualization State: Installed Publisher: userland Version: 6.0.12 Branch: 2019.0.0.0 Packaging Date: 18 October 2019 at 02:42:48 am Last Install Time: 18 October 2019 at 03:01:18 am Size: 118.63 MB FMRI: pkg://userland/system/virtualbox@6.0.12-2019.0.0.0:20191018T024248Z Project URL: http://www.virtualbox.org/ Source URL: http://download.virtualbox.org/virtualbox/6.0.12/VirtualBox-6.0.12.tar.bz2 Any suggestions? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 18/10/2019 3:47 pm, Carl Brewer wrote: On 18/10/2019 3:24 pm, Aurélien Larcher wrote: gmake setup at the root directory. I think this is described in the docs. Not that I noticed, but I was scanning. That's created the repo, thank you The only place "setup" is mentioned on that page https://github.com/OpenIndiana/oi-userland Is where it talks about a component build. Now I have a repo and somewhere in it, there's a new virtualbox package, what's the trick to pulling a pkg from it? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
On 18/10/2019 3:24 pm, Aurélien Larcher wrote: gmake setup at the root directory. I think this is described in the docs. Not that I noticed, but I was scanning. That's created the repo, thank you Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
gmake setup at the root directory. I think this is described in the docs. On 10/18/19, Carl Brewer wrote: > further to this, I stumbled onto : > https://github.com/OpenIndiana/oi-userland > which gives instructions on how to build individual components. Nice! > > I think I've managed to build a new Virtualbox (still only 6.0.12, I > don't know how to change it yet) - but it got to the end of the gmake > publish and failed, because it didn't know (or I don't!) about the IPS > repository to publish to : > > NEW PACKAGE CONTENTS ARE LOCALLY VALIDATED AND READY TO GO > /usr/bin/touch > /usr/local/src/OI/clone/components/sysutils/virtualbox/build/.pre-published-i386 > /usr/bin/pkgsend -s /usr/local/src/OI/clone/i386/repo publish > --fmri-in-manifest -d > /usr/local/src/OI/clone/components/sysutils/virtualbox/build/prototype/i386/mangled > > -d > /usr/local/src/OI/clone/components/sysutils/virtualbox/build/prototype/i386 > > -d /usr/local/src/OI/clone/components/sysutils/virtualbox/build -d > /usr/local/src/OI/clone/components/sysutils/virtualbox -d > VirtualBox-6.0.12 -T \*.py > /usr/local/src/OI/clone/components/sysutils/virtualbox/build/manifest-i386-virtualbox-additions.pre-published > pkgsend: file protocol error: code: E_HTTP_NOT_FOUND (22) reason: The > path '/usr/local/src/OI/clone/i386/repo' does not contain a valid > package repository. > Repository URL: 'file:///usr/local/src/OI/clone/i386/repo'. > gmake: *** [/usr/local/src/OI/clone/make-rules/ips.mk:494: > /usr/local/src/OI/clone/components/sysutils/virtualbox/build/manifest-i386-virtualbox-additions.published] > > Error 1 > > > > so, trying the obvious, I just created a directory : > /usr/local/src/OI/clone/i386/repo > > But now : > pkgsend: file protocol error: code: E_HTTP_NOT_FOUND (22) reason: The > path '/usr/local/src/OI/clone/i386/repo' does not contain a valid > package repository. > Repository URL: 'file:///usr/local/src/OI/clone/i386/repo'. > > Makes sense. > > If I just want to try the new Virtualbox drivers, which I think I've > managed to build, somewhere, what's the trick? > > 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 kernel module not loading - mixed version?
further to this, I stumbled onto : https://github.com/OpenIndiana/oi-userland which gives instructions on how to build individual components. Nice! I think I've managed to build a new Virtualbox (still only 6.0.12, I don't know how to change it yet) - but it got to the end of the gmake publish and failed, because it didn't know (or I don't!) about the IPS repository to publish to : NEW PACKAGE CONTENTS ARE LOCALLY VALIDATED AND READY TO GO /usr/bin/touch /usr/local/src/OI/clone/components/sysutils/virtualbox/build/.pre-published-i386 /usr/bin/pkgsend -s /usr/local/src/OI/clone/i386/repo publish --fmri-in-manifest -d /usr/local/src/OI/clone/components/sysutils/virtualbox/build/prototype/i386/mangled -d /usr/local/src/OI/clone/components/sysutils/virtualbox/build/prototype/i386 -d /usr/local/src/OI/clone/components/sysutils/virtualbox/build -d /usr/local/src/OI/clone/components/sysutils/virtualbox -d VirtualBox-6.0.12 -T \*.py /usr/local/src/OI/clone/components/sysutils/virtualbox/build/manifest-i386-virtualbox-additions.pre-published pkgsend: file protocol error: code: E_HTTP_NOT_FOUND (22) reason: The path '/usr/local/src/OI/clone/i386/repo' does not contain a valid package repository. Repository URL: 'file:///usr/local/src/OI/clone/i386/repo'. gmake: *** [/usr/local/src/OI/clone/make-rules/ips.mk:494: /usr/local/src/OI/clone/components/sysutils/virtualbox/build/manifest-i386-virtualbox-additions.published] Error 1 so, trying the obvious, I just created a directory : /usr/local/src/OI/clone/i386/repo But now : pkgsend: file protocol error: code: E_HTTP_NOT_FOUND (22) reason: The path '/usr/local/src/OI/clone/i386/repo' does not contain a valid package repository. Repository URL: 'file:///usr/local/src/OI/clone/i386/repo'. Makes sense. If I just want to try the new Virtualbox drivers, which I think I've managed to build, somewhere, what's the trick? Thank you, Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Virtualbox kernel module not loading - mixed version?
G'day, Trying to get a VM running on a test server, OI pkg updated from about a month ago, I see this : "VBoxClient: the VirtualBox kernel service is not running. Exiting" I suspect I have a version of the kernel that's been updated, but VB is from an older build. pkg info shows virtualbox v 6.0.12, from 2019.0.0.0 packaged on Sept 14 The kernel : v 0.5.11 branch 2019.0.0.18919 When I try to start a VM it crashes the whole machine and it reboots. Ouch! Is there an easy way to sync them up again? Hints? Thank you, Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
