virtualbox.org

When I bridge Hyper-V Virtual Ethernet Adaptor start a virtual machine,It crash with null point exception. Can someone help me with the question.

Pictures show the question.

The Hyper-v Ethernet adapter is designed to be used by Hyper-v, not by VirtualBox.

The purpose of VirtualBox's bridging feature is to connect the virtual NIC inside a VM to a physical NIC on the host. Those are the realms being bridged. As far as I'm aware, connections to third party virtual NICs are not supported - and make no sense (VirtualBox has its own virtual NICs if that's what you want).

This is a bit of a puzzle. How does the OP see a Hyper-V Ethernet adapter to bridge to? Is he perhaps running VirtualBox inside a Hyper-V vm? Or does he simply have Hyper-V installed on the host so that the host has a Hyper-V Ethernet adapter?

I have not run Hyper-V for a while so I am not sure whether a VirtualBox host with Hyper-V installed would offer a Hyper-V adapter as a choice for bridging. I guess it could.

Answering my own question - yes it does.

I enabled Hyper- V on my test machine. VirtualBox does indeed offer the Hyper-V adapter as an option to bridge to.

If Windows offers that NIC to all apps that ask, and I don't see how else it could work, then yes - it would have to appear in VirtualBox. VirtualBox must have code to suppress its own host-only adapter.