[OpenIndiana-discuss] Update boot environment - VirtualBox now causes reboot
Stephan Althaus
Stephan.Althaus at Duedinghausen.eu
Mon Jul 5 11:19:48 UTC 2021
On 7/5/21 12:16 PM, Andreas Wacknitz wrote:
> Am 05.07.21 um 11:56 schrieb Peter Tribble:
>> On Mon, Jul 5, 2021 at 10:14 AM russell <stream at willows7.myzen.co.uk>
>> wrote:
>>
>>> 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.
>>>
>> Has VirtualBox on OpenIndiana been rebuilt to account for the
>> following? If
>> not,
>> it presumably needs to be.
>>
>> https://illumos.topicbox.com/groups/discuss/T38b7ddf6f14b64a6/flag-day-for-kernel-modules-that-call-installctx
>>
> I can increment the COMPONENT_REVISION in order to rebuild the package.
> But I am not sure this is really the cause of the problems
> as it rebuilds without needing a patch (which was necessary for kvm).
>
> Andreas
>>
>>
>>> 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
>>>
>>>
>>> _______________________________________________
>>> openindiana-discuss mailing list
>>> openindiana-discuss at openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>
>
>
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
Hello!
i just rebuild virtualbox locally and installed,
there is no change in behaviour,
# pkg info virtualbox
Name: system/virtualbox
Summary: VirtualBox - general-purpose full virtualizer
Category: System/Virtualization
State: Installed
Publisher: userland
Version: 6.1.22
Branch: 2020.0.1.0
Packaging Date: July 5, 2021 at 11:24:01 AM
Last Install Time: January 26, 2021 at 09:01:31 PM
Last Update Time: July 5, 2021 at 11:31:42 AM
Size: 124.43 MB
FMRI:
pkg://userland/system/virtualbox@6.1.22-2020.0.1.0:20210705T112401Z
# fmdump -Vp -u f15ef788-1a6a-64c5-c784-ea41324948ed
TIME UUID
SUNW-MSG-ID
Jul 05 2021 14:14:52.801050000 f15ef788-1a6a-64c5-c784-ea41324948ed
SUNOS-8000-KL
TIME CLASS ENA
Jul 05 14:14:52.0350 ireport.os.sunos.panic.dump_pending_on_device
0x0000000000000000
nvlist version: 0
version = 0x0
class = list.suspect
uuid = f15ef788-1a6a-64c5-c784-ea41324948ed
code = SUNOS-8000-KL
diag-time = 1625487292 661428
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/fuji/.f15ef788-1a6a-64c5-c784-ea41324948ed
resource =
sw:///:path=/var/crash/fuji/.f15ef788-1a6a-64c5-c784-ea41324948ed
savecore-succcess = 0
os-instance-uuid = f15ef788-1a6a-64c5-c784-ea41324948ed
panicstr = BAD TRAP: type=e (#pf Page fault)
rp=fffffe003d8651d0 addr=fffffe2d30f47010
panicstack = unix:real_mode_stop_cpu_stage2_end+c47d ()
| unix:trap+1169 () | unix:cmntrap+e9 () | unix:bzero+358 () |
zfs:arc_read+571 () | zfs:dbuf_read_impl+45a () | zfs:dbuf_read+e6 () |
zfs:dmu_buf_will_dirty_impl+c4 () | zfs:dmu_buf_will_dirty+13 () |
zfs:dmu_write_impl+45 () | zfs:dmu_write+da () |
zfs:space_map_write_intro_debug+cf () | zfs:space_map_write_impl+60 () |
zfs:space_map_write+e5 () | zfs:metaslab_flush+1ad () |
zfs:spa_flush_metaslabs+194 () | zfs:spa_sync_iterate_to_convergence+135
() | zfs:spa_sync+2f6 () | zfs:txg_sync_thread+1f5 () |
unix:thread_start+b () |
crashtime = 1625487108
panic-time = Mon Jul 5 14:11:48 2021 CEST
(end fault-list[0])
fault-status = 0x1
severity = Major
__ttl = 0x1
__tod = 0x60e2f7bc 0x2fbf0d90
.. what irritates me is that there are many zfs: in the stack.. maybe
this is an unrelated bug (??) (i have no raidz2 pool with 8 disks)
Greetings,
Stephan
.
More information about the openindiana-discuss
mailing list