Please reopen if still relevant with a recent VirtualBox release and attach the VBoxSVC.log, a VBox.log from the VM and the VM config to this ticket and give some instructions on how to reproduce this issue.