virtualbox.org

So maxed out the system memory, and i quit my vbox session of backbox. When i attempted to reopen it i got multiple errors however after multiple restarts and installs to newest version. Still i get this error.

" Failed to open a session for the virtual machine .

The object functionality is limited.

Result Code: E_ACCESSDENIED (0x80070005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd} "
That error i get when i try to access my vm through a link on desktop. The error bellow is what i see within the Vbox .

" Start tag expected, '<' not found.
Location: 'C:\Users\user\VirtualBox VMs\New group\bb\bb.vbox', line 1 (0), column 1.
F:\tinderbox\win-5.0\src\VBox\Main\src-server\MachineImpl.cpp[740] (long __cdecl Machine::i_registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}"
I still have my snap shot vdi but in my attempts to save i lost another image file. I hope this issue is still salvageable. If i need to get red of things how much becuase i have some spare isos i can dispose of. I have a lot of work on that vm so your help would be appreciated to the highest degree!

Thanks again your fellow VBox user..

Maxing out your system memory while running VirtualBox should not cause file corruption. Rebooting your host while a VM is running might.

The solution is to find the "<vmname>.vbox-tmp" file in the VM folder and rename it to ".vbox". If that doesn't exist then rename the ".vbox-prev" file instead.

Thank you very much for your reply. In my research of this issue i did this however it still says not found error. I have 2gb of space left now.

The .vbox-tmp, .vbox-prev and .vbox files are all corrupted? I don't know of any way for that to happen - you should check again.

If that is what really happened then you can restore the files from your last backup.

If you don't have a backup then you have to create a new VM using the using VDI. You can expect activation problems, and data loss if you made the mistake of using snapshots, linked clones etc.

I have tried all that you have said is it safe to fan the white flag?

This issue has only become less clear to me as mpack was helping you - do you have reasonably looking (non-truncated) .vbox files for all your VMs? If that's the case it should be possible to revive them. If you don't have working .vbox files then the only option is to delete them (keeping backups just in case!) and create new VMs with the same settings "from your memory", pointing to the hopefully still intact disk images.

I know it's not terribly helpful or something which people like to hear after the fact, but please remember the general truth in IT: not having a known working backup implies that the data is worth nothing.

klaus wrote:This issue has only become less clear to me as mpack was helping you

What on earth does that mean? What did you say in your post that wasn't already said just as clearly in mine?

mpack wrote:

klaus wrote:This issue has only become less clear to me as mpack was helping you

What on earth does that mean? What did you say in your post that wasn't already said just as clearly in mine?

Wasn't criticizing your help at all... the replies by juswya5320 were not giving any hints what the current state is, and if there's something left to work with.

Thank yall i did copy the whole folder containing everything. However i did delete the original vm via Vbox.

That doesn't make sense. If you deleted the original VM via VirtualBox then VirtualBox would not let you run the VM and you couldn't be getting the error message you describe. And what does that have to do with "maxing out the Windows memory"?

Oh dear... when you say "system memory" (which normally means RAM) are you actually referring to disk space?

So let's see if I've got this right :-

1. You had a working VM, launched by opening a shortcut on your host desktop.
2. The VM used one or more snapshots.
3. The host PC ran out of disk space (while doing what?).
4. You responded by deleting something (unclear - the VM?), using method (unclear).
5. You tried to relaunch the VM (step missing: if you deleted the VM from the GUI then you should get VM not found message).
6. You deleted some other files.
7. You may or may not have a backup somewhere.

Nope, there is just too much vagueness, I have no idea where to start with this.

I mean disk space pardon my ignorance.