Hyper-V and VirtualBox

So when I needed to setup a Linux VM, I needed to have one set on top of the OS instead of below. So instead of using my favorite virtualization technology in Hyper-V, I had to use something like Oracle’s VirtualBox.

Why do I need a virtualization technology on top of the OS? I need the USB access so I can use a Ubertooth One.

One problem is that Hyper-V and VirtualBox do not play well together. When you have Hyper-V enabled then VirtualBox can not run. I think this is because Hyper-V can not support virtualization within itself. Because you turn on Hyper-V your Host OS is not actually your host. It is a special VM. When it is off, it’s your host.

When Windows 8 can out with the Hyper-V technology ready to go within it, I asked a server admin buddy about it. He said my theory was a little off but I had the general idea. Windows 8 system is a special VM sitting on top of Hyper-V technology. The hypervisor was the OS. It is special hence why it has access to the USB ports. When you turn on the hypervisor function, you make the system treat it as a VM. Because it becomes a VM you can not run another virtualization technology within it.

Understand what I just said is technically wrong but for the layman good enough to understand what is happening. You can only have one virtualization technology running.

How do you get around this issue? Easy you need two scripts. One that will enable Hyper-V and another that will disable it. This is a rip off the work of this chap, Derek Gusoff . Give his site some love and give him a click. He gave the commands needed. I prefer to wrap that up in some batch files.

Make sure to run it as an admin. After you run it, you will have to reboot. Annoying but that is what happens when you play with the computer’s inside bits too much.

To disable you need this command:

bcdedit /set hypervisorlaunchtype off

To enable, you need this command:

bcdedit /set hypervisorlaunchtype auto

I would throw a pause statement after each in your commands so your control window does not close before you can read the result. If you don’t run it as an administrator, it will fail.

Hopefully, this will make life a bit easier on Hyper-V lovers that have to occasionally use VirtualBox. I have not yet noticed any little punishments for doing this yet but if I do, I will let you know.

Leave a Reply

Your email address will not be published. Required fields are marked *