virtualbox.org

Hi,

I have a fairly vanilla Windows Server 2016 physical host that I use in my lab to test "things". Up until now I have always used VirtualBox for my test VMs but now I have a requirement to test using Hyper-V. However, when I install the Hyper-V role on the server and reboot it, none of the VB servers will start and throw the following error:
I searched though some threads but I'm not sure that I can find my same situation. I see some threads indicating that people tried to run VB *inside* a Hyper-V VM - that is not my case. I just want both to live side-by-side. I see the *huge* thread titled "VirtualBox 6.0 and Hyper-V" but that seems to be about something else altogether.

In my case it seems that the physical adapter gets disabled because it gets virtualized by Hyper-V and then I can't choose the virtualized adapter in the VB VM settings.

any way to get this to work?
Thanks

I think you've misread the threads you're already aware of. They all relate to the fact that, in the majority of cases, VirtualBox does not work well when Hyper-V is active.

Lockon wrote: I see some threads indicating that people tried to run VB *inside* a Hyper-V VM - that is not my case. I just want both to live side-by-side.

There is no such thing as "living side-by-side" with Hyper-v.

Hyper-v is a type 1 hypervisor. Meaning that it launches before the main OS, so your Server 2016 "host" is now a VM. It's a thin layer, but still a VM. If you try to run VirtualBox on Server 2016 then that's a nested VM scenario, and it is NOT straightforward. VirtualBox has been trying for a while to come up with a version that can live with this scenario, but it's all very hardware and OS scenario dependent, and we are definitely not there yet.

Frankly, for now (6.1.34) you still need to pick one or the other: Hyper-v or VirtualBox.

Try the 6.1.35 test build. It is reported by some to allow Virtualbox to run under Hyper-V.

Save the test build installer until you update again later. You'll need it if your host's MSI installation database goes south (they do) and the installer will not be available for download after the next even-number version gets released.

That said, the posted error seems to be related to the Virtualbox Bridged networking. Please uninstall Virtualbox, reboot the host, disable any non-Microsoft AV & security software, then reinstall Virtualbox using right-click Run As Administrator, even if the account is already an admin.