You'll launch the Virtual Switch Manager to create a virtual network connection

ntThe Virtual Switch Manager

n

ntIn order for a virtual machine created with Client Hyper-V to connect to a network and to the Internet, it must have access to a virtual switch. So the first order of business is to launch the Virtual Switch Manager and create and configure how you want the virtual network connection to work. To begin, launch the Hyper-V Manager using the tile on the Start Screen, navigate to the Actions pane, and select the Virtual Switch Manager action, as shown in Figure B.

n

ntCredit: Images by Greg Shultz for TechRepublic

The Virtual Switch Manager offers you three types of virtual switches

ntWhen you see the Virtual Switch Manager screen, as shown in Figure C, you’ll notice that the first thing that you must do is choose what type of virtual switch you want to create. As you can see here are three options: External, Internal, and Private.

n

ntCredit: Images by Greg Shultz for TechRepublic

Each type of virtual switch has specific uses

ntOf course, the one you choose will depend on how you want to use your virtual machine and in most cases you’ll choose the External option. However, let’s take a moment to examine each of these options so that you have a good understanding of what each one does.

n

nt
• nttWhen you select an External virtual switch, your virtual machine will be able to access all resources available on your physical network including host machine and the Internet.

nt

• nttWhen you select an Internal virtual switch, your virtual machine will only have a network connection with the host machine. In other words, the virtual machine will not be able to access resources on your physical network nor will it have access to the Internet.

nt

• nttThe only time that you would want to select the Private virtual switch, is if have more than one virtual machine running at one time and you only want a connection between your virtual machines.

n

n

ntEach of these types of virtual switches is illustrated in Figure D.

n

ntBefore I move on, I just want to point out that you can indeed have more than one virtual switch. For instance, you could have both an External virtual switch and an Internal virtual switch. You could then experiment with virtual machines in different types of network configurations.

n

ntCredit: Images by Greg Shultz for TechRepublic

You'll use the Virtual Switch Manager to set up your External virtual switch

ntConfiguring an External virtual switch

n

ntAs I mentioned, in most cases you’ll choose to create an External virtual switch in Windows 8’s Client Hyper-V. When you do, the Virtual Switch Manager will present you with the set of options shown in Figure E.

n

ntCredit: Images by Greg Shultz for TechRepublic

The host machine is actually connected to a virtual network card

ntStarting from the top, you can assign your virtual switch a name and provide a description in the Notes section. As you can see, I have provided both a name and notes for my example virtual switch.

n

ntMoving down to the Connection type section, you’ll notice that while the connection type that you selected previously is selected here, in this case External, you could change your mind and select one of the other two types of network switches.

n

ntWhen the Connection type is set to External network, you’ll see that your system’s network card is shown in the drop down text box and that the Allow management operating system to share this network adapter check box is selected. To simplify what this check box selection means, think of it as saying Allow host machine and virtual machine to use the same network card.

n

ntIn order for both machines to use the same network card to access the physical network, the Virtual Switch Manager actually creates two virtual network cards, one for the host machine and one for the virtual machine, and then connects these to the virtual switch. The virtual switch is then connected to the physical network card which is already connected to the physical network. This configuration is illustrated in Figure F.

n

ntCredit: Images by Greg Shultz for TechRepublic

Virtual Switch Extensions can add enhanced networking and security features to the virtual switch

ntIn most cases, you’ll leave the default selections for the External network just as they are. However, let’s examine how these options work. Let’s suppose that your system has two network cards in it: an Ethernet card called NC1 and Wireless card called NC2. If so, you could separate the network connections of your virtual machine and your host machine such that each would use a separate network card. To do so, you would select the network card that you wanted to use for the External network, say NC2, and then clear the Allow management operating system to share this network adapter check box. Then, the host machine would use NC1 to connect to the physical network and the virtual machine would use NC2 to connect to the physical network.

n

ntAs you can see, by default the Enable virtual LAN identification for management operating system in the VLAN ID section is not selected. Chances are that you won’t use this feature in a typical Client Hyper-V configuration. If you had a VLAN, or Virtual Local Area Network, you could use this option to specify an identification number that could be used to isolate network traffic from the host machine.

n

ntOther options

n

ntThere are a two other sets of options that you can configure from within the Virtual Switch Manager and these appear in the left panel. The first one is called Extensions and it appears under your virtual switch. The second one is called MAC Address Range and appears under Global Network Settings. Again, both of these are advanced features and chances are that you won’t use them in a typical Client Hyper-V configuration, but they are worth taking a look at, just so you know what they are all about.

n

ntVirtual Switch Extensions settings, shown in Figure G, provide you with a way to enable and add third-party extensible plug-ins to the virtual switch. These plug-ins can add enhanced networking and security features to a virtual network switch.

n

ntThere are two options in the Switch extensions list: Microsoft NDIS Capture and Microsoft Windows Filtering Platform. As you can see, by default the Microsoft Windows Filtering Platform check box is selected while the Microsoft NDIS Capture check box is not. Without getting too technical, Capturing extensions are used to capture and monitor packet traffic while Filtering extensions are used to inspect, drop, or exclude packets. You can learn more about Virtual Switch Extensions here.

n

ntCredit: Images by Greg Shultz for TechRepublic

MAC Address Settings displays the range of MAC addresses that are available

ntAs I said, these types of Virtual Switch Extensions won’t generally be used in a typical Client Hyper-V configuration, so just leave the default settings as they are.

n

ntMAC Address Settings, shown in Figure H, displays the range of MAC addresses that are available to be assigned to the virtual network cards that the Virtual Switch Manager can create. Under normal circumstances, the default range of MAC addresses is sufficient for Client Hyper-V and you won’t need to alter it.

n

ntCredit: Images by Greg Shultz for TechRepublic

When you are done configuring your External virtual switch, click OK

ntCompleting the configuration

n

ntWhen you are done configuring your External virtual switch, click OK. When you do, you’ll see a warning message indicating that during the virtual network connection procedure, the network connection for the host machine may temporarily go offline. When you click Yes, the changes will be applied and you’ll see a progress bar. These steps are illustrated in Figure I.

n

ntCredit: Images by Greg Shultz for TechRepublic

Running the Network Connections tool on the host machine

ntMany of the folks that I have spoken to about setting up an External switch find it surprising that the host machine is actually connected to a virtual network card after you set up a virtual switch for your virtual machine. But its true and you can see for yourself by investigating the Network Connections tool or even on the command line with IPConfig.

n

ntFigures J and Kshow before and after screenshots of the Network Connections tool and the results from running the IPConfig command on the host machine.

n

ntCredit: Images by Greg Shultz for TechRepublic

Running the IPConfig command on the host machine

ntRunning the IPConfig command on the host machine

n

ntWhat’s your take?

n

ntHave you attempted to create a Virtual Switch in Windows 8’s Client Hyper-V and encountered problems? Does this article help you to better understand how Client Hyper-V connects to a network? As always, if you have comments or information to share about this topic, please take a moment to drop by the TechRepublic Community Forums and let us hear from you.

n

ntAlso read:

n

nt
• ntt10 benefits of virtualization in the data center

nt

• ntt10 things you should consider when virtualizing enterprise desktops

nt

• nttGet started with Windows 8 Client Hyper-V the right way

n

n

ntCredit: Images by Greg Shultz for TechRepublic