Hi, Mark.
Sure enough, your procedure worked. It showed that there was a pair of "hexcharacters.vdi" files attached to one of the nodes, one of which indicated "Not Attached". While using the Remove Tool this box appeared: At this step I chose to keep the storage unit because it was no obvious to me whether I may need it with the existing configuration. Afterwards I was indeed able to delete the snapshot successfully. Awesome! This now leads me to two questions. First, looking at the size of this storage unit file in the Snapshots folder, I see it is over 3.25 GB and I am inclined to delete it. So, how can I go about determining whether it is needed for any reason without just removing it and seeing the consequences? Second, exactly where did you find this information to explain what I needed to do? Thank you. > -----Original Message----- > From: Mark Cranness [mailto:mark.crann...@gmail.com] > Sent: Monday, March 11, 2013 6:19 AM > To: Community mailing list of VirtualBox users > Subject: Re: [VBox-users] unable to delete a particular snapshot > > Use menu File > Virtual Media Manager... > (select the disk and expand > all/any child nodes under the vdi file (click the triangles to > expand)) > > You may find that one of the nodes has two {hex}.vdi files at the same > indent level. > Click both and observe the 'Attached to' field at the bottom of the > window. > The one that displays 'Not attached' will be an orphan of some kind > (perhaps a failed snapshot or failed Save State or something). > Click it and then click the 'Remove' tool icon to delete it. > > Then try deleting the snapshot again. > > On 11 March 2013 14:21, John A. Wallace < <mailto:jw72...@verizon.net> jw72...@verizon.net> wrote: > > I am trying to delete a snapshot from a VM on a machine running > > Windows, but I keep getting the following error message. The guest is > > 32-bit WinXP Pro and the host is 64-bit Win7. > > > > > > It seems to be restricted by the apparent presence of "more than one > > child hard disk" although currently there is only one virtual disk > > associated with this guest on this physical machine. There were two > in > > the past, but I removed the other one some time ago. Perhaps > something > > confused the settings and they did not separate completely? I looked > > in the folder where this VM's virtual disk is located, and there is > only one there. > > > > If anyone has an idea about what I can look at to figure out how to > > make this right, your suggestion would be welcome. > >
<<attachment: image003.jpg>>
------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
