VBOX_E_INVALID_OBJECT_STATE (0x80bb0007) "locked read" adding multiattach

[dnhutchins_VCL]

VBoxManage will not allow me to attach multiattach type disk to another VM.

Example:

Setup VM #1 with a multiattach disk:

VBoxManage -q createvm --name vbox-ubuntu.vdi_vm18 --register
VBoxManage -q modifyvm vbox-ubuntu.vdi_vm18 --memory 256
VBoxManage -q modifyvm vbox-ubuntu.vdi_vm18 --nic1 bridged --bridgeadapter1 eth0 --macaddress1 00505600d541
VBoxManage -q modifyvm vbox-ubuntu.vdi_vm18 --nic2 bridged --bridgeadapter2 eth2 --macaddress2 00505600d542
VBoxManage -q storagectl vbox-ubuntu.vdi_vm18 --name vm18_stor --add ide
VBoxManage -q storageattach vbox-ubuntu.vdi_vm18 --storagectl vm18_stor --port 0 --device 0 --type hdd --medium /install/vbox/vbox-ubuntu.vdi --mtype multiattach
VBoxManage -q modifyvm vbox-ubuntu.vdi_vm18 --pae on
VBoxManage -q startvm vbox-ubuntu.vdi_vm18 --type headless

At this point this VM boots up without any issues, now on to setup VM #2:

VBoxManage -q createvm --name vbox-ubuntu.vdi_vm19 --register
VBoxManage -q modifyvm vbox-ubuntu.vdi_vm19 --memory 256
VBoxManage -q modifyvm vbox-ubuntu.vdi_vm19 --nic1 bridged --bridgeadapter1 eth0 --macaddress1 00505600d541
VBoxManage -q modifyvm vbox-ubuntu.vdi_vm19 --nic2 bridged --bridgeadapter2 eth2 --macaddress2 00505600d542
VBoxManage -q storagectl vbox-ubuntu.vdi_vm19 --name vm18_stor --add ide
VBoxManage -q storageattach vbox-ubuntu.vdi_vm19 --storagectl vm18_stor --port 0 --device 0 --type hdd --medium /install/vbox/vbox-ubuntu.vdi --mtype multiattach

And at this point I get the following error:

VBoxManage: error: Medium '/install/vbox/vbox-ubuntu.vdi' is locked for reading by another task

VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium, callee nsISupports Context: "COMSETTER(Type)(mediumType)" at line 554 of file VBoxManageStorageController.cpp VBoxManage: error: Failed to set the medium type

[dnhutchins_VCL]

[Removed]

[dnhutchins_VCL]

After further testing I understand it a bit more. If I omit the "--mtype multiattach" for subsequent attachments to new VMs after the first VM is running it works fine and defaults to the desired behavior of creating a new differencing snapshot and attaching that. Understanding that the locked state should be a blocker if changing the parent image from another type, but should this necessarily be a blocker if the image is already multiattach?

Although I realize this isn't the biggest fish to fry in terms of an enhancement, it sure would make a provisioning module I'm maintaining for Apache VCL a far sight easier to develop.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.