Page 1 of 8
VirtualBox crashes after upgrading to macOS Catalina (#18990)
Posted: 8. Oct 2019, 02:56
by GMan7
ModEdit;
6.0.14 got released on 2019-10-16.
Try it out before posting in the thread.
Tying the thread to ticket #18990: Catalina host with Win 10 VM crashes
I Just upgraded to Catalina 10.15 and did the steps described with the same results using (VirtualBox-6.0.12-133076-OSX). The VirtualBox App runs fine but the Virtual Machine keeps throwing the NS_Error_Failure when I try to launch the virtual machine that previously worked.
VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 12:00
by vurgoe
After upgrading to macOS Catalina, every time I start the guest, everything seems OK. But it will crash in a few minutes showing the error
You must specify a machine to start, using the command line. Usage: VirtualBoxVM --startvm <name|UUID> ...
I've looked into the logs, no error information.
Is there someone who can help? If you need more information, let me know.
Host System: macOS 10.15 Catalina
Guest System: Windows 7
VirtualBox: 6.0.8
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 13:12
by prad007
I'm also facing the same issue after upgrade... Please share the solution in case if you found it already.
Windows 2016 Guest Error after 6.0.12 Update
Posted: 8. Oct 2019, 13:27
by Moises Goncalves
I have a Mac OS Catalina 10.15 Host and a Windows 2016 Guest. Everything was running fine before the 6.0.12 upgrade.
Now when I try to execute any Request from the Host to the Guest Chrome - IIS, the Guest crashes and I get the following error.
Code: Select all
Process: VirtualBoxVM [840]
Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier: org.virtualbox.app.VirtualBoxVM
Version: 6.0.12 (6.0.12)
Code Type: X86-64 (Native)
Parent Process: VBoxSVC [795]
Responsible: VirtualBox [788]
User ID: 501
Date/Time: 2019-10-08 11:57:50.959 +0200
OS Version: Mac OS X 10.15 (19A583)
Report Version: 12
Anonymous UUID: CDA5A24B-A6D8-0067-14B7-758F45E3A688
Time Awake Since Boot: 880 seconds
System Integrity Protection: enabled
Crashed Thread: 37 Dispatch queue: com.apple.root.default-qos.overcommit
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000007fc0a5286d0
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [840]
VM Regions Near 0x7fc0a5286d0:
MALLOC_LARGE 00000003474b9000-00000003476b9000 [ 2048K] rw-/rwx SM=PRV
-->
STACK GUARD 0000700005d9e000-0000700005d9f000 [ 4K] ---/rwx SM=NUL stack guard for thread 35
Thread 0:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtGuiVBox 0x000000010fd06b25 0x10f93e000 + 3967781
1 org.qt-project.QtGuiVBox 0x000000010fb8be09 0x10f93e000 + 2416137
2 org.qt-project.QtGuiVBox 0x000000010fb8d5c7 QRasterPaintEngine::fillRect(QRectF const&, QSpanData*) + 247
3 org.qt-project.QtGuiVBox 0x000000010fbb0821 QPainter::fillRect(QRect const&, QColor const&) + 145
4 libqcocoa.dylib 0x000000011646d6fe QCocoaBackingStore::beginPaint(QRegion const&) + 142
5 org.qt-project.QtGuiVBox 0x000000010fb07d3d QBackingStore::beginPaint(QRegion const&) + 365
6 org.qt-project.QtWidgetsVBox 0x000000010ff2c7e5 0x10ff0d000 + 128997
7 org.qt-project.QtWidgetsVBox 0x000000010ff2ad21 0x10ff0d000 + 122145
8 org.qt-project.QtWidgetsVBox 0x000000010ff50fdc QWidgetPrivate::syncBackingStore() + 236
9 org.qt-project.QtWidgetsVBox 0x000000010ff60ed1 QWidget::event(QEvent*) + 2609
10 org.qt-project.QtWidgetsVBox 0x0000000110072a8a QMainWindow::event(QEvent*) + 858
11 VirtualBoxVM.dylib 0x000000010f24b775 0x10f209000 + 272245
12 org.qt-project.QtWidgetsVBox 0x000000010ff1e766 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 294
13 org.qt-project.QtWidgetsVBox 0x000000010ff21cde QApplication::notify(QObject*, QEvent*) + 8558
14 org.qt-project.QtCoreVBox 0x000000010f548467 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 167
15 org.qt-project.QtWidgetsVBox 0x000000010ff286ba 0x10ff0d000 + 112314
16 org.qt-project.QtWidgetsVBox 0x000000010ff29202 0x10ff0d000 + 115202
17 org.qt-project.QtWidgetsVBox 0x000000010ff6420f QWidget::repaint(QRect const&) + 207
18 org.qt-project.QtWidgetsVBox 0x000000010ff64134 QWidget::repaint() + 52
19 org.qt-project.QtCoreVBox 0x000000010f57c808 QMetaObject::activate(QObject*, int, int, void**) + 3048
20 VirtualBoxVM.dylib 0x000000010f2c7ec3 0x10f209000 + 782019
21 org.qt-project.QtCoreVBox 0x000000010f57c808 QMetaObject::activate(QObject*, int, int, void**) + 3048
22 VirtualBoxVM.dylib 0x000000010f2c5b4c 0x10f209000 + 772940
23 VirtualBoxVM.dylib 0x000000010f22edf4 0x10f209000 + 155124
24 org.qt-project.QtCoreVBox 0x000000010f54876e QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 222
25 org.qt-project.QtWidgetsVBox 0x000000010ff1e751 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 273
26 org.qt-project.QtWidgetsVBox 0x000000010ff21cde QApplication::notify(QObject*, QEvent*) + 8558
27 org.qt-project.QtCoreVBox 0x000000010f548467 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 167
28 org.qt-project.QtWidgetsVBox 0x000000010ff1c3b1 QApplicationPrivate::setFocusWidget(QWidget*, Qt::FocusReason) + 273
29 org.qt-project.QtWidgetsVBox 0x000000010ff1d59a QApplication::setActiveWindow(QWidget*) + 1146
30 org.qt-project.QtWidgetsVBox 0x000000010ff1d9e2 QApplicationPrivate::notifyActiveWindowChange(QWindow*) + 50
31 org.qt-project.QtGuiVBox 0x000000010f968f7a QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) + 618
32 org.qt-project.QtGuiVBox 0x000000010f9652e7 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 1383
33 org.qt-project.QtGuiVBox 0x000000010f94efeb QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 411
34 libqcocoa.dylib 0x00000001164840b1 QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 33
35 com.apple.CoreFoundation 0x00007fff35027a21 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
36 com.apple.CoreFoundation 0x00007fff350279c0 __CFRunLoopDoSource0 + 103
37 com.apple.CoreFoundation 0x00007fff3500af84 __CFRunLoopDoSources0 + 209
38 com.apple.CoreFoundation 0x00007fff3500a590 __CFRunLoopRun + 1272
39 com.apple.CoreFoundation 0x00007fff35009e13 CFRunLoopRunSpecific + 499
40 com.apple.HIToolbox 0x00007fff33b96b2d RunCurrentEventLoopInMode + 292
41 com.apple.HIToolbox 0x00007fff33b9686d ReceiveNextEventCommon + 600
42 com.apple.HIToolbox 0x00007fff33b965f7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
43 com.apple.AppKit 0x00007fff3222cac4 _DPSNextEvent + 990
44 com.apple.AppKit 0x00007fff3222b834 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
45 com.apple.AppKit 0x00007fff32225fd4 -[NSApplication run] + 658
46 libqcocoa.dylib 0x0000000116482eed QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2205
47 org.qt-project.QtCoreVBox 0x000000010f544791 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
48 org.qt-project.QtCoreVBox 0x000000010f548b4a QCoreApplication::exec() + 346
49 VirtualBoxVM.dylib 0x000000010f210f93 TrustedMain + 1315
50 org.virtualbox.app.VirtualBoxVM 0x000000010eb56d36 0x10eb53000 + 15670
51 libdyld.dylib 0x00007fff6c309405 start + 1
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 768K 6
Activity Tracing 256K 1
CG backing stores 29.1M 5
CG image 112K 1
CG raster data 140K 3
CoreAnimation 88K 7
CoreGraphics 8K 1
CoreImage 36K 5
CoreServices 152K 1
CoreUI image data 1504K 13
Dispatch continuations 16.0M 1
Foundation 4K 1
Kernel Alloc Once 8K 1
MALLOC 8.6G 4511
MALLOC guard page 32K 8
MALLOC_LARGE (reserved) 476K 7 reserved VM address space (unallocated)
Memory Tag 242 12K 1
STACK GUARD 56.1M 39
Stack 26.2M 39
VM_ALLOCATE 20.0M 49
__DATA 33.7M 341
__DATA_CONST 24K 2
__FONT_DATA 4K 1
__LINKEDIT 354.3M 28
__OBJC_RO 31.8M 1
__OBJC_RW 1764K 2
__TEXT 254.8M 334
__UNICODE 564K 1
mapped file 52.1M 24
shared memory 640K 14
=========== ======= =======
TOTAL 9.5G 5448
TOTAL, minus reserved VM space 9.5G 5448
Model: MacBookPro11,4, BootROM 195.0.0.0.0, 4 processors, Quad-Core Intel Core i7, 2,2 GHz, 16 GB, SMC 2.29f24
Graphics: kHW_IntelIrisProItem, Intel Iris Pro, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x31364B544631473634485A2D314736453120
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x31364B544631473634485A2D314736453120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), Broadcom BCM43xx 1.0 (7.77.105.1 AirPortDriverBrcmNIC-1429)
Bluetooth: Version 7.0.0f8, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0256G, 251 GB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1
Re: start new VM report NS_ERROR_FAILURE (0x80004005)
Posted: 8. Oct 2019, 13:34
by GMan7
I tried the command line and it gave me a "Segmentation fault: 11" error without starting the VM.
Windows guests on VBMac Catalina hosts
Posted: 8. Oct 2019, 16:49
by Wallym
I have just upgraded my Macbook Pro 2018 to Catalina. I start up VirtualBox. I start one of my Windows guests. The guest starts, I login, and then the VB Guest crashes. I've tried this 5 or 6 times, all with similar results. I've added my log file as an attachment. I'm quite at a loss regarding how to resolve this. Any ideas? TIA.
Wally
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 17:00
by JuniorBR
Code: Select all
Process: VirtualBoxVM [1694]
Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
Identifier: org.virtualbox.app.VirtualBoxVM
Version: 6.0.12 (6.0.12)
Code Type: X86-64 (Native)
Parent Process: VBoxSVC [1693]
Responsible: VirtualBox [1689]
User ID: 501
Date/Time: 2019-10-08 11:53:29.760 -0300
OS Version: Mac OS X 10.15 (19A583)
Report Version: 12
Anonymous UUID: 3F0827BD-8E28-7E22-2E9B-545A734F0668
Time Awake Since Boot: 4000 seconds
System Integrity Protection: enabled
Crashed Thread: 2 Dispatch queue: com.apple.root.default-qos.overcommit
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1694]
VM Regions Near 0:
-->
__TEXT 0000000105c4d000-0000000105c6f000 [ 136K] r-x/rwx SM=COW /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
Model: MacBookAir7,2, BootROM 190.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 1,8 GHz, 8 GB, SMC 2.27f2
Graphics: kHW_IntelHDGraphics6000Item, Intel HD Graphics 6000, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.77.105.1 AirPortDriverBrcmNIC-1429)
Bluetooth: Version 7.0.0f8, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0128G, 121,33 GB
USB Device: USB 3.0 Bus
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Hub
USB Device: USB Hub 2.0
USB Device: USB Keyboard
Thunderbolt Bus: MacBook Air, Apple Inc., 27.2
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 17:32
by vurgoe
I also try to upgrade to VirtualBox 6.0.12. It still doesn't work because of the same issue
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 18:08
by spacebug
Same here.
The guest crashes when klicking outside the client window.
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 18:20
by Doug_M
I'm getting the crashing a few minutes after launching a guest (Win10 in this case) as well as the guest crashing (instantly aborts) when clicking outside the VM. The macOS crash report and VB log are attached.
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 19:06
by socratis
The latest release VirtualBox 6.0.12 and 10.15 don't play nice. You can either get the latest
test build (after disabling SIP) which addresses the issue, or wait until
6.0.14 gets released on
2019-10-15.
See also:
viewtopic.php?f=39&t=93419 and the
solution that involves "Input Monitoring".
@'Gman7', 'Wallym', 'Moises Goncalves'
I merged your threads with the prominent one that deals with that issue.
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 20:38
by socratis
Another thing to try is to enter the command:
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 21:04
by msw_116
I too had a similar issue with a Windows 10 VM crashing when launching VirtualBox (version 6.0.12 r133076) and reading this thread gave me an idea. I've replicated what I did here.
- Close Virtual Box (and ensure it's gone from the dock)
- Go to System Preferences > Security & Privacy
- Click on Privacy
- In the left-hand pane, select Full Disk Access
- Using the + button, find the VirtualBox.app file (in the Applications folder) and double-click on it
It would seem my issue was with the new Catalina security and my Virtual Box couldn't access the files it needed to run. Clicking now on my VM causes it to open normally and not crash!
Re: VirtualBox crashes after upgrading to macOS Catalina
Posted: 8. Oct 2019, 21:13
by socratis
It seems that Apple is going overboard with this security stuff. Both for developers (signed kexts, notarization) and end-users (Allow this, Allow that, Allow ...).
Re: updated to Catalina: can't launch VM
Posted: 9. Oct 2019, 01:35
by hulksmash
Same problem here w/ VirtualBox 6.0.12 and osx 10.15. Was working fine before upgrading OSX to 10.15. Guaranteed to crash as soon as I switch windows. Is there any update available for this?