Please reopen if still relevant with VBox 4.3.2. In that case, please attach a VBox.log for a VBox 4.3.2 session.