Windows server R2 Hyper-V (known?) issue with Virtual Switch

Forums › IT Pro and developers › Windows server R2 Hyper-V (known?) issue with Virtual Switch

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#82539 1-May-2011 10:28

Is there a known problem in Windows Server 2008 R2 SP1 (not upgraded, installed from image that includes SP1) with Hyper-V virtual switch? When I enable Hyper-V and a external network (bound to phyiscal) it moves the Static settings from the phyiscal adapter, causing all connection to be lost. So I moved the static settings back the physical but the virtual switch is unable to obtain settings from the DHCP server.

I have a Hyper-V already active and it works fine with the same configuration, however, it was installed on Windows Server 2008 R2 without SP1 and upgraded to SP1 later.

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

ajp

1 post

Wannabe Geek

#729547 10-Dec-2012 09:57

Hi lyonrouge, you wrote "Can now verify that Realtek RTL8169/8110 will not work as the Virtual Switch adapter". Thanks for your post. I had the same experience. In short, a Realtek PCI card wouldn't work no matter what tweaks I tried but then as soon as I changed to using an Intel Server Pro PCIe NIC the virtual networking worked fine.

Details: running Windows Server 2008 R2 Hyper-v, using an RTL819-based PCI-card NIC dedicated to the virtual network. The virtual network comms worked fine with XP VMs but as soon as I tried to add in a Windows 7 VM all the virtual network comms ground to a halt. I tried to fix it by disabling the TCP offload but that didn't help. Changed the card then everything perfect

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#794814 8-Apr-2013 08:24

Just did another build and migration, and found another issue with RTL8169. As per previous posts, this cannot be used as "share with management os" adapter. After migrating I found a long running issue I had with UDP traffic traversing a Virtual Switch appears to have been fixed. The root cause appears to be again the RTL8169. When I pulled apport the decommissioned Hyper-V host I found that this adapter was the one giving me UDP grief.

So in summary don't use a RTL8169 for

management adapter
UDP network

basic TCP seems fine.