Because Windows 8.1 ships with Hyper-V bundled, my VMware virtual machine couldn’t be used anymore, so I had to pick one — of course I chose the built-in one; the native one surely runs well. For the virtual machine network, it’s actually very simple; we can easily virtualize a switch, which is essentially a link, similar to a local connection. First let’s look at the three network types of Hyper-V: External network (lets the VM connect to the external network) Internal network (lets multiple VMs connect internally; multiple networks can also be isolated via VLAN) Private network (an isolated local-machine network) The first type lets the VM connect to the external network and go online. In the Virtual Switch Manager, select the first option External network, and choose the network adapter you want to use — I have both a wired and a wireless adapter. 
Then, in the settings of the created virtual machine, select Network Adapter and choose the virtual switch you just created. The same applies below, so I won’t repeat it.
- Hyper-V Private network, as its name suggests, is for VMs only; data communication can only happen between VMs, and no communication is possible between VMs and the host or the physical network.
- Hyper-V Internal network type only allows network communication between VMs and between VMs and the host running Hyper-V, but does not allow VMs to communicate with the physical network.
- Hyper-V External network type allows network communication between VMs, between VMs and the host running Hyper-V, and between VMs and the physical network.