socratis wrote:You might have missed my previous post:
socratis wrote:Have you closed all VirtualBox processes? If not, shut down everything including the VirtualBox Manager and check not only for "vir" but for "vbox" processes as well. Wait about 30 sec and relaunch VirtualBox Manager. See if that helps...
If not, zip and attach the "VirtualBox.xml" file located either in "$HOME/.config/VirtualBox" or in "$HOME/.VirtualBox"
I closed it and reopen Virtual Box.
Then I see, no 'XP.vdi' in the Virtual Media Manager!
mpack wrote:Please zip up the .vbox file for this VM and attach it here.
Don, I hope you don't mean the XP.vbox, cause that's gone long time:
inshion wrote:5. I used 'rm -rf' to delete all the files of 'XP' in the file system.
@inshion: The "definition/recipe" of each VM (including its attached HDDs) is loaded during the launch of VirtualBox Manager and is kept in memory. You went behind VirtualBox's back and removed the files from within your host. VBox didn't know about that and when you tried to remove the XP.vdi it complained about being attached to an (in memory) guest. Closing and reopening VBox Manage forced the proper, existing VM definitions to be reloaded, therefore removing the XP.vdi from the Media Manager. Glad the facts didn't get misinterpreted, things worked out and you didn't get disappointed...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis wrote:Don, I hope you don't mean the XP.vbox, cause that's gone long time:
Why would I mean that? If I ask to see "the .vbox file" then I will usually be referring to the one belonging to the VM under discussion, in this case the CentOS VM shown in the original screenshot, which I've been commenting on throughout.