Why RHEL 7 and above still uses ethX naming for hv_netvsc driver in Microsoft Hyper-V environment ?
Issue
- Why RHEL 7 still uses
ethX
naming forhv_netvsc
driver in Microsoft Hyper-V environment - Microsoft Azure VM swaps around
eth0
andeth1
randomly each time the system is booted - The Azure server cannot be connected. After rebooting, the issue had gone without any acting.
Environment
- Red Hat Enterprise Linux (RHEL) 7 and later
- Microsoft Hyper-V or Azure virtual machine
- Paravirtualized network interface with
hv_netvsc
driver
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.