Error in VirtualBox VBOX
These are the steps that VirtualBox takes when it writes a new Vbox file. Each step is contingent on the last one being completed without errors.
- Write a temporary file with ".vbox-tmp" extension.
- Delete any existing ".vbox-prev" file.
- Rename existing ".vbox" file to ".vbox-prev".
- Rename ".vbox-tmp" to ".vbox".
Have not tried these yet
The error that comes after the corruption of the vbox XML file is usually caused when the system locks up; thus preventing the virtualization software from finalizing the writing out to its file of configuration. The error probably implies that the <VirtualBox> opening tag on the line 2 of the file did not have any corresponding </VirtualBox> closing tag at the file’s end.
The fastest method of finding out if this is exactly what has caused the problem in your case; you can locate your vbox XML file for the Guest Operating System, whose home directory location is inside the folder of ‘VirtualBox’ in the ‘Machines’ folder in the ‘Name-of-Your-Guest-OS-Directory’ folder, saved as ‘Name-of-Your-Guest-OS.xml file’
The cause of the problem and the emergence of the error message could probably be simply that the XML file was badly corrupted whose repair process is easy and quick and might take only a minute to be repaired.
- Open the .vbox XML file in a text editor
- Then, go to that file’s last line
- On not seeing any closing tag of </VirtualBox>, it is confirmed that your XML file is corrupt.
- Now, initiate by adding this closing tag at the end of the file
- And then, from there, try and work your way back.
- Look through the file for the <Opening Tags> which do not have any needed </Closing Tag>
- Another way is to use some XML validation service
- Just after a few rounds of the three easy steps of Copying -> Pasting -> Validating, you can successfully repair corrupt vbox XML file.
Refer: https://www.bitrecover.com/blog/repair-corrupt-virtualbox-vbox-file/
Download Notes: [ repair-corrupt-virtualbox.pdf ]