Please check whether this is still a problem with a recent release of VirtualBox and reopen the defect if necessary. Closing for now.