Home > Hyper-V > Some Hyper-V Networking Recomendation

Some Hyper-V Networking Recomendation

Hyper-V uses a network virtual switch driver to control Windows Server network I/O. The switch abstracts the adapter by shutting down the adapter’s internal services and inserting itself between the network adapter and the virtual machines, including applications and services running on Windows Server 2008. Once in place, the switch wedges itself between virtual machines and the Windows 2008 server physical adapter.

Here it is some recommendations for networking:


1. Isolation of Networks connections

try to isolate your network connection, Use a dedicated network for management and a separate one for each VM.

2. Disable TCPOffloading

http://itproctology.blogspot.com/2008/05/hyper-v-tcpoffloading-poor-network.html


3. Measure Network Performance

http://msdn.microsoft.com/en-us/library/cc768535.aspx


4. Use synthetic network drivers
Hyper-V support two types of virtual network drivers: emulated and synthetic. Emulated drivers provide the highest level of compatibility. Synthetic drivers are far more efficient, because they use a dedicated VMBus to communicate between the virtual network interface card (NIC) and the root/parent partitions physical NIC. To verify which drivers are used from within a Windows guest OS, you can use Device Manager.


5. Increasing network capacity
Network performance is important for various types of applications and services. Whether running one or a few VMs, you can often get by with just a single physical NIC on the host server. But if many VMs compete for resources and a physical network-layer security is to be implemented, consider adding multiple gigabit Ethernet NICs on the host server.

Advertisements
Categories: Hyper-V
  1. Samir
    February 24, 2009 at 1:11 am

    Hi

    In the new server 2008 R2 beta there is a new server role service under the newly named RDS(remote desktop services) called RD(Remote Desktop) virtualization. The elaboration is that it enables users to connect to VM to acces Vitual desktops.

    Till yet there is no info on how to use this feature because i am building a FYP (final year )project based around this scenario of a user to access his her VM automatically via RDS WebAcess portal etc.

    Also where can i find RDS connection broker implementation info as the new feature introduced in R2. Any API link or so?

    So can any help be available on this?

    Thanks

    Take Care

  2. Mohamed Fawzi
    February 24, 2009 at 10:53 pm

    I sent you a mail reading that.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: