[ovirt-users] Re: [External] : about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name
The naming convention is called BiosDevName and was introduced in kernel 2.6.27. It is
defined by the OS kernel you are using in the guest. It is not related to oVirt itself or
the KVM host.
In my case, I install my VMs passing "biosdevname=0 net.ifnames=0" during the OS
installation process, so all my VMs have ethX name style to make it easier to use
cloud-init and other scripts.
Marcos
From: Tommy Sway <sz_cuitao(a)163.com>
Sent: terça-feira, 24 de agosto de 2021 05:57
To: users(a)ovirt.org
Subject: [External] : [ovirt-users] about the network name rules on CentOS/Redhat 8 and
the cloud-init network interface name
Everybody is good!
As you all know, to use the client's network card name in cloud-init, you must fill in
the exact name of the network card interface.
This was easy in version 7 and before, which usually started with EN0.
After version 8, however, the naming conventions for network cards changed a lot. In my
own test environment, for example, I started with ENS3.
I'm not sure what naming convention it uses, which would make it impossible to specify
nic information using cloud-init.
Could you help me explain how to deal with this problem?
Thank you very much!