> From: Mark Filipak [mailto:markfilipak.virtual...@gmail.com] > Sent: Monday, March 25, 2013 3:55 PM > > This happened all of a > sudden and for no apparent reason. I booted my host a couple of mornings > ago, did some light work, then fired up VBox and was confronted with this > error.
In the worst case, you can close VirtualBox, eliminate your config directory, and then launch VirtualBox as if it were the first launch ever. Click on Machine / Add, and browse to your guest.vbox file and import the machine. If *that* doesn't work, you must have some corruption in your guest machine files, in which case, you might want to repeat this process, but create a new machine from scratch and try to add the existing .vdi disk to your new guest. If you don't have a corrupt guest hard drive, you should be able to find *some* solution this way. I don't know where the VirtualBox config dir is on windows, but in solaris it's ~/.VirtualBox, so I'm just guessing you'll find a ".VirtualBox" directory in your home directory. It contains VirtualBox.xml, as well as several VBoxSVC.log files and a few others. If you delete that directory, the next time you launch VirtualBox, it will be like the first time. ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
