VT-x vs. Hyper-V (and what Virtualbox and Docker think about it)

I recently updated to Windows 10 and wanted to play with Docker (the native one, not the Toolbox). I was eager to see if the Folder Mounting works better than with the Toolbox – which requires some unnerving Commands to produce a shared folder in the Boot2Docker Image which is then mapped to Folders inside the Docker Container.

So, i activated the VT-x Features in the BIOS (and used a fancy tool for my Dell Latitude , „CCTK“ – which really sucks, imho). Then in installed Virtualbox and the Docker (Beta). Now Virtualbox will be able to boot my (x64) VM…..oh, actually not. Various Errors told me that my machine has no VT-x Features.

This happens because Windows 10 (and – i presume – Windows 8) is running the Hyper-V Hypervisor. And there can only be one Hypervisor in Charge. Either Hyper-V or VT-x. And since the Service is running per default, the Hardware is blocked by Hyper-V.

You can actually disable Hyper-V in Windows 10 (sorry for the German Screenshot, its available in the Program Install Part of the Control Panel):

As you see i have disabled the Platform Features and the Administrative Tools for it. The worst part is : A reboot is needed as the kernel is either controlling the Hardware or not.

You can check if thats correct in Oracle Virtualbox. German Screenshot again, but you can find it when Changing a Box at the System Menu….the Screenshot shows the Acceleration Tab which is completely greyed out if Hyper-V is active:

Now it´s usable and Virtualbox runs again.

Still pondering if i make a start menu entry like described here to make switching more comfy: Switch easily between VirtualBox and Hyper-V with a BCDEdit boot Entry in Windows 8.1

Looks like the OsX Users don´t know that Problem. This is either making Windows obsolete or Oracle Virtualbox. Definitely not Docker.