VirtualBox 6.1.4 GUI SEGV/crash when deleting a VM

[crunchyjohn]

This issue is not present in Virtual Box 6.1.2. I do not know about 6.1.3.

I use a mac for virtual box (Mojave, v10.14.6)

Procedure to reproduce:

1. Install Virtual Box 6.1.4
2. Install Vagrant 2.2.7 (latest)
3. mkdir test
4. cd test
5. vagrant init centos/7
6. Vagrant up
7. Vagrant ssh
8. ls -l (just proof that you did something in the VM)
9. exit
10. VBoxManage list runningvms
11. Get the ID from the left column, e.g. test_default_1584037646504_61912
12. VBoxManage controlvm test_default_1584037646504_61912 poweroff
13. VBoxManage unregistervm test_default_1584037646504_61912 --delete
14. VirtualBox crashes.

I have a log that it tries to send to Apple, which I'll attach if I can.

[crunchyjohn]

Crash log

[crunchyjohn]

Sorry-- host was MacOS, Guest was CentOS/7

[crunchyjohn]

Any update?

A crash seems like a pretty severe problem, so I'm hoping others are able to easily reproduce it.

Is there anything else I can do to help?

[nycnewman]

Sounds similar to problem where VirtualBox crashes when last VM deleted through UI.

[paulson]

Thanks for the report. This is a regression introduced in 6.1.4 which affects all hosts. As @nycnewman reported in #19490 this is a problem in the VirtualBox GUI and as reported here is also reproducible if running 'VBoxManage unregistervm VMname --delete' of a VM while the GUI is running.

The easiest way to reproduce this on the command line is the following which works for me when there are no other VMs created:

$ VirtualBox &
$ VBoxManage createvm --name fubar --register
$ VBoxManage unregistervm fubar --delete
[1] + Memory fault(coredump) VirtualBox