Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-19 Thread Nikola M 

On 04/18/16 01:29 PM, Predrag Zečević - Unix Systems Administrator wrote:


Hi,

ticket opened: https://www.illumos.org/issues/6919


I asked helpful VBox people and they says it looks like 'Supervisor Mode 
Access Prevention' (SMAP) problem. 
(https://en.wikipedia.org/wiki/Supervisor_Mode_Access_Prevention), 
VirtualBox disables SMAP only for Solaris builds (SMAP support works on 
Linux, OSX) , because Oracle Solaris disables SMAP.


So aether illumos after illumos-a526879 needs an option to disable SMAP 
for VirtualBox compatibility
or VirtualBox needs to handle SMAP on Solaris build that runs on illumos 
and VirtualBox doesn't have illumos-specific build.


Proposed workaround from tsoome:
disable_smap/W1 in mdb -k , disable_smap is int, so /W should be ok (to 
write 4byte value)


Please try it and report inside https://www.illumos.org/issues/6919 
ticket  if it worked,

so it is know if it is truly SMAP issue.


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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-18 Thread Predrag Zečević - Unix Systems Administrator 

On 04/18/16 11:14 AM, Nikola M wrote:

On 04/18/16 10:04 AM, Predrag Zečević - Unix Systems Administrator wrote:

You could try disabling some of drivers that are non-essential and try
over.

Is it possible that some changes in kernel detect on-board network,
graphic (or both) cards improperly?


Try asking on #illumos.
I , per instance, made my wireless card working  by putting it in
/etc/driver_aliases .


I prefer ticket... Would be OK to open ticket?
I would like to avoid situation like in this one:
https://www.illumos.org/issues/5873


I guess it would be appropriate. Please do.

Under comments on that intel Haswell hardware-related bug, there is a
link ,as I see, that mentions some bugs in intel's Haswell chip itself
and recommendations for putting workaround to put in kernel..
Maybe with one more bug report and more data , in kernel changes for
possible hardware workaround could be sponsored.

"Haswell erratum 131 of the 'Intel® Xeon® Processor E3-1200 v3 Product
Family Specification Update' "
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-e3-1200v3-spec-update.pdf


http://svnweb.freebsd.org/base/head/sys/x86/x86/mca.c?r1=269052=269051=269052



Hi,

ticket opened: https://www.illumos.org/issues/6919

Regards.


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


--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!

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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-18 Thread Nikola M 

On 04/18/16 10:04 AM, Predrag Zečević - Unix Systems Administrator wrote:

You could try disabling some of drivers that are non-essential and try
over.
Is it possible that some changes in kernel detect on-board network, 
graphic (or both) cards improperly?


Try asking on #illumos.
I , per instance, made my wireless card working  by putting it in 
/etc/driver_aliases .



I prefer ticket... Would be OK to open ticket?
I would like to avoid situation like in this one: 
https://www.illumos.org/issues/5873


I guess it would be appropriate. Please do.

Under comments on that intel Haswell hardware-related bug, there is a 
link ,as I see, that mentions some bugs in intel's Haswell chip itself 
and recommendations for putting workaround to put in kernel..
Maybe with one more bug report and more data , in kernel changes for 
possible hardware workaround could be sponsored.


"Haswell erratum 131 of the 'Intel® Xeon® Processor E3-1200 v3 Product 
Family Specification Update' "
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-e3-1200v3-spec-update.pdf 


http://svnweb.freebsd.org/base/head/sys/x86/x86/mca.c?r1=269052=269051=269052

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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-18 Thread Predrag Zečević - Unix Systems Administrator 

On 04/18/16 09:54 AM, Nikola M wrote:

On 04/18/16 08:32 AM, Predrag Zečević - Unix Systems Administrator wrote:

Is it "vboxuser" or "vboxusers"?


Yes, vboxuser



Anyway, tried everything I could think of, and nothing works...

To me, it looks like some driver was changed/upgraded and that causes
problem. And I am not sure how to trace that down...


I reported using same illumos timestamp with no issues at the moment,
but truly with the other hardware then yours.
Do you actually use benefits of VirtualBox proprietary extension and can
you try without having it installed. (Make new BE out of working, boot
from new BE, disable extension, update)

Well, using extensions heavily, especially for Win guest...


You could try disabling some of drivers that are non-essential and try
over.
Is it possible that some changes in kernel detect on-board network, 
graphic (or both) cards improperly?



What are VBox machine settings


ALL VMs are failing (both Win and Linux).


It is valuable to see what is actually going on, because running on
newer hardware truly is more valuable for the future then the old
hardware I run on..

Sure.


If at the moment VBox is working right on one OI's BE, VBox stays the
same and you try getting just illumos is updated, that is where to find
the problem as you suggested.

Yes.


Feel free to come to irc.Freenode.net, #openindiana and #oi-dev and
#illumos IRC channels so we can interactively discuss, pastebin/bpaste
and try to see what could be done for your install.


I prefer ticket... Would be OK to open ticket?
I would like to avoid situation like in this one: 
https://www.illumos.org/issues/5873


Best regards.


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


--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!

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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-18 Thread Nikola M 

On 04/18/16 08:32 AM, Predrag Zečević - Unix Systems Administrator wrote:

Is it "vboxuser" or "vboxusers"?


Yes, vboxuser



Anyway, tried everything I could think of, and nothing works...

To me, it looks like some driver was changed/upgraded and that causes 
problem. And I am not sure how to trace that down...


I reported using same illumos timestamp with no issues at the moment, 
but truly with the other hardware then yours.
Do you actually use benefits of VirtualBox proprietary extension and can 
you try without having it installed. (Make new BE out of working, boot 
from new BE, disable extension, update)
You could try disabling some of drivers that are non-essential and try 
over.

What are VBox machine settings

It is valuable to see what is actually going on, because running on 
newer hardware truly is more valuable for the future then the old 
hardware I run on..


If at the moment VBox is working right on one OI's BE, VBox stays the 
same and you try getting just illumos is updated, that is where to find 
the problem as you suggested.
Feel free to come to irc.Freenode.net, #openindiana and #oi-dev and 
#illumos IRC channels so we can interactively discuss, pastebin/bpaste 
and try to see what could be done for your install.



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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-18 Thread Predrag Zečević - Unix Systems Administrator 


On 04/16/16 08:58 PM, Jim Klimov wrote:

16 апреля 2016 г. 10:21:00 CEST, Alexander Pyhalov  пишет:

Jim Klimov писал 15.04.2016 22:01:

15 апреля 2016 г. 20:07:47 CEST, Nikola M  пишет:

On 04/15/16 04:12 PM, Predrag Zečević - Unix Systems Administrator
wrote:


Trying it:
$ pfexec fmdump -Vp -u e701b777-689f-6be0-952a-9e382a0c23e5

No luck this time - nothing has been displayed

$ ls -al /export/tmp/crash/vmdump.1
-rw-r--r-- 1 root root 363M Apr 15 15:58 /export/tmp/crash/vmdump.1

So, I am writing this from reverted image :-(


User using VirtualBox needs to be member of 'vboxuser' group.



Hi,
is it something new in VirtualBox 5? I run 4.3.30, user doesn't have
any
special permissions.
---
System Administrator of Southern Federal University Computer Center



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


It was there from very long ago. Certain device nodes maintained by virtualbox 
are owned by the vboxusers group, so people wanting usb passthrough, maybe raw 
host partition delegation, etc. and some other usecases must be members of the 
group.

Not every usecase needs it - so maybe you never cared ;)

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



Dear all,

thanks for ideas, but you probably have missed that VBox is working with 
some older bits (BE) already, ONLY when I upgrade BE it stops (actually 
crashes box). My user account is member of that group already (in this 
working BE, which is then updated):


$ grep predrag /etc/group
vboxuser::1962:predrag_zecevic

Is it "vboxuser" or "vboxusers"?

Anyway, tried everything I could think of, and nothing works...

To me, it looks like some driver was changed/upgraded and that causes 
problem. And I am not sure how to trace that down...


Regards.

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



--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!

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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-16 Thread Jim Klimov 
16 апреля 2016 г. 10:21:00 CEST, Alexander Pyhalov  пишет:
>Jim Klimov писал 15.04.2016 22:01:
>> 15 апреля 2016 г. 20:07:47 CEST, Nikola M  пишет:
>>> On 04/15/16 04:12 PM, Predrag Zečević - Unix Systems Administrator
>>> wrote:
 
 Trying it:
 $ pfexec fmdump -Vp -u e701b777-689f-6be0-952a-9e382a0c23e5
 
 No luck this time - nothing has been displayed
 
 $ ls -al /export/tmp/crash/vmdump.1
 -rw-r--r-- 1 root root 363M Apr 15 15:58 /export/tmp/crash/vmdump.1
 
 So, I am writing this from reverted image :-(
>>> 
>>> User using VirtualBox needs to be member of 'vboxuser' group.
>>> 
>
>Hi,
>is it something new in VirtualBox 5? I run 4.3.30, user doesn't have
>any 
>special permissions.
>---
>System Administrator of Southern Federal University Computer Center
>
>
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss

It was there from very long ago. Certain device nodes maintained by virtualbox 
are owned by the vboxusers group, so people wanting usb passthrough, maybe raw 
host partition delegation, etc. and some other usecases must be members of the 
group.

Not every usecase needs it - so maybe you never cared ;)

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

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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Jim Klimov 
15 апреля 2016 г. 20:07:47 CEST, Nikola M  пишет:
>On 04/15/16 04:12 PM, Predrag Zečević - Unix Systems Administrator
>wrote:
>>
>> Trying it:
>> $ pfexec fmdump -Vp -u e701b777-689f-6be0-952a-9e382a0c23e5
>>
>> No luck this time - nothing has been displayed
>>
>> $ ls -al /export/tmp/crash/vmdump.1
>> -rw-r--r-- 1 root root 363M Apr 15 15:58 /export/tmp/crash/vmdump.1
>>
>> So, I am writing this from reverted image :-(
>
>User using VirtualBox needs to be member of 'vboxuser' group.
>
>You can make it by starting 'sudo users-admin' (or pfexec users-admin 
>with aproppriate/all priviledges)  and on 'Groups' tab, find 'vboxuser'
>
>, select Properies and add user(s) to the group.
>
>Try that.
>
>
>___
>openindiana-discuss mailing list
>openindiana-discuss@openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss

 Or something like (OTOH) `usermod -g vboxusers myusername` ;)

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

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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Nikola M 

On 04/15/16 04:12 PM, Predrag Zečević - Unix Systems Administrator wrote:


Trying it:
$ pfexec fmdump -Vp -u e701b777-689f-6be0-952a-9e382a0c23e5

No luck this time - nothing has been displayed

$ ls -al /export/tmp/crash/vmdump.1
-rw-r--r-- 1 root root 363M Apr 15 15:58 /export/tmp/crash/vmdump.1

So, I am writing this from reverted image :-(


User using VirtualBox needs to be member of 'vboxuser' group.

You can make it by starting 'sudo users-admin' (or pfexec users-admin 
with aproppriate/all priviledges)  and on 'Groups' tab, find 'vboxuser' 
, select Properies and add user(s) to the group.


Try that.


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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Nikola M 

On 04/15/16 11:54 AM, Predrag Zečević - Unix Systems Administrator wrote:
I OWN apologize, did not installed that VBOx version. Will give it try 
right now


Thanks for pointing to it!

But, on mentioned wiki page (was reading it for whole day): 
http://wiki.openindiana.org/oi/7.2+VirtualBox I did not seen that link...

From where did you got it? And what is exactly patched there?


Sorry, I somehow pasted link to Jim Klimov's Github page wrongly, it is 
https://github.com/jimklimov/vboxconfig_sh
Also I pasted patched my own package from Mega. VirtualBoxBinaries are 
also GPL so redistributable, I checked the other day.



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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Jim Klimov 
> But, on mentioned wiki page (was reading it for whole day): 
> http://wiki.openindiana.org/oi/7.2+VirtualBox I did not seen that link... 
> From where did you got it? And what is exactly patched there?

I believe this refers to my patch for vboxconfig.sh (see github links in the 
middle of Installation and Configuration Process chapter). Readme for the patch 
describes how to repackage VirtualBox SVR4 file including the config-script 
patch, and I'd *guess* minikola published the resulting file to simplify life 
for others.

HTH, Jim

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

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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Predrag Zečević - Unix Systems Administrator 

On 04/15/16 11:29 AM, Nikola M wrote:

On 04/14/16 09:02 AM, Predrag Zečević - Unix Systems Administrator wrote:

Hi all,

any one has an idea on this?

This morning I have updated /hipster to
[2016-04-14 08:46:26] solarix genunix: [ID 540533 kern.notice]
#015SunOS Release 5.11 Version illumos-cb92f41 64-bit

And things are now even worse: as soon as starting (any) VBox guest,
system freezes and stays like that. Tried wit re-installation, but it
does not help too.
No crash report, nothing. Nada.

/var/adm/messages also shows no more info,,, This is kind a
frustrating situation, since I had to revert and this is not good...
Also, google-ing resulted to no solution.


I have VirtualBox 5.0.16 (patched with Jom Klimov's
https://github.comSunOS oi-h2015 5.11 illumos-cb92f41 i86pc i386 i86pc
Solaris/jimklimov/vboxconfig_sh
(http://wiki.openindiana.org/oi/7.2+VirtualBox) , shared at:
https://mega.nz/#!7ZQHzTLa!02SMDWC7gyMS15oSQAwrnrM5AmD7gqNUNmujGSrCZwc
sha256sum:
726350d7057b6f8f478993f0a0103f8ec7ed19faa16bd3c2c598186a16d362fb
VirtualBox-5.0.16-SunOS-r105871-illumos.tar.gz
And it works right on 2 OI hipster machines with  illumos-cb92f41 , with
VT and without (I run xubuntu inside Vbox, XP and others), guests are
32bit, could try also 64 bit.

Try re-installing VirtualBox (might need to patch vboxconfig_sh to
uninstall) but you have patched Vbox on that Mega link if fresh installing.
What is your hardware? Mine is from C2Duo T5600 and Pentium E5200 era.



Hi again,

Just have tried again, this time with latest updates (and Jim's package):
[2016-04-15 15:58:39] solarix genunix: [ID 540533 kern.notice] #015SunOS 
Release 5.11 Version illumos-a526879 64-bit


and this time got this (in /var/adm/messages):
[2016-04-15 15:58:39] solarix genunix: [ID 864859 kern.notice] NOTICE: 
hald[355]: missing privilege "sys_mount" (euid = 0, syscall = 255) 
needed at secpolicy_fs_owner+0x2e#012
[2016-04-15 15:58:39] solarix genunix: [ID 864859 kern.notice] NOTICE: 
proftpd[838]: missing privilege "ALL" (euid = 21, syscall = 225) needed 
at devfs_unlocked_access+0x7e#012
[2016-04-15 15:58:38] solarix console-kit-daemon[844]: [ID 702911 
daemon.warning] WARNING: signal "open_session_request" (from 
"OpenSessionRequest") exported but not found in object class "CkSeat"#012
[2016-04-15 15:58:38] solarix console-kit-daemon[844]: [ID 702911 
daemon.warning] WARNING: signal "close_session_request" (from 
"CloseSessionRequest") exported but not found in object class "CkSeat"#012
[2016-04-15 15:58:39] solarix genunix: [ID 864859 kern.notice] NOTICE: 
reparsed[879]: missing privilege "sys_mount" (euid = 0, syscall = 255) 
needed at secpolicy_fs_owner+0x2e#012
[2016-04-15 15:58:38] solarix in.routed[885]: [ID 749644 daemon.notice] 
rge0 has a bad address 0.0.0.0
[2016-04-15 15:58:39] solarix savecore: [ID 570001 auth.error] reboot 
after panic: BAD TRAP: type=e (#pf Page fault) rp=ff0012579940 
addr=fd7ffb2ff660 occurred in module "" due to an illegal 
access to a user add

ress
[2016-04-15 15:58:39] solarix savecore: [ID 105003 auth.error] Saving 
compressed system crash dump in /export/tmp/crash/vmdump.1
[2016-04-15 15:58:39] solarix genunix: [ID 864859 kern.notice] NOTICE: 
fmd[987]: missing privilege "sys_mount" (euid = 0, syscall = 255) needed 
at secpolicy_fs_owner+0x2e#012
[2016-04-15 15:58:39] solarix genunix: [ID 864859 kern.notice] NOTICE: 
hald-addon-stora[1171]: missing privilege "sys_mount" (euid = 0, syscall 
= 255) needed at secpolicy_fs_owner+0x2e#012
[2016-04-15 15:58:39] solarix mac: [ID 435574 kern.info] NOTICE: rge0 
link up, 1000 Mbps, full duplex
[2016-04-15 15:58:40] solarix /sbin/dhcpagent[124]: [ID 778557 
daemon.warning] configure_v4_lease: no IP broadcast specified for rge0, 
making best guess
[2016-04-15 15:58:40] solarix in.routed[885]: [ID 847162 daemon.error] 4 
bytes of routing message left over
[2016-04-15 15:58:40] solarix in.routed[885]: [ID 606928 daemon.warning] 
sendto(rge0, 224.0.0.2): Network is unreachable
[2016-04-15 15:58:41] solarix ipf: [ID 774698 kern.info] IP Filter: 
v4.1.9, running.
[2016-04-15 15:58:41] solarix /sbin/dhcpagent[124]: [ID 732872 
daemon.error] dhcp_bound_complete: cannot add default router 
192.168.222.1 on rge0: File exists
[2016-04-15 15:58:43] solarix savecore: [ID 606186 auth.error] 
Decompress the crash dump with #012'savecore -vf /export/tmp/crash/vmdump.1'
[2016-04-15 15:58:43] solarix fmd: [ID 377184 daemon.error] SUNW-MSG-ID: 
SUNOS-8000-KL, TYPE: Defect, VER: 1, SEVERITY: Major#012EVENT-TIME: Fri 
Apr 15 15:58:43 CEST 2016#012PLATFORM: To-Be-Filled-By-O.E.M., CSN: -, 
HOSTNAME: solarix#012SOURCE: software-diagnosis, REV: 0.1#012EVENT-ID: 
e701b777-689f-6be0-952a-9e382a0c23e5#012DESC: The system has rebooted 
after a kernel panic.  Refer to http://illumos.org/msg/SUNOS-8000-KL for 
more information.#012AUTO-RESPONSE: The failed system image was dumped 
to the dump device.  If savecore is enabled (see dumpadm(1M)) a copy of 
the dump will be written to the

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Predrag Zečević - Unix Systems Administrator 

On 04/15/16 11:49 AM, Predrag Zečević - Unix Systems Administrator wrote:

On 04/15/16 11:29 AM, Nikola M wrote:

On 04/14/16 09:02 AM, Predrag Zečević - Unix Systems Administrator wrote:

Hi all,

any one has an idea on this?

This morning I have updated /hipster to
[2016-04-14 08:46:26] solarix genunix: [ID 540533 kern.notice]
#015SunOS Release 5.11 Version illumos-cb92f41 64-bit

And things are now even worse: as soon as starting (any) VBox guest,
system freezes and stays like that. Tried wit re-installation, but it
does not help too.
No crash report, nothing. Nada.

/var/adm/messages also shows no more info,,, This is kind a
frustrating situation, since I had to revert and this is not good...
Also, google-ing resulted to no solution.


I have VirtualBox 5.0.16 (patched with Jom Klimov's
https://github.comSunOS oi-h2015 5.11 illumos-cb92f41 i86pc i386 i86pc
Solaris/jimklimov/vboxconfig_sh
(http://wiki.openindiana.org/oi/7.2+VirtualBox) , shared at:
https://mega.nz/#!7ZQHzTLa!02SMDWC7gyMS15oSQAwrnrM5AmD7gqNUNmujGSrCZwc
sha256sum:
726350d7057b6f8f478993f0a0103f8ec7ed19faa16bd3c2c598186a16d362fb
VirtualBox-5.0.16-SunOS-r105871-illumos.tar.gz
And it works right on 2 OI hipster machines with  illumos-cb92f41 , with
VT and without (I run xubuntu inside Vbox, XP and others), guests are
32bit, could try also 64 bit.

Try re-installing VirtualBox (might need to patch vboxconfig_sh to
uninstall) but you have patched Vbox on that Mega link if fresh
installing.
What is your hardware? Mine is from C2Duo T5600 and Pentium E5200 era.



Hi Nikola,

I have tried with re-installation, AND I am using Jim's fix and IT is
working with this kernel:
$ uname -rosv
SunOS 5.11 illumos-258e862 Solaris

Until now, all updates went fine. Since then (some changes made after
approx 2016-03-29 makes it failing).

H/W is quiet new (I had to add extra Graphic, Network and USB 2.0 PCIe
cards to have OI working). Here extracts from 'dmidecode' utility:
8<---
BIOS Information
 Vendor: American Megatrends Inc.
 Version: P1.20
 Release Date: 09/03/2015
 Characteristics:
 PCI is supported
 BIOS is upgradeable
 BIOS shadowing is allowed
 Boot from CD is supported
 Selectable boot is supported
 BIOS ROM is socketed
 EDD is supported
 5.25"/1.2 MB floppy services are supported (int 13h)
 3.5"/720 kB floppy services are supported (int 13h)
 3.5"/2.88 MB floppy services are supported (int 13h)
 Print screen service is supported (int 5h)
 8042 keyboard services are supported (int 9h)
 Serial services are supported (int 14h)
 Printer services are supported (int 17h)
 ACPI is supported
 USB legacy is supported
 BIOS boot specification is supported
 Targeted content distribution is supported
 UEFI is supported

Base Board Information
 Manufacturer: ASRock
 Product Name: B150M Pro4S

Processor Information
 Socket Designation: CPUSocket
 Type: Central Processor
 Family: Core i5
 Manufacturer: Intel(R) Corporation
 ID: E3 06 05 00 FF FB EB BF
 Signature: Type 0, Family 6, Model 94, Stepping 3
 Flags:
 FPU (Floating-point unit on-chip)
 VME (Virtual mode extension)
 DE (Debugging extension)
 PSE (Page size extension)
 TSC (Time stamp counter)
 MSR (Model specific registers)
 PAE (Physical address extension)
 MCE (Machine check exception)
 CX8 (CMPXCHG8 instruction supported)
 APIC (On-chip APIC hardware supported)
 SEP (Fast system call)
 MTRR (Memory type range registers)
 PGE (Page global enable)
 MCA (Machine check architecture)
 CMOV (Conditional move instruction supported)
 PAT (Page attribute table)
 PSE-36 (36-bit page size extension)
 CLFSH (CLFLUSH instruction supported)
 DS (Debug store)
 ACPI (ACPI supported)
 MMX (MMX technology supported)
 FXSR (FXSAVE and FXSTOR instructions supported)
 SSE (Streaming SIMD extensions)
 SSE2 (Streaming SIMD extensions 2)
 SS (Self-snoop)
 HTT (Multi-threading)
 TM (Thermal monitor supported)
 PBE (Pending break enabled)
 Version: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz

Memory Device
 Array Handle: 0x0010
 Error Information Handle: Not Provided
 Total Width: 64 bits

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Predrag Zečević - Unix Systems Administrator 

On 04/15/16 11:29 AM, Nikola M wrote:

On 04/14/16 09:02 AM, Predrag Zečević - Unix Systems Administrator wrote:

Hi all,

any one has an idea on this?

This morning I have updated /hipster to
[2016-04-14 08:46:26] solarix genunix: [ID 540533 kern.notice]
#015SunOS Release 5.11 Version illumos-cb92f41 64-bit

And things are now even worse: as soon as starting (any) VBox guest,
system freezes and stays like that. Tried wit re-installation, but it
does not help too.
No crash report, nothing. Nada.

/var/adm/messages also shows no more info,,, This is kind a
frustrating situation, since I had to revert and this is not good...
Also, google-ing resulted to no solution.


I have VirtualBox 5.0.16 (patched with Jom Klimov's
https://github.comSunOS oi-h2015 5.11 illumos-cb92f41 i86pc i386 i86pc
Solaris/jimklimov/vboxconfig_sh
(http://wiki.openindiana.org/oi/7.2+VirtualBox) , shared at:
https://mega.nz/#!7ZQHzTLa!02SMDWC7gyMS15oSQAwrnrM5AmD7gqNUNmujGSrCZwc
sha256sum:
726350d7057b6f8f478993f0a0103f8ec7ed19faa16bd3c2c598186a16d362fb
VirtualBox-5.0.16-SunOS-r105871-illumos.tar.gz
And it works right on 2 OI hipster machines with  illumos-cb92f41 , with
VT and without (I run xubuntu inside Vbox, XP and others), guests are
32bit, could try also 64 bit.

Try re-installing VirtualBox (might need to patch vboxconfig_sh to
uninstall) but you have patched Vbox on that Mega link if fresh installing.
What is your hardware? Mine is from C2Duo T5600 and Pentium E5200 era.



Hi Nikola,

I have tried with re-installation, AND I am using Jim's fix and IT is 
working with this kernel:

$ uname -rosv
SunOS 5.11 illumos-258e862 Solaris

Until now, all updates went fine. Since then (some changes made after 
approx 2016-03-29 makes it failing).


H/W is quiet new (I had to add extra Graphic, Network and USB 2.0 PCIe 
cards to have OI working). Here extracts from 'dmidecode' utility:

8<---
BIOS Information
Vendor: American Megatrends Inc.
Version: P1.20
Release Date: 09/03/2015
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported

Base Board Information
Manufacturer: ASRock
Product Name: B150M Pro4S

Processor Information
Socket Designation: CPUSocket
Type: Central Processor
Family: Core i5
Manufacturer: Intel(R) Corporation
ID: E3 06 05 00 FF FB EB BF
Signature: Type 0, Family 6, Model 94, Stepping 3
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz

Memory Device
Array Handle: 0x0010
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: ChannelA-DIMM1
Bank

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-15 Thread Nikola M 

On 04/14/16 09:02 AM, Predrag Zečević - Unix Systems Administrator wrote:

Hi all,

any one has an idea on this?

This morning I have updated /hipster to
[2016-04-14 08:46:26] solarix genunix: [ID 540533 kern.notice] 
#015SunOS Release 5.11 Version illumos-cb92f41 64-bit


And things are now even worse: as soon as starting (any) VBox guest, 
system freezes and stays like that. Tried wit re-installation, but it 
does not help too.

No crash report, nothing. Nada.

/var/adm/messages also shows no more info,,, This is kind a 
frustrating situation, since I had to revert and this is not good... 
Also, google-ing resulted to no solution.


I have VirtualBox 5.0.16 (patched with Jom Klimov's 
https://github.comSunOS oi-h2015 5.11 illumos-cb92f41 i86pc i386 i86pc 
Solaris/jimklimov/vboxconfig_sh 
(http://wiki.openindiana.org/oi/7.2+VirtualBox) , shared at:

https://mega.nz/#!7ZQHzTLa!02SMDWC7gyMS15oSQAwrnrM5AmD7gqNUNmujGSrCZwc
sha256sum: 
726350d7057b6f8f478993f0a0103f8ec7ed19faa16bd3c2c598186a16d362fb 
VirtualBox-5.0.16-SunOS-r105871-illumos.tar.gz
And it works right on 2 OI hipster machines with  illumos-cb92f41 , with 
VT and without (I run xubuntu inside Vbox, XP and others), guests are 
32bit, could try also 64 bit.


Try re-installing VirtualBox (might need to patch vboxconfig_sh to 
uninstall) but you have patched Vbox on that Mega link if fresh installing.

What is your hardware? Mine is from C2Duo T5600 and Pentium E5200 era.


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

Re: [OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-14 Thread Predrag Zečević - Unix Systems Administrator 

Hi all,

any one has an idea on this?

This morning I have updated /hipster to
[2016-04-14 08:46:26] solarix genunix: [ID 540533 kern.notice] #015SunOS 
Release 5.11 Version illumos-cb92f41 64-bit


And things are now even worse: as soon as starting (any) VBox guest, 
system freezes and stays like that. Tried wit re-installation, but it 
does not help too.

No crash report, nothing. Nada.

/var/adm/messages also shows no more info,,, This is kind a frustrating 
situation, since I had to revert and this is not good... Also, 
google-ing resulted to no solution.


With best regards.
Predrag Zečević

On 04/ 6/16 04:35 PM, Predrag Zečević - Unix Systems Administrator wrote:

Hi all,

I have updated my /hipster installation from:
$ uname -rosv
SunOS 5.11 illumos-258e862 Solaris

to(today's one):
SunOS 5.11 illumos-a48d812 Solaris


As soon as I start VBox guest, kernel crashes... (which is not case with
this OLDER one - nothing else has changed).

Suggested command from /var/adm/messages
---8<--
...
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE:
reparsed[1153]: missing privilege "sys_mount" (euid = 0, syscall = 255)
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix savecore: [ID 570001 auth.error] reboot
after panic: BAD TRAP: type=e (#pf Page fault) rp=ff000f8bc940
addr=fd7ffcced660 occurred in module "" due to an illegal
access to a user address
[2016-04-06 16:05:47] solarix mac: [ID 469746 kern.info] NOTICE: e1000g0
registered
[2016-04-06 16:05:47] solarix isa: [ID 202937 kern.info] ISA-device:
pit_beep0
[2016-04-06 16:05:47] solarix genunix: [ID 936769 kern.info] pit_beep0
is /pci@0,0/isa@1f/pit_beep
[2016-04-06 16:05:47] solarix savecore: [ID 284810 auth.error] Panic
crashdump pending on dump device but dumpadm -n in effect; run
savecore(1M) manually to extract. Image UUID
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00.
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE:
fmd[1220]: missing privilege "sys_mount" (euid = 0, syscall = 255)
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix /sbin/dhcpagent[118]: [ID 778557
daemon.warning] configure_v4_lease: no IP broadcast specified for rge0,
making best guess
[2016-04-06 16:05:47] solarix in.routed[898]: [ID 847162 daemon.error] 4
bytes of routing message left over
[2016-04-06 16:05:48] solarix fmd: [ID 377184 daemon.error] SUNW-MSG-ID:
SUNOS-8000-KL, TYPE: Defect, VER: 1, SEVERITY: Major#012EVENT-TIME: Wed
Apr  6 16:05:47 CEST 2016#012PLATFORM: To-Be-Filled-By-O.E.M., CSN: -,
HOSTNAME: solarix#012SOURCE: software-diagnosis, REV: 0.1#012EVENT-ID:
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00#012DESC: The system has rebooted
after a kernel panic.  Refer to http://illumos.org/msg/SUNOS-8000-KL for
more information.#012AUTO-RESPONSE: The failed system image was dumped
to the dump device.  If savecore is enabled (see dumpadm(1M)) a copy of
the dump will be written to the savecore directory .#012IMPACT: There
may be some performance impact while the panic is copied to the savecore
directory.  Disk space usage by panics can be
substantial.#012REC-ACTION: If savecore is not enabled then please take
steps to preserve the crash image.#012Use 'fmdump -Vp -u
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00' to view more panic detail.  Please
refer to the knowledge article for additional information.
...
---8<--

shows:
---8<--
TIME   UUID SUNW-MSG-ID
Apr 06 2016 16:05:47.983398000 a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
SUNOS-8000-KL

   TIME CLASS ENA
   Apr 06 16:05:47.5043 ireport.os.sunos.panic.dump_pending_on_device
0x

nvlist version: 0
 version = 0x0
 class = list.suspect
 uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
 code = SUNOS-8000-KL
 diag-time = 1459951547 950718
 de = fmd:///module/software-diagnosis
 fault-list-sz = 0x1
 fault-list = (array of embedded nvlists)
 (start fault-list[0])
 nvlist version: 0
 version = 0x0
 class = defect.sunos.kernel.panic
 certainty = 0x64
 asru =
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
 resource =
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
 savecore-succcess = 0
 os-instance-uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
 panicstr = BAD TRAP: type=e (#pf Page fault)
rp=ff000f8bc940 addr=fd7ffcced660 occurred in module ""
due to an illegal access to a user address
 panicstack = unix:die+df () | unix:trap+1490 () |
unix:_cmntrap+e6 () | f8d09225 () | f8d07bf8 () |
f8d923d7 () | f8d081ea () | vboxdrv:supdrvIOCtl+17fd ()
| vboxdrv:VBoxDrvSolarisIOCtl+36c () | genunix:cdev_ioctl+39 () |
specfs:spec_ioctl+60 () | genunix:fop_ioctl+55 () | genunix:ioctl+9b ()
|

[OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-11 Thread Predrag Zečević - Unix Systems Administrator 

Hi all,

I have updated my /hipster installation from:
$ uname -rosv
SunOS 5.11 illumos-258e862 Solaris

to(today's one):
SunOS 5.11 illumos-a48d812 Solaris


As soon as I start VBox guest, kernel crashes... (which is not case with 
this OLDER one - i just did "pkg update").


Suggested command from /var/adm/messages
---8<--
...
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE: 
reparsed[1153]: missing privilege "sys_mount" (euid = 0, syscall = 255) 
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix savecore: [ID 570001 auth.error] reboot 
after panic: BAD TRAP: type=e (#pf Page fault) rp=ff000f8bc940 
addr=fd7ffcced660 occurred in module "" due to an illegal 
access to a user address
[2016-04-06 16:05:47] solarix mac: [ID 469746 kern.info] NOTICE: e1000g0 
registered
[2016-04-06 16:05:47] solarix isa: [ID 202937 kern.info] ISA-device: 
pit_beep0
[2016-04-06 16:05:47] solarix genunix: [ID 936769 kern.info] pit_beep0 
is /pci@0,0/isa@1f/pit_beep
[2016-04-06 16:05:47] solarix savecore: [ID 284810 auth.error] Panic 
crashdump pending on dump device but dumpadm -n in effect; run 
savecore(1M) manually to extract. Image UUID 
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00.
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE: 
fmd[1220]: missing privilege "sys_mount" (euid = 0, syscall = 255) 
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix /sbin/dhcpagent[118]: [ID 778557 
daemon.warning] configure_v4_lease: no IP broadcast specified for rge0, 
making best guess
[2016-04-06 16:05:47] solarix in.routed[898]: [ID 847162 daemon.error] 4 
bytes of routing message left over
[2016-04-06 16:05:48] solarix fmd: [ID 377184 daemon.error] SUNW-MSG-ID: 
SUNOS-8000-KL, TYPE: Defect, VER: 1, SEVERITY: Major#012EVENT-TIME: Wed 
Apr  6 16:05:47 CEST 2016#012PLATFORM: To-Be-Filled-By-O.E.M., CSN: -, 
HOSTNAME: solarix#012SOURCE: software-diagnosis, REV: 0.1#012EVENT-ID: 
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00#012DESC: The system has rebooted 
after a kernel panic.  Refer to http://illumos.org/msg/SUNOS-8000-KL for 
more information.#012AUTO-RESPONSE: The failed system image was dumped 
to the dump device.  If savecore is enabled (see dumpadm(1M)) a copy of 
the dump will be written to the savecore directory .#012IMPACT: There 
may be some performance impact while the panic is copied to the savecore 
directory.  Disk space usage by panics can be 
substantial.#012REC-ACTION: If savecore is not enabled then please take 
steps to preserve the crash image.#012Use 'fmdump -Vp -u 
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00' to view more panic detail.  Please 
refer to the knowledge article for additional information.

...
---8<--

shows:
---8<--
TIME   UUID SUNW-MSG-ID
Apr 06 2016 16:05:47.983398000 a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00 
SUNOS-8000-KL


  TIME CLASS ENA
  Apr 06 16:05:47.5043 ireport.os.sunos.panic.dump_pending_on_device 
0x


nvlist version: 0
version = 0x0
class = list.suspect
uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
code = SUNOS-8000-KL
diag-time = 1459951547 950718
de = fmd:///module/software-diagnosis
fault-list-sz = 0x1
fault-list = (array of embedded nvlists)
(start fault-list[0])
nvlist version: 0
version = 0x0
class = defect.sunos.kernel.panic
certainty = 0x64
asru = 
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
resource = 
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00

savecore-succcess = 0
os-instance-uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
panicstr = BAD TRAP: type=e (#pf Page fault) 
rp=ff000f8bc940 addr=fd7ffcced660 occurred in module "" 
due to an illegal access to a user address
panicstack = unix:die+df () | unix:trap+1490 () | 
unix:_cmntrap+e6 () | f8d09225 () | f8d07bf8 () | 
f8d923d7 () | f8d081ea () | vboxdrv:supdrvIOCtl+17fd () 
| vboxdrv:VBoxDrvSolarisIOCtl+36c () | genunix:cdev_ioctl+39 () | 
specfs:spec_ioctl+60 () | genunix:fop_ioctl+55 () | genunix:ioctl+9b () 
| unix:brand_sys_syscall+1f5 () |

crashtime = 1459951477
panic-time = April  6, 2016 04:04:37 PM CEST CEST
(end fault-list[0])

fault-status = 0x1
severity = Major
__ttl = 0x1
__tod = 0x570517bb 0x3a9d7670
---8<--

Moreover, page suggested to visit shows nothing at all: 
http://illumos.org/msg/SUNOS-8000-KL


Any ideas (had to revert back to old BE)?
With best regards.

--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:

[OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-11 Thread Predrag Zecevic 

Hi all,

I have updated my /hipster installation from:
$ uname -rosv
SunOS 5.11 illumos-258e862 Solaris

to(today's one):
SunOS 5.11 illumos-a48d812 Solaris


As soon as I start VBox guest, kernel crashes... (which is not case with
this OLDER one - nothing else has changed).

Suggested command from /var/adm/messages
---8<--
...
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE:
reparsed[1153]: missing privilege "sys_mount" (euid = 0, syscall = 255)
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix savecore: [ID 570001 auth.error] reboot
after panic: BAD TRAP: type=e (#pf Page fault) rp=ff000f8bc940
addr=fd7ffcced660 occurred in module "" due to an illegal
access to a user address
[2016-04-06 16:05:47] solarix mac: [ID 469746 kern.info] NOTICE: e1000g0
registered
[2016-04-06 16:05:47] solarix isa: [ID 202937 kern.info] ISA-device:
pit_beep0
[2016-04-06 16:05:47] solarix genunix: [ID 936769 kern.info] pit_beep0
is /pci@0,0/isa@1f/pit_beep
[2016-04-06 16:05:47] solarix savecore: [ID 284810 auth.error] Panic
crashdump pending on dump device but dumpadm -n in effect; run
savecore(1M) manually to extract. Image UUID
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00.
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE:
fmd[1220]: missing privilege "sys_mount" (euid = 0, syscall = 255)
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix /sbin/dhcpagent[118]: [ID 778557
daemon.warning] configure_v4_lease: no IP broadcast specified for rge0,
making best guess
[2016-04-06 16:05:47] solarix in.routed[898]: [ID 847162 daemon.error] 4
bytes of routing message left over
[2016-04-06 16:05:48] solarix fmd: [ID 377184 daemon.error] SUNW-MSG-ID:
SUNOS-8000-KL, TYPE: Defect, VER: 1, SEVERITY: Major#012EVENT-TIME: Wed
Apr  6 16:05:47 CEST 2016#012PLATFORM: To-Be-Filled-By-O.E.M., CSN: -,
HOSTNAME: solarix#012SOURCE: software-diagnosis, REV: 0.1#012EVENT-ID:
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00#012DESC: The system has rebooted
after a kernel panic.  Refer to http://illumos.org/msg/SUNOS-8000-KL for
more information.#012AUTO-RESPONSE: The failed system image was dumped
to the dump device.  If savecore is enabled (see dumpadm(1M)) a copy of
the dump will be written to the savecore directory .#012IMPACT: There
may be some performance impact while the panic is copied to the savecore
directory.  Disk space usage by panics can be
substantial.#012REC-ACTION: If savecore is not enabled then please take
steps to preserve the crash image.#012Use 'fmdump -Vp -u
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00' to view more panic detail.  Please
refer to the knowledge article for additional information.
...
---8<--

shows:
---8<--
TIME   UUID
SUNW-MSG-ID
Apr 06 2016 16:05:47.983398000 a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
SUNOS-8000-KL

  TIME CLASS ENA
  Apr 06 16:05:47.5043 ireport.os.sunos.panic.dump_pending_on_device
0x

nvlist version: 0
version = 0x0
class = list.suspect
uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
code = SUNOS-8000-KL
diag-time = 1459951547 950718
de = fmd:///module/software-diagnosis
fault-list-sz = 0x1
fault-list = (array of embedded nvlists)
(start fault-list[0])
nvlist version: 0
version = 0x0
class = defect.sunos.kernel.panic
certainty = 0x64
asru =
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
resource =
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
savecore-succcess = 0
os-instance-uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
panicstr = BAD TRAP: type=e (#pf Page fault)
rp=ff000f8bc940 addr=fd7ffcced660 occurred in module ""
due to an illegal access to a user address
panicstack = unix:die+df () | unix:trap+1490 () |
unix:_cmntrap+e6 () | f8d09225 () | f8d07bf8 () |
f8d923d7 () | f8d081ea () | vboxdrv:supdrvIOCtl+17fd ()
| vboxdrv:VBoxDrvSolarisIOCtl+36c () | genunix:cdev_ioctl+39 () |
specfs:spec_ioctl+60 () | genunix:fop_ioctl+55 () | genunix:ioctl+9b ()
| unix:brand_sys_syscall+1f5 () |
crashtime = 1459951477
panic-time = April  6, 2016 04:04:37 PM CEST CEST
(end fault-list[0])

fault-status = 0x1
severity = Major
__ttl = 0x1
__tod = 0x570517bb 0x3a9d7670
---8<--

Moreover, page suggested to visit shows nothing at all:
http://illumos.org/msg/SUNOS-8000-KL

Any ideas (had to revert back to old BE)?
With best regards.
--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH,

[OpenIndiana-discuss] /hipster: latest kernel updates cause crash when vbox guest is started

2016-04-11 Thread Predrag Zečević - Unix Systems Administrator 

Hi all,

I have updated my /hipster installation from:
$ uname -rosv
SunOS 5.11 illumos-258e862 Solaris

to(today's one):
SunOS 5.11 illumos-a48d812 Solaris


As soon as I start VBox guest, kernel crashes... (which is not case with 
this OLDER one - nothing else has changed).


Suggested command from /var/adm/messages
---8<--
...
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE: 
reparsed[1153]: missing privilege "sys_mount" (euid = 0, syscall = 255) 
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix savecore: [ID 570001 auth.error] reboot 
after panic: BAD TRAP: type=e (#pf Page fault) rp=ff000f8bc940 
addr=fd7ffcced660 occurred in module "" due to an illegal 
access to a user address
[2016-04-06 16:05:47] solarix mac: [ID 469746 kern.info] NOTICE: e1000g0 
registered
[2016-04-06 16:05:47] solarix isa: [ID 202937 kern.info] ISA-device: 
pit_beep0
[2016-04-06 16:05:47] solarix genunix: [ID 936769 kern.info] pit_beep0 
is /pci@0,0/isa@1f/pit_beep
[2016-04-06 16:05:47] solarix savecore: [ID 284810 auth.error] Panic 
crashdump pending on dump device but dumpadm -n in effect; run 
savecore(1M) manually to extract. Image UUID 
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00.
[2016-04-06 16:05:47] solarix genunix: [ID 864859 kern.notice] NOTICE: 
fmd[1220]: missing privilege "sys_mount" (euid = 0, syscall = 255) 
needed at secpolicy_fs_owner+0x2e#012
[2016-04-06 16:05:47] solarix /sbin/dhcpagent[118]: [ID 778557 
daemon.warning] configure_v4_lease: no IP broadcast specified for rge0, 
making best guess
[2016-04-06 16:05:47] solarix in.routed[898]: [ID 847162 daemon.error] 4 
bytes of routing message left over
[2016-04-06 16:05:48] solarix fmd: [ID 377184 daemon.error] SUNW-MSG-ID: 
SUNOS-8000-KL, TYPE: Defect, VER: 1, SEVERITY: Major#012EVENT-TIME: Wed 
Apr  6 16:05:47 CEST 2016#012PLATFORM: To-Be-Filled-By-O.E.M., CSN: -, 
HOSTNAME: solarix#012SOURCE: software-diagnosis, REV: 0.1#012EVENT-ID: 
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00#012DESC: The system has rebooted 
after a kernel panic.  Refer to http://illumos.org/msg/SUNOS-8000-KL for 
more information.#012AUTO-RESPONSE: The failed system image was dumped 
to the dump device.  If savecore is enabled (see dumpadm(1M)) a copy of 
the dump will be written to the savecore directory .#012IMPACT: There 
may be some performance impact while the panic is copied to the savecore 
directory.  Disk space usage by panics can be 
substantial.#012REC-ACTION: If savecore is not enabled then please take 
steps to preserve the crash image.#012Use 'fmdump -Vp -u 
a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00' to view more panic detail.  Please 
refer to the knowledge article for additional information.

...
---8<--

shows:
---8<--
TIME   UUID 
SUNW-MSG-ID
Apr 06 2016 16:05:47.983398000 a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00 
SUNOS-8000-KL


  TIME CLASS ENA
  Apr 06 16:05:47.5043 ireport.os.sunos.panic.dump_pending_on_device 
0x


nvlist version: 0
version = 0x0
class = list.suspect
uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
code = SUNOS-8000-KL
diag-time = 1459951547 950718
de = fmd:///module/software-diagnosis
fault-list-sz = 0x1
fault-list = (array of embedded nvlists)
(start fault-list[0])
nvlist version: 0
version = 0x0
class = defect.sunos.kernel.panic
certainty = 0x64
asru = 
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
resource = 
sw:///:path=/var/crash/solarix/.a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00

savecore-succcess = 0
os-instance-uuid = a9b1c6ba-b4e0-6ad5-d2f7-e59d3b946c00
panicstr = BAD TRAP: type=e (#pf Page fault) 
rp=ff000f8bc940 addr=fd7ffcced660 occurred in module "" 
due to an illegal access to a user address
panicstack = unix:die+df () | unix:trap+1490 () | 
unix:_cmntrap+e6 () | f8d09225 () | f8d07bf8 () | 
f8d923d7 () | f8d081ea () | vboxdrv:supdrvIOCtl+17fd () 
| vboxdrv:VBoxDrvSolarisIOCtl+36c () | genunix:cdev_ioctl+39 () | 
specfs:spec_ioctl+60 () | genunix:fop_ioctl+55 () | genunix:ioctl+9b () 
| unix:brand_sys_syscall+1f5 () |

crashtime = 1459951477
panic-time = April  6, 2016 04:04:37 PM CEST CEST
(end fault-list[0])

fault-status = 0x1
severity = Major
__ttl = 0x1
__tod = 0x570517bb 0x3a9d7670
---8<--

Moreover, page suggested to visit shows nothing at all: 
http://illumos.org/msg/SUNOS-8000-KL


Any ideas (had to revert back to old BE)?
With best regards.

--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail: