Comment 2 for bug 495178

I confirm this bug. Exact same error message on same architecture (Amd64). However, reverting to virtualbox-3.0.12 corrects the problem. It would be nice to make it work as well with the newer virtualbox, since there is lots of bugfixes/new features!