question

EduardMartinenko-9492 avatar image
0 Votes"
EduardMartinenko-9492 asked CR-0266 edited

Windows server 2016 Hyper-V external Switch really slow speed

I have a windows server 2016 machine, with two network interfaces, and installed Hyper-V server.
I want my virtual machines to be accessible from the external network (Local restricted network, without internet) and make it so that my virtual machines could get an IP address from the external DHCP server.

So I created a new external switch and made a network bridge between my real network card and the "virtual" hyper-v switch.

It works, but the speed is just abysmal... And the strangest thing not always. Sometimes it could be the full speed, sometimes especially when copying a large file between two virtual machines speed can reach as low as 10-15Kbyte/sec for no apparent reason (the network itself is more than capable to handle such load )).
When using the "internal" switch all work just fine without any problems.

What is the usual reason for this problem?

Maybe I don't need to create a bridge? (but how will my virtual machines be accessible from the network?)

windows-server-hyper-v
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Like in this example
https://www.tenforums.com/virtualization/31369-cant-enable-hyper-v-extensible-virtual-switch-networking.html?cf_chl_jschl_tk=6981573ebdebd8a991db77b9e24af7f5a7fa3ea5-1599634004-0-ATZNyxFRA_3fVS5ru6GaOdpSMgvm8mw-q3mgpSW3baxd5nTMiCcxNOErt-8AlY-493kps2KSmUk_QPF2Yskf4XFl7lAP69_cJHy6eZWv7oyhuUSIjLiBziopBhW01UAdg2oe3JfLHKQS6M-4nijFkDJbuikxlYxe4SQm74BEPuQyy3k0c_a5euHtfSFedlOQ-Tq2EG5VRDdJpnhDeA0_dm5iGqWWyE6fyAsW5cRsT4NG01PQLkxp5TpRHuaBoLXCFIVjcdoazYuI6p_94tvJeHPLE94DQBhr1yQLdHIXDo5-ylvk71M_z8GSFUV6EzYv9cpAzYfWVorqOaWpMRB1HDBXwYBfKAroC5UjrdQCqKkQRY7k48c6ETQIn_-st9Iqxw

0 Votes 0 ·
DSPatrick avatar image
1 Vote"
DSPatrick answered EduardMartinenko-9492 commented

Maybe I don't need to create a bridge?

That's correct. When you create a new external vSwitch the internet protocols are removed from the adapter and the Hyper-V Extensible Switch protocol is added turning that physical port into a multi-port virtual switch. Connect your VMs to this vSwitch and use each VM's vEthernet to configure the addressing in the exact same manner as if it were a physical NIC


--please don't forget to Accept as answer if the reply is helpful--








· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Extensible Switch protocol Doesn't work in my case.
I just can't tick the box...

0 Votes 0 ·
DSPatrick avatar image
0 Votes"
DSPatrick answered CR-0266 edited

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/connect-to-network

There's nothing extra for the end user to do, I'd suggest deleting / recreating the vSwitch. When you create a new external vSwitch the internet protocols are removed from the adapter and the Hyper-V Extensible Switch protocol is added turning that physical port into a multi-port virtual switch. Connect your VMs to this switch.


--please don't forget to Accept as answer if the reply is helpful--




· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

You have to do this from INSIDE hyper-v manager or else you get the ....i cant tick the box situation

  1. create your external switch and select the correct physical network card.

  2. Click ok and it then does the required for you and sets it all up.

If that does not work delete those switches and create them again inside hyper-v manager.

0 Votes 0 ·