Could you check whether the issue is fixed with VBox 4.3 and 4.3 Additions, and if so, attach a fresh VM log here?