Any guest on 6.1.50 VB fail to start / crash VB or the host

[Cubytus32]

I have various VM, either Windows, Linux-es and Mac OS X running inside VirtualBox 6.1.50 on a 2012 MBP (Mojave host). Guests are stored on an external SSD.

I remember running them successfully at the end of last month.

However, trying to start any of them today (mostly for routine guest maintenance) resulted in a crash, either in the guest, in VM itself, or, more rarely, in the host (kernel panic) - Even in a running state, it's not unusual for VirtualBox to crash the host.

Symptoms:
Windows 7 in Safe Mode: blue screen with PAGE_FAULT_IN_NONPAGED_AREA
Windows 7 in Normal mode: blue screen with STOP: 0X0000007E errror code
Windows 10 in Normal mode: immediately crashes
Win10 VBox.log:

Win10 test-2024-03-08-21-05-34.log

(94.13 KiB) Downloaded 8 times

Linux Mint, MX Linux: immediately terminates with "forbidden" sign. Host registers a crash:
Linux Mint VBox.log after crash:

Linux Mint-2024-03-08-23-06-24.log.zip

(19.66 KiB) Downloaded 6 times

MX Linux VBox.log after crash:

MX Linux flux-2024-03-08-23-08-21.log.zip

(18.44 KiB) Downloaded 7 times

Code: Select all

Process:               ReportCrash [2919]
Path:                  /System/Library/CoreServices/ReportCrash
Identifier:            ReportCrash
Version:               938.29
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           ReportCrash [2919]
User ID:               501

Date/Time:             2024-03-08 23:06:24.851 -0500
OS Version:            Mac OS X 10.14.6 (18G9323)
Report Version:        12
Anonymous UUID:        B11A7CD1-F439-815A-1E3E-7E11EB227165


Time Awake Since Boot: 7500 seconds

System Integrity Protection: enabled

Crashed Thread:        10

Exception Type:        EXC_CRASH (Code Signature Invalid)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace CODESIGNING, Code 0x2
[…]

Other, unrelated symptom: from the GUI, VirtualBox refuses to check for updates with error "Wrong SSL certificate format"
(Proposed solution from 10 years ago doesn't work anymore)

Already tried:
rebooted.
uninstalling / reinstalling VirtualBox;
Manually setting back time to last month, just in case an unknown certificate expired in the meantime
to no avail.

Any idea what would cause a generalized failure like that?

[fth0]

Any idea what would cause a generalized failure like that?

Any idea what you changed on the host side?

Please provide a few (zipped) macOS Crash Logs.