[Bug]: VirtualBox 7.1.12 / 7.2.0 virtual machines crash when 3D acceleration is enabled, on macOS 15 as a Host OS.

[johnvranos]

Version

trunk/main

Host OS Type

macOS

Host Architecture

ARM

Guest OS Type

Linux, Windows 11

Guest Architecture

ARM

Component

3D Support

What happened?

When "enable 3D acceleration" is enabled in a VirtualBox virtual machine settings, the virtual machine crashes when started.

Debian 13 virtual machine, on VirtualBox 7.2.0:

VBox.log

How can we reproduce this?

Enable 3D graphics acceleration on any Linux or Windows 11 virtual machine.

Start the virtual machine.

After the virtual machine boots, it crashes.

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.

[AlexanderEichner]

Can you try whether VirtualBox 7.2.0_RC1 is better in that regard? We switched the stack handling the translation from DX11 to Metal to DXMT and it shouldn't crash anymore. Basic desktop usage should work quite okay now, however this is still highly experimental, so don't expect to run any games inside the VM.

[johnvranos]

New VirtualBox 7.2.0 has the same issue, including Windows 11 as a guest OS.

[johnvranos]

I am sending the automatically generated problem report, for each one of the virtual machines, created by macOS 15.6, when the virtual machine crashes.

debian 13 problem report.txt
ubuntu 25.04 problem report.txt
windows 11 problem report.txt

[johnvranos]

I am sending the VirtualBox log file, for each one of the virtual machines, created by VirtualBox 7.2.0, when each virtual machine crashes.

Debian 13
VBox.log

Ubuntu 25.04
VBox.log

Windows 11
VBox.log

[AlexanderEichner]

It looks like the VM is aborting due to an assertion in DXMT, can you start the VM from a terminal using "Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM --startvm " and post the output when it aborts?

[johnvranos]

Here is the VirtualBox error: There is no virtual machine named . Could not find a registered machine named *''*. Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) Component: VirtualBoxWrap Interface: IVirtualBox {2ce10519-3c09-45d8-a12d-e887786146b7}

…

On Mon, 18 Aug 2025 at 19:27, Alexander Eichner ***@***.***> wrote: *AlexanderEichner* left a comment (VirtualBox/virtualbox#101) <#101 (comment)> It looks like the VM is aborting due to an assertion in DXMT, can you start the VM from a terminal using "Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM --startvm " and post the output when it aborts? — Reply to this email directly, view it on GitHub <#101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMG4WUY6ZF74DBHRXSCQVOT3OH5F3AVCNFSM6AAAAACCNOZRCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJXGYYTCOJXGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[AlexanderEichner]

Github ate part of my command line, it should've been:
Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM --startvm <VM name>. The error you encountered means that VirtualBox couldn't find a matching VM because no name was given.

[johnvranos]

***@***.*** Downloads % /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM --startvm "Debian MATE 13" Assertion failed: (0 && "unknown component type"), function to_msl_type, file dxbc_converter.hpp, line 306. zsh: abort --startvm "Debian MATE 13" ***@***.*** Downloads %

…

On Mon, 18 Aug 2025 at 21:17, Alexander Eichner ***@***.***> wrote: AlexanderEichner left a comment (VirtualBox/virtualbox#101) Github ate part of my command line, it should've been: Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM --startvm <VM name>. The error you encountered means that VirtualBox couldn't find a matching VM because no name was given. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[AlexanderEichner]

This assertion will be fixed in the next 7.2.x maintenance release, please note that 3D is still considered highly experimental on macOS.