vboxmanage startvm reports success even if virtualization is turned of and the vm won't start

[HackerBaloo]

vboxmanage startvm reports: VM successfully started, but the VM is not started, and if you try to start the vm from the GUI, you get an error message with the error code: VERR_VMX_MSR_ALL_VMX_DISABLED

I'm running a Debian wheezy64 guest on Windows 7 SP1. So the workaround is to enable virtualization in the BIOS, but I would like to know that my script starting the server failed, instead of succeeded.

[Frank Mehnert]

Sorry, that's nothing VBoxManage is able to detect. VBoxManage just asks VBoxSVC to start a new VM process. The operation was successful if the VM process successfully started. The error reason you see happens later (when the VM process is already running).

[Frank Mehnert]

At least we've extended 'VBoxManage list hostinfo' to show if the processor supports VT-x/AMD-V or not, see r60684. I don't think that there is anything else we can do here...