Machine suddenly inaccessible

[John Perry]

Hello,

I was running VB 4.3.6 under Windows 7 early this week with no
problems. Monday or Tuesday I got a Windows update that required a
reboot; after it came back up I did some other work under Windows and
then tried to restart my openSuse 13.1 VM, which I've used happily now
for several months.

When the Manager came up it said my machine was inaccessible, with the
below copied message under Details. It also said 4.3.8 was available,
so I updated it, hoping this might be the solution. No luck.

I would just go ahead and reinstall openSuse, but I have a couple of
days' work in that machine that I'd like to avoid redoing. Is there
anything I can do to get this machine and my data back?

John Perry

----------------------------------------------------------------------------------------

Runtime error opening 'C:\Users\John\VirtualBox VMs\opensuse
13.1\opensuse 13.1.vbox'
for reading: -102(File not found.).

D:\tinderbox\win-4.3\src\VBox\Main\src-server\MachineImpl.cpp[731] (long
__cdecl
Machine::registeredInit(void)).
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

[Gregory Nowak]

Post by John Perry
Runtime error opening 'C:\Users\John\VirtualBox VMs\opensuse
13.1\opensuse 13.1.vbox'
for reading: -102(File not found.).

Hmmm, strange. My suggestion would be to see if you have a
C:\Users\John\VirtualBox VMs\opensuse13.1\opensuse 13.1.vbox.prev
file. If you do, make a copy somewhere else, and rename it minus the
.prev extension. Then, try to start your guest. If that still doesn't
work, you hopefully still have an 'opensuse 13.1.vdi' file in that
directory. If you do, then make a new guest, but use that vdi file as
the hard disk. Good luck.

Greg


--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

--
Free domains: http://www.eu.org/ or mail dns-manager-iDweQDFWK/***@public.gmane.org

[George R Goffe]

John,

I am NOT an expert with this by any means and don't do much with Windows.

Windows seems to like blanks in file names... A LOT.

It seems to me that you have a couple of options here:

1) reinstall suse...:(
2) copy/rename the current instance of suse, recreate the instance, compare file names, redo the suse installation in the new instance. I can't tell for sure but it looks like someone (VB? Windows?) has inserted a blank in your file name. If the names are EXACTLY identical, I would try copying your old instance files to the new instance files.
3) install the older instance of VB and try again.
4) is it possible to attach the copy of your running suse to a new instance as another disk?


In any event, I would try to save the "current" suse instance files.

Good luck,

George...