Why RHEL 7 and above still uses ethX naming for hv_netvsc driver in Microsoft Hyper-V environment ?

Solution Verified - Updated -

Issue

  • Why RHEL 7 still uses ethX naming for hv_netvsc driver in Microsoft Hyper-V environment
  • Microsoft Azure VM swaps around eth0 and eth1 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.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content