#19397 closed defect
VirtualBox 6.1.4 GUI SEGV/crash when deleting a VM — 於 版本 5
回報者: | crunchyjohn | 負責人: | |
---|---|---|---|
元件: | other | 版本: | VirtualBox 6.1.4 |
關鍵字: | crash segmentation fault unregister vboxmanage unregistervm | 副本: | |
Guest type: | Linux | Host type: | all |
描述 (由 作最後更新)
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:
- Install Virtual Box 6.1.4
- Install Vagrant 2.2.7 (latest)
- mkdir test
- cd test
- vagrant init centos/7
- Vagrant up
- Vagrant ssh
- ls -l (just proof that you did something in the VM)
- exit
- VBoxManage list runningvms
- Get the ID from the left column, e.g. test_default_1584037646504_61912
- VBoxManage controlvm test_default_1584037646504_61912 poweroff
- VBoxManage unregistervm test_default_1584037646504_61912 --delete
- VirtualBox crashes.
I have a log that it tries to send to Apple, which I'll attach if I can.
更動歷史 (6)
comment:3 5 年 前 由 編輯
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?
comment:4 5 年 前 由 編輯
Sounds similar to problem where VirtualBox crashes when last VM deleted through UI.
comment:5 5 年 前 由 編輯
Host type: | Mac OS X → all |
---|---|
描述: | 修改 (差異) |
摘要: | Virtual Box 6.1.4 segementation fault / crash on "VBoxManage unregistervm" → VirtualBox 6.1.4 GUI SEGV/crash when deleting a VM |
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
Crash log