Welcome to TechNet Blogs Sign in | Join | Help

Robert Larson

Thoughts and information on Virtualization and other topics

News

  • Hyper-V Resource Kit on the Shelves now! br>

    Welcome to my blog.

    I am an Architect with MS Consulting Services specializing in Infrastructure Optimization and Virtualization. I am also the co-author of the new Windows Server 2008 Hyper-V Resource Kit and the Virtual Server 2005 R2 Resource Kit.

    In this blog I will talk about various technology subjects that are my passion and also drive me crazy sometimes.

    The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Hyper-V R2 and Management NICs

When you install Hyper-V R2 role now it reserves a single wired NIC in the machine for management of the parent partition. If you have only a single NIC in your server, you will not be able you select a NIC to create an external network when you are installing the role.  This is a good thing because the installation is enforcing best practices.

Hyper-V R2 also has a new default when creating an External Virtual Network. By default the new external virtual network is not exposed to the parent partition for it to share. In order to enable the parent partition to share the NIC, there is a new checkbox that you must enable under the physical NIC dropdown box (as you can see in the picture below).

image

If your machine only has a single NIC, you can create an external virtual network and check this box. This will allow the virtual machines and the parent partition to share the single NIC.

NOTE: Doing this will violate best practices for a Hyper-V install. It is recommended to add an additional NIC to the server instead.

If you are running Hyper-V R2 on a notebook, another option is to use and ExpressCard Ethernet adapter or an USB-to-Ethernet adapter to add an additional NIC that can be seen by Hyper-V. See this previous post for some USB-to-Ethernet adapters that have 64-bit drivers.

Posted: Wednesday, February 11, 2009 2:41 AM by RobLarso

Comments

News said:

Want to know more about Hyper-V and what’s coming with R2? Here’s a collection of resources: TechNet

# April 15, 2009 10:54 PM
Anonymous comments are disabled
Page view tracker