It would be interesting to see what's in the cited log file. Unfortunately, many sites block attachements, and many of us refuse to open them for the same reason others block them. Did you examine the log yourself for clues? Many people here have a bad habit of just dumping log files without ever making an attempt to analyze them themselves. Even if you don't think you can understand "all" of it, it's often possible to locate "interesting bits" that provide valuable clues.
It would also be helpful to know the nature of your "problem" that caused you to lose your VM's.
First off, why not install a latest VirtualBox (5.2.4) and see if the issue persists?
1 person found this helpful
Google show many results about this error.
1. Check that present previos configuration file of VM. ( VM_NAME.xml-prev or VM_NAME.xml-tmp )
try rename it to VM_NAME.xml
2. May be you need install more fresh verison of VirtualBox or downgrade.
Good way - start from latest version.
Uninstall VBOX extension.
3. You not write what OS used on host-system.
Some people say that problem may cause windows update KB3004394.
You need ask sameself - what changed? Return to original state is also possible way.
VirtualBox have own forum: https://forums.virtualbox.org you can try seach answer on that forum or ask.
I already reinstall all the versions and the problem continues
I dind't find the XML file, look that:
C:\Users\rafael\VirtualBox VMs\oracle teste
Just this files.
So, I think what started the problem was when I set up my personal machine to use to work. I needed to install a lot of VPN to connect in differents costumers.
So I think the problem are in some windows KEY, network, some like that, when I go to FILE -> NETWORK OPERATIONS MANAGERS
Try rename oracle teste.vbox to oracle teste.vbox.some-else and oracle teste.vbox-prev to oracle teste.vbox