Still getting VT-x error after enabling in bios
mbecks
Registered Posts: 7 ✭✭✭✭
Yesterday I got started with DSS, had IT install Virtualbox and enable virtualization in the bios - everything worked great.
This morning it's no longer working. I keep getting VT-x error when starting the virtual machine.
We've checked the bios and virtualization is still enabled. Also, Hypver-V is not enabled.
Please help.
This morning it's no longer working. I keep getting VT-x error when starting the virtual machine.
We've checked the bios and virtualization is still enabled. Also, Hypver-V is not enabled.
Please help.
Tagged:
Best Answer
-
For future users who encounter this problem:
There is no solution.
The issue is caused by Windows Device Guard blocking virtualbox. So unless you can convince IT to disable Device Guard, this effectively shuts down this method of trialling Dataiku.
Answers
-
Hi,
Hardware virtualization is needed for Dataiku DSS to work in a virtual machine. You should find some troubleshooting help on: https://doc.dataiku.com/dss/latest/installation/other/vm.html#hardware-virtualization
Cheers,
Alex -
Alex, as you can see from my original post - Hardware virtualization is enabled.
-
This issue is linked to VirtualBox and your operating system. You should find help in the links referenced in our documentation.
-
Could you be more specific? I'm using Windows 10 64-bit with 16gb ram.
My laptop was with IT for an hour yesterday and they couldn't solve the problem. -
Has IT uninstalled hyper V and then restarted your computer? The link referenced in our documentation (http://druss.co/2015/06/fix-vt-x-is-not-available-verr_vmx_no_vmx-in-virtualbox/) corresponds to the same error you posted.
-
Hyper-V was never enabled, we looked and it is un-ticked.
We will try enabling it and then disabling it again and see if that helps. -
We've now tried this and it hasn't worked.
We either get the VT-x error:
VT-x is not available (VERR_VMX_NO_VMX).
OR, if we reduce the RAM available to the VM, we get the following Hyper-V error:
Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).
But to be clear:
Virtualization is ON
Hyper-V is OFF
So we shouldn't get either of these errors. -
Did you disable or uninstall HyperV? It specifically needs to be uninstalled, disabling may not be enough. Then you need to restart your computer.
-
We've followed the instructions in the documentation (windows features > untick Hyper-V>restart PC).
One article calls it 'uninstalling' and another calls it 'disabling' but the instructions are identical.
