Which solution?
From https://www.whonix.org/wiki/VirtualBox/Troubleshooting#Aborted_Status
Whonix ™ provides VM images that operate inside of the VM. Whatever occurs inside a VM should never lead to a crash (status aborted) of the host virtualization software, VirtualBox.
Unfortunately, I cannot add anything else to that.
The General VirtualBox Troubleshooting Steps include
consider running Whonix ™ from a Linux computer rather than Windows computer, see Host Operating System Selection.
I doubt you switched your host operating system to Debian buster
? Because this very most likely wouldn’t happen there.
Therefore the only option left is this:
Consider reporting a bug against upstream VirtualBox [archive] – VirtualBox bugtracker [archive] / VirtualBox forums [archive]. Logs are useful for developers to isolate the problem. [10]
To capture the VirtualBox log:
-
VirtualBox
→ right click a VM
→ Show Log...
→ Log
→ Save
→ OK
- Zip the log.
- Report to VirtualBox support.
I haven’t seen that happened yet either.