#5339 closed defect (fixed)
DVD Image cannot be released after reverting VM to current snapshot
回報者: | Markus Duft | 負責人: | |
---|---|---|---|
元件: | DVD | 版本: | VirtualBox 3.0.8 |
關鍵字: | dvd image snapshot revert | 副本: | |
Guest type: | Windows | Host type: | Linux |
描述
I just experienced this problem:
1) i started 4 vm from their current snapshot's clean state 2) i added a dvd image to the media manager 3) i mounted that dvd image to all of the 4 VMs 4) i did some work with the VMs, and then powered off, reverting to the snapshot in the same step. 5) i started the VMs again from the clean state 6) i tried to remove the DVD image from the media registry before deleting it from disk, but it is still recorded as mounted in all of the 4 VMs (even though it isn't of course.
trying to "release" the image in the media manager, i'm getting:
======== Are you sure you want to release the CD/DVD image /mnt/smb/s01en22vm1/Projects/Gentoo/interix-setup-trunk/Images/gpx-universal-20091029.iso? This will detach it from the following virtual machine(s): VM2: GPX: Windows XP, VM4: GPX: Windows Server 2008, VM3: GPX: Windows Server 2003R2, VM5: GPX: Server 2008R2 x64. ========
and after clicking release, i'm getting:
======== Failed to open a session for the virtual machine VM2: GPX: Windows XP. A session for the machine 'VM2: GPX: Windows XP' is currently open (or being closed).
Result Code: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007) Component: Machine Interface: IMachine {540dcfda-3df2-49c6-88fa-033a28c2ff85} Callee: IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8} ========
a quick grep over all .xml virtual machine files showed that the last reference to the dvd image is in the media registry itself. i also made sure that no image at all is mounted in any dvd drive, so _nothing_ is mounted at this time...
BTW. (unrelated to this bug) i find it a little questionable to store the DVD image state in a snapshot, or at least the fact that having a image mounted at snapshot creation time locks down the image until the snapshot is removed again.
I think this bug was fixed some time ago. Please reopen if still relevant with VBox 4.1.6.