This has been fixed in Virtualbox 4.2.18. See the last comments in upstream's bug report: https://www.virtualbox.org/ticket/12001
This has been fixed in Virtualbox 4.2.18. See the last comments in upstream's bug report: https://www.virtualbox.org/ticket/12001