Yes, we've had this issue. It's a CPU problem, not the VM. I don't know if the new rev 1.15 fixes this issue.