Now Available:

Featured Resource:

line

Newsletter

Email Address:


line

Ask the Expert

Have a question for our resident expert? Email your questions to Greg.

« Don't Miss the Party! Server 2008 Launch Events are Coming Next Month! | Main | Greg Pens a 4-Part Series on System Center Essentials for MCPMag.com »

An Introduction to Networking with Hyper-V

When we start considering Hyper-V as a virtualization solution, we need to begin considering the concept of partitions. Each system with Hyper-V active will have onboard a "primary partition", which you can consider to be the "core" or "base" system upon which Hyper-V actually drives the virtual machines.

Each virtual machine itself is another partition, specifically a "child partition" related to the primary one. One thing impacted by this concept of partitions is now networking is handled by the host. Upon the installation/activation of Hyper-V, network cards assigned to each child partition will show up within the primary partition as additional network cards. When this occurs, the bindings on the original physical network card are changed to remove the usual bindings and add the Virtual Network Switch Protocol.

Thus, the original network card becomes effectively like a software router, sending traffic to virtual cards as necessary within the internal network.

More past the jump...

There will be some important considerations associated with this change. As copied from this blog post at www.thesystemadministrator.com:

The virtual network adapter that appears under Network Connections will have the same name as the virtual network switch it is associated with.

It is possible to create an 'Internal' virtual network - which will expose a virtual network adapter to the parent partition without needing to have a physical network adapter associated with it.

Unlike with Virtual Server, Hyper-V only binds the virtual network service to a physical network adapter when a virtual switch is associated with the physical network adapter in question. The advantage of this is that you avoid the performance overhead involved with having this service enabled on network adapters that are not associated with virtual network switches, the downside is that it means that networking gets disrupted on the network adapter in question when a virtual network switch gets created or deleted.

TrackBack

TrackBack URL for this entry:
http://www.realtime-windowsserver.com/type/mt-tb.cgi/627

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

line

Greg Shields' Bio:

Greg Shields, is an independent author, instructor, and IT consultant based in Denver, Colorado, and a co-founder of Concentrated Technology. With nearly 15 years of experience in information technology, Greg has developed extensive experience in systems administration, engineering, and architecture specializing in Microsoft systems management, remote application, and virtualization technologies. Greg is a Contributing Editor for Redmond Magazine, MCPmag.com, and Virtualization Review Magazine and is the author of five books, including Windows Server 2008:  What’s New / What’s Changed. Greg is also a highly sought-after instructor and speaker, speaking regularly at conferences like TechMentor Events, and producing computer-based training curriculum for CBT Nuggets.  Greg is a recipient of Microsoft "Most Valuable Professional" award with a specialization in Windows Terminal Services.