Comment 1 for bug 1616794

Michael Thayer (michael-thayer) wrote :

This has been identified and fixed upstream in VirtualBox and will be a part of any future 5.0, 5.1 or later releases, as well as test builds[1] as of revision 112195. Please feel free to point the VirtualBox team to this sort of thing in future, on our bug-tracker or on IRC.