Nope, it was to *enable* vt-x, but not everyone has a CPU that supports that.
Wasn't the best way to avoid the issue just to disable VT-X in the VM configuration under VBOX?Or doesn't this trick work always?
We can add a explicit message as "Ey,you!If you are using VboX greater than 4.0 and you face this issue, just disable VT-X for now and done!"
If there is a way that any tester can use the VM...where is the big drama?