| 1 | | The Virtual Media Manager is probably not properly updated when a virtual harddisk (vmdk) is removed from a VM. Operations with VBoxManage on the virtual harddisk fail because it erroneously detects that it is attached to the VM. |
| 2 | | |
| 3 | | 2 hours later: |
| 4 | | |
| 5 | | Discovered that detaching a disk from SATA is not enough if there are snapshots where it still is attached. |
| 6 | | Removing the snapshots is a lot of work (not cutting XML corners, using the Media Manager), especially when the parent VMDK is made read-only (for safety. I just want to operate on a diff disk)). |
| 7 | | But when done, the Media Manager correctly states the the vdisk is no longer attached. |
| 8 | | The new technique I use is unregistering the VM. Do my thing with VBoxmanage - making an extra new diff for the same parent vdisk. And register the VM back again. |
| 9 | | |
| 10 | | But guys, what a lot of tedious work, those kind of operations should be made easier !!! |
| 11 | | |
| 12 | | |
| 13 | | |
| 14 | | |
| | 1 | SOLVED ! Mark this ticket as closed /solved please. |
