Looks, like this is going to be fixed in the next release (VirtualBox Version 3.1.4) Release 3.1.4-B2 already has it and fixes this problem in the software virtualization version (32 bit) but is not recommended in production environments.
Looks, like this is going to be fixed in the next release (VirtualBox Version 3.1.4)
Release 3.1.4-B2 already has it and fixes this problem in the software virtualization version (32 bit) but is not recommended in production environments.