Could you please test whether this is still an issue with VBox 4.3 and 4.3 Additions, and re-open the bug, providing VM log if needed?