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”
There are 3 types switch can be created.
External type allows VMs to communicate with physical server and physical network which connected to Host.
Internal type allows communication between VMs and physical server but VMs can’t communicate with physical network which connected to Hyper-V server.
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.
Hyper-V is a “Type 1” hypervisor-based virtualisation platform that runs on Windows Server since version 2008. In this post, I will demonstrate on Windows Server 2016.
What is virtualisation? Virtualisation enables you to configure one or more virtual machines(so called VM) that emulate one or more physical computers.
Multiple VMs can run on one physical server or computer, with all VMs sharing resources e.g. CPU(s), Memories, Disk(s) or Network Adaptor(s) available on physical server or computer.
So, based on Hypervisor Type 1, those performance of application which runs on OS of VM is no difference with Host.
64 bits processor with Second-Level Address Translation(SLAT)
VM Monitor Mode extensions.
Virtualisation Technology (Intel VT-x / AMD-v) is enabled in BIOS or UEFI Firmware.
Directed I/O must be enabled to support SR-IOV
AMD? (Sorry, I don’t know)
Hardware enabled Data Execution Prevention (DEP) in BIOS or UEFI.
AMD (NX no execute bit)
Intel (XD execute disable)
After you run command “systeminfo.exe”, it will display your hardware meeting requirement for Hyper-V or not.
1. In “Server Manager”, select “Manager” -> “Add Roles and Features”
2. Click “Next” 3 times then tick the “Hyper-V” box.
3. Click “Add Features”
4. Click “Next” 3 times. Then choose and tick the ethernet card which is used for “Virtual Switch” to connect to your network. In my case, I only get one card. As below, I am using Hyper-V for this demonstration so my network card is a Hyper-v network adapter.
5. Keep clicking “Next” until see “Install”. Then, Click “Install”. Installation will be finished after computer is rebooted. You would see a option “Hyper-V Manager”
6. It’s what “Hyper-V Manager” looks like as below in my server running.