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

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

Post by ElMaSkA007 »

Hi again fth0.

Thank you very much for the clarification about the semantic differences between VirtualBox Manager and the binary name.

I just read the thread you told me about and I have the following question: currently section 9.25 has been changed to section 9.26 https://www.virtualbox.org/manual/UserM ... idledssync, Did you mean paragraph 9.25 https://www.virtualbox.org/manual/UserM ... assthrough? and in such a case, would I have to run the following couple of commands on the Windows 10 VM (this one being powered off)?

Code: Select all

VBoxManage setextradata VM-name \VBoxInternal/CPUM/IsaExts/SSE4.1 0
VBoxManage setextradata VM-name \VBoxInternal/CPUM/IsaExts/SSE4.2 0
Thanks in advance, I'm learning a lot.
Regards.
fth0
Volunteer
Posts: 5661
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 »

The title of the link in my old post consists of a chapter number and a heading, and you'd better go with the heading. ;)

Background reason is that the link always points to the newest documentation, and the chapter numbering changes from time to time. Perhaps I should leave out the chapter number in the future, thanks for asking! :)
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 »

Sorry for insisting because I think you have not answered my question, which commands should I execute:

9.26. Support for Keyboard Indicator Synchronization

Code: Select all

VBoxManage setextradata "VM Name" GUI/HidLedsSync 0
or

9.25. Passing Through SSE4.1/SSE4.2 Instructions

Code: Select all

$ VBoxManage setextradata VM-name \
VBoxInternal/CPUM/IsaExts/SSE4.1 0
$ VBoxManage setextradata VM-name \
VBoxInternal/CPUM/IsaExts/SSE4.2 0
Thanks.
Regards.
fth0
Volunteer
Posts: 5661
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 »

To explain both:

The link in my old post has the title "9.25. Support for Keyboard Indicator Synchronization", and I created this title in the past. I'll admit that I did not write it by hand but copy-pasted the title from the VirtualBox User Manual at that time. But it should be clear that the heading part "Support for Keyboard Indicator Synchronization" is the important part. In consequence, you should turn of the HID LED synchronization. And before you ask, don't forget to replace the "VM Name" in the command.
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.

Thank you very much for your patience and the support you have given me.

I will disable it (changing "VM-Name" for "Windows 10", which is how I have it named) and I will observe the evolution of my Win 10 VM.

I will post these days to give you feedback.

Thanks a lot.
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 »

Hi again.

Unfortunately, on December 2 my virtual machine Win 10 suffered again a crash. From the Apple's report that launched the host I could see the following:

Code: Select all

Crashed Thread:        14  SHCLIP
Thread 14 Crashed:: SHCLIP
0   libsystem_kernel.dylib        	    0x7ff80811300e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff8081491ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff808094d24 abort + 123
3   libc++abi.dylib               	    0x7ff808105082 abort_message + 241
4   libc++abi.dylib               	    0x7ff8080f61bd demangling_terminate_handler() + 266
5   libobjc.A.dylib               	    0x7ff807ff2e11 _objc_terminate() + 96
6   libc++abi.dylib               	    0x7ff8081044a7 std::__terminate(void (*)()) + 8
7   libc++abi.dylib               	    0x7ff808104458 std::terminate() + 56
8   VBoxRT.dylib                  	       0x10f3b5ffc 0x10f2a8000 + 1105916
9   VBoxRT.dylib                  	       0x10f474658 0x10f2a8000 + 1885784
10  libsystem_pthread.dylib       	    0x7ff8081494e1 _pthread_start + 125
11  libsystem_pthread.dylib       	    0x7ff808144f6b thread_start + 15

Thread 14 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000700003fd0000  rcx: 0x0000700003fcf908  rdx: 0x0000000000000000
  rdi: 0x000000000000c50f  rsi: 0x0000000000000006  rbp: 0x0000700003fcf930  rsp: 0x0000700003fcf908
   r8: 0x0000700003fcf7d0   r9: 0x00007ff808107fa1  r10: 0x0000000000000000  r11: 0x0000000000000246
  r12: 0x000000000000c50f  r13: 0x0000003000000008  r14: 0x0000000000000006  r15: 0x0000000000000016
  rip: 0x00007ff80811300e  rfl: 0x0000000000000246  cr2: 0x000000010fa4a325
It is true that I did not remember that I did not deactivate the option with the following command:

Code: Select all

VBoxManage setextradata "VM Name" GUI/HidLedsSync 0
Attached the logs so that they can be analyzed. I think I can be a different error than I initially reported.

I must point out this time that the version with which this error appeared was with the Virtualbox Manager ver. VirtualBox VM 7.0.4 r154605.

Thanks and regards.
Attachments
VirtualBoxVM-2022-12-02-113101 and VBox.log.2.zip
Apple report and logs from VBox Manager 7.0.4.
(33.37 KiB) Downloaded 2 times
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.

To record, I just executed the command:

Code: Select all

VBoxManage setextradata "Windows 10" GUI/HidLedsSync 0
to now go by limiting the problem and being able to continue advancing about why these sporadic crash that I still have.

Thanks and 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 »

Hi again.

My Windows 10 virtual machine has suffered another crash today (with VirtualBox Manager 7.0.4), presenting the same signature as I have been able to observe from the report that the host launches about the VirtualBoxVM process:

Code: Select all

Crashed Thread:        15  SHCLIP

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Thread 15 Crashed:: SHCLIP
0   libsystem_kernel.dylib        	    0x7ff80811300e __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff8081491ff pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff808094d24 abort + 123
3   libc++abi.dylib               	    0x7ff808105082 abort_message + 241
4   libc++abi.dylib               	    0x7ff8080f61bd demangling_terminate_handler() + 266
5   libobjc.A.dylib               	    0x7ff807ff2e11 _objc_terminate() + 96
6   libc++abi.dylib               	    0x7ff8081044a7 std::__terminate(void (*)()) + 8
7   libc++abi.dylib               	    0x7ff808104458 std::terminate() + 56
8   VBoxRT.dylib                  	       0x1120e2ffc 0x111fd5000 + 1105916
9   VBoxRT.dylib                  	       0x1121a1658 0x111fd5000 + 1885784
10  libsystem_pthread.dylib       	    0x7ff8081494e1 _pthread_start + 125
11  libsystem_pthread.dylib       	    0x7ff808144f6b thread_start + 15

Thread 15 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x000070000c2fa000  rcx: 0x000070000c2f9908  rdx: 0x0000000000000000
  rdi: 0x0000000000012d03  rsi: 0x0000000000000006  rbp: 0x000070000c2f9930  rsp: 0x000070000c2f9908
   r8: 0x000070000c2f97d0   r9: 0x00007ff808107fa1  r10: 0x0000000000000000  r11: 0x0000000000000246
  r12: 0x0000000000012d03  r13: 0x0000003000000008  r14: 0x0000000000000006  r15: 0x0000000000000016
  rip: 0x00007ff80811300e  rfl: 0x0000000000000246  cr2: 0x000001f597b0a8c0
I attach the logs so they can be analysed. It is clear that it is no longer a question of deactivating some options or others and that this is due to a bug, would you recommend me to open a ticket for this case?

Please help me with this because to be honest this is a bit frustrating.

Thanks and regards.
Attachments
2022-12-07-20-23-35-bugreport and VirtualBoxVM-2022-12-07-184743.zip
Logs VirtualBox and Apple report.
(175.48 KiB) Downloaded 1 time
fth0
Volunteer
Posts: 5661
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 »

Your newer crashes are located inside the Shared Clipboard code. This could be a result of mixing the VirtualBox 7.0.4 application with the VirtualBox 7.0.2 Guest Additions (GA). Uninstall the GA, restart the VM and install the GA 7.0.4.
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:Your newer crashes are located inside the Shared Clipboard code. This could be a result of mixing the VirtualBox 7.0.4 application with the VirtualBox 7.0.2 Guest Additions (GA). Uninstall the GA, restart the VM and install the GA 7.0.4.
Thanks for your help.

I don't know what would happen to me but I would swear I had installed the GA couple version. I have already proceeded to install the correct version of the GA to version 7.0.4.

I will leave my Win 10 VM running to see its evolution. Additionally, on the host I have disabled it from going to sleep.

Many 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.

What I am noticing a lot is regarding the sound (both with VBox 7.0.2 and 7.0.4), it is noticeable that the sound coming from my Win 10 VM does not sound so pure and sizzles are heard.

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 »

Hi again.

Please, Could you explain to me what these small problems in the sound are due to? I used to have Monterey, but just today I upgraded to Ventura 13.1 and the sound crackle on my Win 10 VM is still noticeable.

Regards.
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 »

Sound is not influenced by Guest Additions, unles there is a bug in the GAs that consumes the VM's CPU. 7.0 GAs have been a bit buggy so far. Sound requires some unused overhead in the CPU to work correctly. Per One issue per thread, please start a new topic with the most recent vbox.log:

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab.
Post Reply