> 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?
Now that it has been removed, no VM will be using it, and it can be safely
deleted.
To be 100% sure, you might open up the VM *.vbox file and search inside for
the hex characters that make up the file name.
(Select the VM in the UI and right-click 'Show in Explorer' then open or
view the <VMNAME>.vbox file in your favourite text editor.)
Also search in the main VirtualBox.xml file for the same text.
(Which will be in C:\Users\(Yourname)\.VirtualBox\Virtualbox.xml)
If you find no reference to the removed VDI, then it is not used anywhere
by any VM and can deleted from the disk.
3.5GB is a lot, I wonder what it was? ...
> Second, exactly where did you find this information to explain what I
needed to do?
Hard question to answer simply...
>From various places including the user manual, and the forum FAQs, some
browsing of the source code and also direct experience when the same
problem has happened to me.
Some years ago I felt the need to understand snaphots in some detail and
educated myself by reading what I could find about them.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
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
