Custom Query (16363 matches)
Results (859 - 861 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9606 | obsolete | Batch VBoxManage unregistervm BSOD | ||
| Description |
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? |
|||
| #9608 | obsolete | VBoxManage storageattach fails when using the same filename again after delete and restarting VirtualBox fixes it) | ||
| Description |
I create a VM with VBoxManage using a batch. I copy an empty VDI to a filename of the VM. I attach the VDI with VBoxManage storageattach "%variable%" --storagectl "IDE Controller" --port 1 --device 0 --type hdd --medium "%variable.vdi" --setuuid %variable This works the first time. I delete the VM and repeat the process above, but when attaching the VDI file I get VBoxManage.exe: error: Storage for the medium 'C:\Program Files\Oracle\VirtualBox\data\.VirtualBox\HardDisks\secondtimefails.vdi' is not created VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium, callee IUnknown Context: "SetIDs(fSetNewUuid, bstrNewUuid.raw(), fSetNewParentUuid, bstrNewParentUuid.raw())" at line 637 of file VBoxManageStorageControlle r.cpp VBoxManage.exe: error: Failed to set the medium/parent medium UUID If delete the VM, and try it again, the same result. But here's the thing: When I exit VirtualBox (all of its processes) and launch it again, everything works like on the first time, and the problem repeats on the second. Any name I try reusing fails until restart of VirtualBox. (%variable is not a real variable, it's a placeholder) This worked in 3.x. (And I'm probably going to have to go back to it and try 4 later; you've broken quite a few things between 3 and 4.) |
|||
| #9609 | duplicate | Batch starting multiple VMs simultaneously GURU MEDITATION | ||
| Description |
I started 20 VMs at the same time using VBoxManage and got guru meditation on 6 of them and one aborted. I didn't experience this on 3.x. |
|||

