Cannot start any VM after upgrade to Sonoma 14.2

Discussions related to using VirtualBox on Mac OS X hosts.
Locked
mucuser
Posts: 3
Joined: 21. Jan 2020, 12:44

Cannot start any VM after upgrade to Sonoma 14.2

Post by mucuser »

After upgrading to macos Sonoma 14.2 (23C64)I with 7.0.12 r159484 (Qt5.15.2) I cannot start any VM anymore, neither from a saved nor unsaved state, Linux or Windows VM.

The error I get is:
The virtual machine 'xxxxx' has terminated unexpectedly during startup because of signal 9.
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}
Snippet from the Crash report:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: 2333930F-1639-48D0-AF98-4435220BD59A
CrashReporter Key: 12614E48-DE03-83BA-92E5-4ECA36D4D3CD
Hardware Model: MacBookPro16,1
Process: VirtualBoxVM [4779]
Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier: org.virtualbox.app.VirtualBoxVM
Version: 7.0.12 (7.0.12)
Code Type: X86-64 (Native)
Role: Unspecified
Parent Process: VBoxSVC [4269]
Coalition: org.virtualbox.app.VirtualBox [2939]
Responsible Process: VirtualBox [4265]

Date/Time: 2023-12-12 13:41:16.7612 +0100
Launch Time: 2023-12-12 13:41:16.7166 +0100
OS Version: macOS 14.2 (23C64)
Release Type: User
Report Version: 104

Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0

Thread 0 Crashed:
0 0x1186e4020 _dyld_start + 0
1 0x1097f9000 ???


Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ff7b6706ad8
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00000001186e4020 rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0


Binary Images:
0x1186df000 - 0x11877efff (*) <ab17bf63-259b-3b48-8d70-863166a2191c> ???
0x1097f9000 - 0x1098b8fff (*) <3cd814a7-8f64-3fd9-8dc3-74f3d9b5ba02> ???
0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

Error Formulating Crash Report:
dyld_process_snapshot_get_shared_cache failed

Is this a known issue others experience as well? isther a know workaround/solution?
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Cannot start any VM after upgrade to Sonoma 14.2

Post by scottgus1 »

Did you uninstall and reinstall Virtualbox? Major host OS updates usually require such a un/reinstall.
mucuser
Posts: 3
Joined: 21. Jan 2020, 12:44

Re: Cannot start any VM after upgrade to Sonoma 14.2

Post by mucuser »

Hi,

indeed I just did and fortunately it helped. Using VB for 15 years now and this was the first time I had to re-install after an OS update.

Thanks!
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Cannot start any VM after upgrade to Sonoma 14.2

Post by scottgus1 »

Great! Glad you're up and running.
Lesw
Posts: 1
Joined: 12. Dec 2023, 20:27

Re: Cannot start any VM after upgrade to Sonoma 14.2

Post by Lesw »

The Uninstall/Reinstall worked for my Windows and Linux clients on an Intel iMac host.
DoubleUGee
Posts: 4
Joined: 28. Sep 2023, 11:42

Re: Cannot start any VM after upgrade to Sonoma 14.2

Post by DoubleUGee »

Thanks for the hint.
The Uninstall/Reinstall worked for my MacBook Pro (15,2) host too.
hamfred
Posts: 1
Joined: 27. Dec 2023, 12:25

Re: Cannot start any VM after upgrade to Sonoma 14.2

Post by hamfred »

Yes, I can also confirm that a reinstallation works, Thanx! You can uninstall the previous version by calling the uninstall script that appears in the GUI of the (new) installer in the bottom right corner.
Locked