![]() ![]() The Azure infrastructure controls the placement of the VM on the Azure host. Linux automatically determines whether to use the mlx4 or mlx5 driver. Because of the direct access to the hardware, network latency is lower and less CPU time is used to process network packets, when compared with the synthetic interface.ĭifferent Azure hosts use different models of Mellanox physical NIC. ![]() Most network packets go directly between the Linux guest and the physical NIC without traversing the virtual switch or any other software that runs on the host. It uses the Mellanox mlx4 or mlx5 driver in Linux, because Azure hosts use physical NICs from Mellanox. The VF interface shows up in the Linux guest as a PCI device. The second interface is an SR-IOV virtual function (VF) offered by the physical network's NIC in the Azure host. If the VM is configured with Accelerated Networking, a second network interface is created for each virtual NIC that's configured. Network packets that use this synthetic interface flow through the virtual switch in the Azure host and onto the datacenter's physical network. The synthetic interface is a VMbus device and uses the netvsc driver. ![]() When a virtual machine (VM) is created in Azure, a synthetic network interface is created for each virtual NIC in its configuration. ![]()
0 Comments
Leave a Reply. |