Virtual Network on Hyper-V

Virtual Switch Manager

Virtual Switch Manager is used to configure network for VMs running on server. It enables to create and manage virtual networks.

Refer to article “Hyper-V in Windows Server“. After install Hyper-V role on HV1, we turn on “Hyper-V Manager” -> “Virtual Switch Manager”

3 types switch can be created.

There are 3 types switch can be created.

  1. External
  2. Internal
  3. Private

1. External

External type allows VMs to communicate with physical server and physical network which connected to Host.

2. Internal

Internal type allows communication between VMs and physical server but VMs can’t communicate with physical network which connected to Hyper-V server.

3. Private

Private type only allows communication between VMs but even no communication with Host!

Virtual Network Adapter

Don’t know you would be curious on that there is 1 more virtual network adapter on Host? Why? We use those pictures above to explain. Actually, Hyper-V automatically generates a virtual network adapter that bind to “External” or “Internal” for Host to communicate with VMs

Open “Control Panel” -> “Network and Sharing Centre” -> “Change adapter settings” on left side on windows.

After we installed Hyper-V roles on HV1, 1 virtual adapter would be automatically generated and bound to an External Switch which bound to physical network adapter also. But my demonstration is using a VM to install Hyper-V roles on it so you would see that even a physical network adapter is a Hyper-V Network Adapter also. I know that might cause confusion for understanding. I will show an other image below that running on my physical server.

As you saw, there are 2 network adapters in my host. I bound the External Switch which called “vSwitch” to 82574L adapter.