On 19 July 2012 22:14, Voelker, Bernhard <[email protected]> wrote: > Mark Cranness wrote (Wednesday, July 18, 2012 2:38 PM): >> On 18 July 2012 21:04, Voelker, Bernhard >> <[email protected]> wrote: >> > Hard disk >> > 'D:\ECSIDEVM\ecsidevm2\Snapshots/{c674a912-a1d4-4025-8543-0079e54e42b7}.vdi' >> > has more than one child hard disk (2). >> >> Use the Virtual Media Manager (File > Virtual Media Manager, Ctrl+D) >> and expand the tree under the hard disk(s) concerned. >> >> You will likely see a tree structure, where one of the nodes (the one >> that says "... (Snapshot B)" in the Attached To label) has TWO >> children underneath it. >> One of those child VDI files corresponds to snapshot C, and one is >> likely an orphan. >> >> Click on the one that has "Attached to:" = "Not Attached", and remove it. >> >> Now the tree should look like a linear chain (every node only has a >> single child), and you should be able to now delete snapshot D. > > Do you know where these orphaned VDIs are coming from?
I've had these orphans created when an attempted "Close > Save machine state" failed (from the menu that appears when you close a VM), or maybe when an attempted boot failed, and the VM had a saved state. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
