Losing my first virtual machine Virtual Box without having r
Posted: 6. May 2013, 23:31
Hi everyone,
This is the first time I'm starting to enlist the help of online to help me solve a problem with my Virtual Box software installed on a host machine running Windows 8. So thank you to be lenient with the naivety of my questions as with my English
.
Here's the problem: I spent 3 days trying to create a virtual machine supporting Windows XPSP2 updated correctly from a certified copy (with the hope of returning to operation good devices from my old machine that aren't running Windows 8 ).
Everything seemed to have worked well and I was quite proud of the result until I noticed (after a restart two days later)that my virtual machine ... seems to have been lost somewhere in my computer and that Virtual box is not able to find it back for me !
Here is the warning I get when I raise my software, knowing that I feel that the problem is probably as much of my ignorance of the tree of my files and directories in Windows 8 as my guilty ignorance of what could happen when closing Virtual Box upon this new vitual machine!
May I give you below the comprehensive text of the warning for i hope someone can possibly help me to understand what happened, what i have to do in order to reactivate this virtual machine, without forcing me first obviously to "break" this lost virtual machine :
Runtime error opening 'D: \ Virtual Machines \ MV1-WXPSP2 \ MV1-WXPSP2.vbox' for reading: -252 (device i / o:. Not ready).
D: \ tinderbox \ win-4.2 \ src \ VBox \ Main \ src-server \ MachineImpl.cpp [725] (long __ cdecl Machine :: registeredInit (void)).
Error code:
E_FAIL (0x80004005)
component:
machine
interface:
IMachine {22781af3-1c96-4126-9edf-67a020e0e858}
This is the first time I'm starting to enlist the help of online to help me solve a problem with my Virtual Box software installed on a host machine running Windows 8. So thank you to be lenient with the naivety of my questions as with my English
.Here's the problem: I spent 3 days trying to create a virtual machine supporting Windows XPSP2 updated correctly from a certified copy (with the hope of returning to operation good devices from my old machine that aren't running Windows 8 ).
Everything seemed to have worked well and I was quite proud of the result until I noticed (after a restart two days later)that my virtual machine ... seems to have been lost somewhere in my computer and that Virtual box is not able to find it back for me !
Here is the warning I get when I raise my software, knowing that I feel that the problem is probably as much of my ignorance of the tree of my files and directories in Windows 8 as my guilty ignorance of what could happen when closing Virtual Box upon this new vitual machine!
May I give you below the comprehensive text of the warning for i hope someone can possibly help me to understand what happened, what i have to do in order to reactivate this virtual machine, without forcing me first obviously to "break" this lost virtual machine :
Runtime error opening 'D: \ Virtual Machines \ MV1-WXPSP2 \ MV1-WXPSP2.vbox' for reading: -252 (device i / o:. Not ready).
D: \ tinderbox \ win-4.2 \ src \ VBox \ Main \ src-server \ MachineImpl.cpp [725] (long __ cdecl Machine :: registeredInit (void)).
Error code:
E_FAIL (0x80004005)
component:
machine
interface:
IMachine {22781af3-1c96-4126-9edf-67a020e0e858}