This issue should be fixed with VBox 4.3. Please try it with VBox 4.3 and 4.3 Additions, and re-open if needed, attaching a VM log file here.