[OpenIndiana-discuss] Update boot environment - VirtualBox now causes reboot

[russell]

Good Morning,

Created a new BE this morning 2021-07-05 08:43 with latest Hipster 
download, system booted normally and was able to use all my normal 
desktop applications. My last update was on the 2021-06-24 20:51

Started VirtualBox, the list of VMs appeared, I attempted to start a VM 
this immediately reported an error, locked the system which eventually 
rebooted.

The VM that failed to start generated the following log entry


00:00:02.755860 Installed Extension Packs:
00:00:02.755870   Oracle VM VirtualBox Extension Pack (Version: 6.1.22 
r144080; VRDE Module: VBoxVRDP)
00:00:02.756476 Console: Machine state changed to 'Starting'
00:00:02.779587 Qt version: 5.12.10

This is completely different from a normal start found in VBoz.log.1

00:00:00.712952 VirtualBox VM 6.1.22 r144080 solaris.amd64 (Jun 5 2021 
12:16:14) release log
00:00:00.712954 Log opened 2021-06-19T13:40:04.770473000Z
00:00:00.712954 Build Type: release
00:00:00.712958 OS Product: SunOS
00:00:00.712958 OS Release: 5.11
00:00:00.712959 OS Version: illumos-76e6cd87e3
00:00:00.713027 DMI Product Name: MS-7C56
00:00:00.713053 DMI Product Version: 1.0
00:00:00.713056 Firmware type: failed - VERR_NOT_SUPPORTED
00:00:00.713552 Host RAM: 32648MB (31.8GB) total, 22793MB (22.2GB) available
00:00:00.713555 Executable: /opt/VirtualBox/amd64/VirtualBoxVM
00:00:00.713555 Process ID: 1752
00:00:00.713556 Package type: SOLARIS_64BITS_GENERIC (OSE)
00:00:00.732246 Installed Extension Packs:
00:00:00.732261   Oracle VM VirtualBox Extension Pack (Version: 6.1.22 
r144080; VRDE Module: VBoxVRDP)
00:00:00.732887 Console: Machine state changed to 'Starting'
00:00:00.752406 Qt version: 5.12.10
00:00:00.752418 X11 Window Manager code: 4
00:00:00.756364 GUI: UIMediumEnumerator: Medium-enumeration finished!

I checked to make sure that the entries in /etc/system.d were present in 
the new BE and it includes the /etc/system.d/smap  with the entry "set 
disable_smap = 1" and /etc/system.d/hma with "set hma_disable = 1".

Is any one else experiencing the same problem or knows how to correct?

TIA

Russell