VT-x is not available (VERR_VMX_NO_VMX).
Posted: 4. Dec 2018, 19:19
I know I'm not the first to have this problem, but maybe my situation is different.
I'm working on a W10 machine that's quite locked, installing software is not allowed but internet access is quite open. Windows updates are performed regalarly.
We as developers develop software on a remote VM which is a Windows 10 64 bit environment where software installation can be done (as everyone is responsible for his / her VM) but internet access is restricted in it. So I downloaded and installed Vagrant 2.2.2, VirtualBox 5.2.22 and a 64 bit box (xenial-server-cloudimg-amd64-vagrant.box) on my PC, moved the files to the VM and installed them there. When I want to run this box in Vagrant I get the error mentioned in the subject.
As it's not a pc we're VirtualBox is running in there's no BIOS to enable or disable virtualization in.
As solution to this problem I've tried:
- moving the Virtual Box VM directory from inside C:\Users\<myuser> to a location inside D:\opt as only C:\data, C:\opt, D:\data and D:\opt are free from interference of McAfee (which cannot be turned off)
- looking in the services for Hyper-V services, but they're all switched off
- disabling Hyper-V through "dism.exe /Online /Disable-Feature:Microsoft-Hyper-V", but when I simple look at dism.exe there's nog Hyper-V entry at all under "DISM OPTIONS"
- I executed gpedit.msc, looked for "Turn of Virtualization Based Security" and set it to disabled
- I removed and reinstalled VirtualBox using "Run as administrator" to run the installer
All to no avail.
Does anyone have any other suggestions?
Logs are provided in the attached zip, the weird thing is: the VBoxHardening.log does not show errors, only VBox.log does
I'm working on a W10 machine that's quite locked, installing software is not allowed but internet access is quite open. Windows updates are performed regalarly.
We as developers develop software on a remote VM which is a Windows 10 64 bit environment where software installation can be done (as everyone is responsible for his / her VM) but internet access is restricted in it. So I downloaded and installed Vagrant 2.2.2, VirtualBox 5.2.22 and a 64 bit box (xenial-server-cloudimg-amd64-vagrant.box) on my PC, moved the files to the VM and installed them there. When I want to run this box in Vagrant I get the error mentioned in the subject.
As it's not a pc we're VirtualBox is running in there's no BIOS to enable or disable virtualization in.
As solution to this problem I've tried:
- moving the Virtual Box VM directory from inside C:\Users\<myuser> to a location inside D:\opt as only C:\data, C:\opt, D:\data and D:\opt are free from interference of McAfee (which cannot be turned off)
- looking in the services for Hyper-V services, but they're all switched off
- disabling Hyper-V through "dism.exe /Online /Disable-Feature:Microsoft-Hyper-V", but when I simple look at dism.exe there's nog Hyper-V entry at all under "DISM OPTIONS"
- I executed gpedit.msc, looked for "Turn of Virtualization Based Security" and set it to disabled
- I removed and reinstalled VirtualBox using "Run as administrator" to run the installer
All to no avail.
Does anyone have any other suggestions?
Logs are provided in the attached zip, the weird thing is: the VBoxHardening.log does not show errors, only VBox.log does