Back in the day, I was using VirtualBox (VB) and Vagrant (V) to run VMs. Since I installed docker-for-windows (DfW) and run V, VB complains about Hyper-V (HV).
[user@localhost ~]$ vagrant upStderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)VBoxManage.exe: error: Details: code E_FAIL (0x80004005), componentConsoleWrap, interface IConsole
Although this link indicates that V supports HV, the above error message is contradictive. Why does VB look incompatible with HV, why V says that it supports HV and how to prevent that HV needs to be disabled in order to use V again.
| Product | Version ||:-----------|--------:|| Vagrant | 2.0.1 || VirtualBox | 5.2.4 || Windows | 10 |
Discussion
The suggestion to switch Hyper-V on and off is not the preferred solution as it is time consuming.
If it would be possible to run V and DfW on the same system by replacing VB this could be an option.