Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Discussions related to using VirtualBox on Mac OS X hosts.
ElMaSkA007
Posts: 46
Joined: 3. Oct 2021, 13:42
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 11, Fedora 38, RHEL 8 and Ubuntu 22.04.2

Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by ElMaSkA007 »

Hello everyone.

After upgrading from VBox version 6.1.40 to 7.0.2, I get several spontaneous crashes from my Windows 10 VM. Also these crashes I have been experiencing in previous versions of VBox but I did not decide to post any thread until now.

Before these crashes happened to me, and in version 7.0.2 of VBox, I was able to apply the WA by disabling the 3D acceleration option according to the error message NS_ERROR_FAILURE (0X80004005) (which I suppose is a problem that is still not solved) . After all this, I still don't understand why my Win 10 VM has these spontaneous crashes.

I am attaching the necessary logs for analysis and would kindly ask someone knowledgeable about the matter to look at them. What I have been able to observe from the logs is that the message began to appear very frequently:

Code: Select all

Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
I also send the bug report that macOS collects every time the Win 10 VM crashes.

Thanks in advance.
Attachments
2022-11-15-09-09-33-bugreport.tgz
VM Windows 10 bugreport 2022-11-15
(182.43 KiB) Downloaded 5 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by scottgus1 »

ElMaSkA007 wrote:according to the error message NS_ERROR_FAILURE (0X80004005)
Ah yessssssssss, good ol' NS_ERROR_FAILURE . viewtopic.php?f=9&t=107724
*************************

I'm no Mac host guru, but I did see something that might help such gurus:

Last line of latest vbox.log:
02:41:21.223487 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
Last lines of latest VboxSVC.log:
02:41:54.404916 MainPower Host suspending: Paused 0 VMs
03:09:40.965763 MainPower Host resumed: Resumed 0 VMs
The similarity between timestamps makes me wonder if you 'slept' the Mac (or it slept itself) right before the VM crashed, or you found the VM crashed when the host woke up?
ElMaSkA007
Posts: 46
Joined: 3. Oct 2021, 13:42
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 11, Fedora 38, RHEL 8 and Ubuntu 22.04.2

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by ElMaSkA007 »

Hi scottgus1 and thanks for your reply.

Those last few lines you've seen in the logs reminded me that yes, my Mac went to sleep autonomously and I woke it up later, shortly after I saw the VM crash at the very moment it happened.

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

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by scottgus1 »

If that's always the way it happens, then the immediate workaround is to not let the Mac go to sleep.

Why the crash happens, I have no idea. We'll have to wait for a Mac guru to come along.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by fth0 »

scottgus1 wrote:The similarity between timestamps [...]
... doesn't play a role when the starting times are more than 12 hours apart. :wink:
ElMaSkA007
Posts: 46
Joined: 3. Oct 2021, 13:42
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 11, Fedora 38, RHEL 8 and Ubuntu 22.04.2

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by ElMaSkA007 »

scottgus1 wrote:If that's always the way it happens, then the immediate workaround is to not let the Mac go to sleep.

Why the crash happens, I have no idea. We'll have to wait for a Mac guru to come along.
This is how it was when I had it set up before.

I hope there is someone specialized in VBox on macOS to shed a little more light on this and if they could confirm if there is any open ticket about it.

Regards.
ElMaSkA007
Posts: 46
Joined: 3. Oct 2021, 13:42
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 11, Fedora 38, RHEL 8 and Ubuntu 22.04.2

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by ElMaSkA007 »

fth0 wrote:
scottgus1 wrote:The similarity between timestamps [...]
... doesn't play a role when the starting times are more than 12 hours apart. :wink:
Excuse my ignorance, I didn't quite understand the last thing you posted, could you be more specific?

Thanks in advance.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by fth0 »

ElMaSkA007 wrote:I didn't quite understand the last thing you posted, could you be more specific?
With pleasure:
VBoxSVC.log file wrote:
00:00:00.028652 main     VirtualBox XPCOM Server 7.0.2 r154219 darwin.amd64 (Oct 19 2022 20:17:53) release log
00:00:00.028656 main     Log opened 2022-11-14T22:14:42.690142000Z
[...]
02:41:54.404916 MainPower Host suspending: Paused 0 VMs
VBox.log file wrote:
00:00:02.000429 VirtualBox VM 7.0.2 r154219 darwin.amd64 (Oct 19 2022 20:17:53) release log
00:00:02.000431 Log opened 2022-11-14T10:00:31.210255000Z
[...]
02:41:21.223487 Shared Clipboard: Signalling host about guest clipboard data failed with VERR_NOT_FOUND
The relative timestamps compared are very similar, but they are relative to the time when the respective log file was started. In consequence the two events happened more than 12 hours apart from each other. I could be wrong in that it doesn't play a role, though.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by scottgus1 »

fth0 wrote:00:00:00.028656 main Log opened 2022-11-14T22:14:42.690142000Z
fth0 wrote:00:00:02.000431 Log opened 2022-11-14T10:00:31.210255000Z
Good point, fth0! I was wondering how you found that out. Thanks!
ElMaSkA007
Posts: 46
Joined: 3. Oct 2021, 13:42
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 11, Fedora 38, RHEL 8 and Ubuntu 22.04.2

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by ElMaSkA007 »

Hi again good people.

Unfortunately just now that I was using my Win 10 VM it crashed within minutes of resizing the VM window.

I also want to mention that there is a lot of click in the VM audio as the sound is not totally pure.

I attach new logs so you could analyze it. The truth is that this is being a bit worrying and at the same time disappointing with VBox...

Thanks in advance.
Attachments
2022-11-18-08-32-51-bugreport.tgz
Logs after resizing the VM window
(171.74 KiB) Downloaded 3 times
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by fth0 »

VBoxSVC.log file wrote:
00:09:13.070583 Watcher  Reaper: Pid 50668 (c5ec) was signalled: 11 (0xb)
Signal 11 is a segmentation fault (like on Linux hosts), which means that a VirtualBox component crashed on the host side. Details should be available in your macOS crash logs.
ElMaSkA007
Posts: 46
Joined: 3. Oct 2021, 13:42
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 11, Fedora 38, RHEL 8 and Ubuntu 22.04.2

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by ElMaSkA007 »

fth0 wrote:
VBoxSVC.log file wrote:
00:09:13.070583 Watcher  Reaper: Pid 50668 (c5ec) was signalled: 11 (0xb)
Signal 11 is a segmentation fault (like on Linux hosts), which means that a VirtualBox component crashed on the host side. Details should be available in your macOS crash logs.
Hi fth0.

I have been able to locate said crash through the "Console" application, it is a file with an .ips extension (I attached it to this message for analyzing by yours). The same, I sent it to Apple according to the crash report it generated. What I have been able to inspect in the crash log file is the following:

There we can clearly see the following lines:

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [50668]


I hope it helps to draw some conclusion as to whether it is a bug or not. What I would like to point out is that the crash was from the VM itself and not from VBox.

Thanks in advance.
Regards.
Attachments
VirtualBoxVM-2022-11-18-093135.ips.zip
Apple crash report
(9.11 KiB) Downloaded 3 times
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by fth0 »

Following the "Termination Process" line, there usually is information about which thread crashed, followed by a list of all threads with stack frames. The name of the crashed thread could hint to a VirtualBox component.
ElMaSkA007 wrote:What I would like to point out is that the crash was from the VM itself and not from VBox.
I'm not sure what you mean by that, since there is no VirtualBox component named "VBox". A few technical explanations:

Two major VirtualBox components are the VirtualBox Manager and the VirtualBoxVM process, and the latter uses a lot of threads (~42). If one of those threads crashes and takes the process with it, the VM naturally disappears with them. This is different from a crash inside the guest OS, which usually does not keep the VM from running.
ElMaSkA007
Posts: 46
Joined: 3. Oct 2021, 13:42
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 11, Fedora 38, RHEL 8 and Ubuntu 22.04.2

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by ElMaSkA007 »

Hi fth0.
fth0 wrote:I'm not sure what you mean by that, since there is no VirtualBox component named "VBox".
When I said "VBox" I meant the VirtualBox application itself.

If you were able to inspect the logs I provided, after the "Terminating process" line there is a thread that crashed:

Code: Select all

VM Region Info: 0 is not in any region.  Bytes before following region: 4304248832
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      1008da000-10099a000    [  768K] r-x/r-x SM=COW  .../VirtualBoxVM

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   IOKit                         	    0x7ff80ab33114 IOHIDDeviceCopyMatchingElements + 34
1   UICommon.dylib                	       0x1044b9ee9 0x104109000 + 3870441
2   UICommon.dylib                	       0x1044b9d33 DarwinHidDevicesApplyAndReleaseLedsState + 515
3   VirtualBoxVM                  	       0x1009125b1 0x1008da000 + 230833
4   QtCoreVBox                    	       0x1014cbea0 QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) + 224
5   QtWidgetsVBox                 	       0x101f305e4 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 68
6   QtWidgetsVBox                 	       0x101f31a72 QApplication::notify(QObject*, QEvent*) + 466
7   QtCoreVBox                    	       0x1014cbcf4 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
8   QtWidgetsVBox                 	       0x101f2f417 QApplication::setActiveWindow(QWidget*) + 1015
9   QtWidgetsVBox                 	       0x101f2fa43 QApplicationPrivate::notifyActiveWindowChange(QWindow*) + 51
10  QtGuiVBox                     	       0x101945d72 QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) + 674
11  QtGuiVBox                     	       0x101928cba void QWindowSystemInterface::handleWindowActivated<QWindowSystemInterface::SynchronousDelivery>(QWindow*, Qt::FocusReason) + 186
12  QtCoreVBox                    	       0x1014d6767 QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const + 1271
13  libqcocoa.dylib               	       0x108251832 invocation function for block in qRegisterNotificationCallbacks() + 2546
14  Foundation                    	    0x7ff80904149d -[__NSObserver _doit:] + 287
15  CoreFoundation                	    0x7ff80820575c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
16  CoreFoundation                	    0x7ff8082a2b32 ___CFXRegistrationPost_block_invoke + 49
17  CoreFoundation                	    0x7ff8082a2ab0 _CFXRegistrationPost + 496
18  CoreFoundation                	    0x7ff8081d73e8 _CFXNotificationPost + 735
19  Foundation                    	    0x7ff8090157fe -[NSNotificationCenter postNotificationName:object:userInfo:] + 82
20  AppKit                        	    0x7ff80adf3457 -[NSWindow resignKeyWindow] + 759
21  AppKit                        	    0x7ff80adf30a9 _NXEndKeyAndMain + 162
22  AppKit                        	    0x7ff80adf203b -[NSApplication _handleDeactivateEvent:] + 751
23  AppKit                        	    0x7ff80adb7f3c -[NSApplication(NSEvent) sendEvent:] + 2936
24  libqcocoa.dylib               	       0x108268758 -[QNSApplication qt_sendEvent_replacement:] + 56
25  UICommon.dylib                	       0x1044bb5cd 0x104109000 + 3876301
26  AppKit                        	    0x7ff80b07018b -[NSApplication _handleEvent:] + 65
27  AppKit                        	    0x7ff80ac38d3e -[NSApplication run] + 623
28  libqcocoa.dylib               	       0x108265294 QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2548
29  QtCoreVBox                    	       0x1014c7eb7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 439
30  QtCoreVBox                    	       0x1014cc282 QCoreApplication::exec() + 130
31  VirtualBoxVM                  	       0x1008dffab TrustedMain + 1163
32  VirtualBoxVM                  	       0x1008e01b6 0x1008da000 + 25014
33  dyld                          	       0x100bfe52e start + 462
From what can be seen, there are many components related to VirtualBox involved.

Could we be facing a possible bug?

Thanks.
Regards.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Windows 10 guest crash unexpectedly on host macOS Monterey 12.6.1 and VBox 7.0.2

Post by fth0 »

ElMaSkA007 wrote:When I said "VBox" I meant the VirtualBox application itself.
That's the VirtualBox Manager then. For simplicity, the corresponding binary's name is VirtualBox(.exe), leading to an ambiguity between "the whole application downloaded and installed" and "the single user interface application started". Both could be called "the VirtualBox application", too. ;)
ElMaSkA007 wrote:If you were able to inspect the logs I provided
I didn't have macOS Monterey available, so I could only view the logs in a text editor as a JSON-like file. Thanks for providing the better readable visualization.
ElMaSkA007 wrote:Could we be facing a possible bug?
It looks like an old acquaintance, please see my post in MH - HidLedsSync workaround.
Post Reply