Ticket #9606 (closed defect: obsolete)
Batch VBoxManage unregistervm BSOD
|Reported by:||virtualboxbug||Owned by:|
|Version:||VirtualBox 4.1.2||Keywords:||batch, BSOD, unregistervm, delete, remove, VBoxManage, IRQL_NOT_LESS_OR_EQUAL|
Description (last modified by frank) (diff)
I ran this batch on a list of 10 VM names and at the fourth a BSOD with IRQL_NOT_LESS_OR_EQUAL occurred.
_ VBoxManage controlvm "%variable" poweroff VBoxManage controlvm discardstate "%variable"
VBoxManage storageattach "%variable" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium none
VBoxManage unregistervm "%variable" --delete VBoxManage closemedium disk "%variable.vdi" VBoxManage closemedium disk "%variable.vdi" _
"%variable" is a place-holder, not a real variable name. (Not sure all of the lines are required.)
Maybe because they were performed in such close succession, even running simultaneously since each deletion batch was started as a separate process, VirtualBox got really confused.
As a workaround I'll make them serial and introduce delays between deletions, so that everything has time to settle down.
Host is Windows Server 2003 Service Pack 2.
The question I'd like an answer to: Is it safe to run multiple instances of vboxmanage, asking VirtualBox to do many things at once?