Hyper-v how to solve network problem?

Question

Virtualization

Hello, in general, I’ll tell you a little background, before there was an imac in my room, I ran parallels or vbox on it, I drove virtual machines there, when there is one powerful computer, you can easily do without additional pieces of iron, everything flies, works perfectly, despite the fact that the computer is connected via wifi (the provider's tariff is 60 megabits, over the air in the LAN it's more than a weave).
Now I have assembled a desktop with 128 gigabytes of RAM, 8 nuclear Xeon, installed the previously purchased wine 10 pro, and decided to use a virtualizer that comes free of charge and can run virtual machines in the background, well, in general, it is ideal for services deployed in the native environment. I have several machines on Linux, all add-ons are installed (kernel modules), the latest debians are installed.
Virtuals are bridged to my LAN, then I forward the necessary ports from the router. The bridge does not work adequately; virtual machines have losses of 20% or more packets, from the host computer itself to the same address, pings usually go to about 0% losses, well, occasionally the interference is small, i.e. the network itself is working fine. But Hyper-v, when creating a virtual switch, makes a bridge, but not between network boxes, but only includes an external network card in the bridge and adds its service there, and then creates its own virtual adapter, on which its service is also again and through it the Internet gives.
Maybe I should create an internal switch and manually make a bridge between them as usual? There is either dampness of dozens or something else, but the sites hosted on the virtual machine are either available, or again inaccessible, at the moment of inaccessibility, I cling to the computer via RDP, i.e. before it, the link is just super-duper and stable, and I worked on this computer for two days in a row, not a single gap, but the trouble with virtual machines is terrible.
Maybe someone had experience, tell me, advise, I'm just on Windows virtualization for the first time.

Answer 1

Guys, thank you all for trying to help, but, as it turned out, Hyper-v has such a problem with wifi, I found an article on the Microsoft website , there is an explanation that all virtual machines are thrown into the network with different poppies, as a result, one network box with a bunch of mac-addresses, it works well on ethernet networks, but on a wireless network there are such connection interruptions.
In general, for adequate work of virtual machines via wifi, an internal switch is created that connects the virtual machines with each other and with the host itself, a virtual interface appears in network connections, we set it to a different subnet and give the virtual machine an IP from this subnet, then we share the wifi connection (tab access) , we get NAT, i.e. The virtual machine climbs into the Internet, then to connect to the virtual machine from the outside - we forward the port in the same place, everything works, pings 0.8ms to the router. You will also have to add rules in the firewall, otherwise I did not get pings from virtual machines.

Answer 2

Answer from the category of a finger to the sky.
See what's the story with the virtualization mode on Windows:
1 when you turn it on, the host machine goes into a special mode - it kind of becomes virtual (and processor control goes to VMM).
2 you, if I understand correctly, have a regular network card, without SR-IOV modes, which means it does not know how to competently resolve flows (that is, all traffic first goes to the CPU, and only after processing it goes to the
virtual machine ) Your OS has other tasks with which it works, for processing interrupts and delivering traffic to the guest OS, it does not have enough priorities (not for it, but for VMM, but the essence is the same)
As a result, it turns out that network operation for the guest has a lower priority, than the tasks of the host OS, and the host OS performs tasks for which it takes a percent.
Those. maybe you just don’t have enough processor time for the network to work (you won’t be able to see such a load in the task manager, since see step 1).
Try the following:
1. Remove all load from the host
2. Turn on virtual machines gradually
3. Organize a separate network for Hyper-V and see if it will function normally (without using a physical card)
4. Make a separate machine with routing and set only it to real card, and the rest of the virtual machines will be in a separate virtual switch with it.
Also check that you are using exactly the Network Adapter (not Legacy)
UPD everything above is to find the problem.
The medicines are:
1. Use a full-fledged Hyper-V (Host\Guest priorities work better there)
2. Use server network cards
3. Remove all load from the host
4. Use Network Adapter as a virtual adapter for a non-Legacy guest

Answer 3

I'm afraid to make a mistake, but as far as I know, a full-fledged Hyper-V server (which is free, but a paid control panel) and the Hyper-V role are two different things. I've also tried using "built-in free virtualization". But he spat, shutting up on the network setup. I have enough virtualbox. And where there is not enough, I reboot into ubuntu and start kvm.

Answer 4

8 nuclear xeon

For reference: the network stack only works on the first core. Therefore, if you disable programs from running on this core, the situation may change.