Replying to therion, mousecat & reece:
The problem is still there with 4.0.8, FYI.
Could you try if the issue is still there with the latest VBox 4.2.6 and 4.2.6 additions? And if yes, please attach a VM log here.