Last comment on upstream VirtualBox bug says that this was virtualbox problem, and that this issue is fixed with upcoming 2.0.2 release. http://www.virtualbox.org/ticket/1875
Last comment on upstream VirtualBox bug says that this was virtualbox problem, and that this issue is fixed with upcoming 2.0.2 release. http:// www.virtualbox. org/ticket/ 1875