After installing a new VM in VirtualBox Version 4.1.10 I got this error for the first time since working with VirtualBox. I did not do anything with snapshots or config file editing. I just stopped the new installed VM, closed VirtualBox and at the next startup I got this error regarding my only VM in there. After googling a little, this seems to be a known bug in VirtualBox and can be fixed by following comment #29 of this post. After making the recommended changes everything turned out to be smooth again. When the fix will be applied is open til now.
This month’s „Tool of the month award“ on this blog goes to:
AND THE WINNER IS: VirtualBox
This is really breathtaking how easy and usable this virtualization software works and is available freely for private use for windows and linux.
Thanks to the VirtualBox developers team and company lead which have decided to make this extraordinary tool public under the GPL. This was the start ignition for porting my needed Windoofs into a VirtualBox window under Linux and remove the scrap from my harddisk.