[ovirt-users] Re: [External] : about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name
You have two options: - If installing the VM using a pxe environment/network server, you can add this options as kernel_extra boot options at the Run Once install procedure. - if installing the VM using an ISO image, edit the install menu entry and add this option at the end of line. Marcos -Original Message- From: Tommy Sway Sent: terça-feira, 24 de agosto de 2021 11:34 To: Marcos Sungaila ; users@ovirt.org Subject: [ovirt-users] Re: [External] : about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name Thank you! But where to set in on oVirt Platform when I create the VM ? -Original Message- From: Marcos Sungaila Sent: Tuesday, August 24, 2021 9:10 PM To: Tommy Sway ; users@ovirt.org Subject: RE: [External] : [ovirt-users] 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 Sent: terça-feira, 24 de agosto de 2021 05:57 To: users@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! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!ACWV5N9M2RV99hQ!Ycf4LjLfnL9oqrPnfm7E7c7pDjwu9mjeBlHfxftqDx1TQiofzsFeU2IEmE08GkxRr4M$ oVirt Code of Conduct: https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-guidelines/__;!!ACWV5N9M2RV99hQ!Ycf4LjLfnL9oqrPnfm7E7c7pDjwu9mjeBlHfxftqDx1TQiofzsFeU2IEmE08J-8c7Nc$ List Archives: https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovirt.org/message/AZZGRDFPJ77FMJA4HJCEXR6PPOWIMVDR/__;!!ACWV5N9M2RV99hQ!Ycf4LjLfnL9oqrPnfm7E7c7pDjwu9mjeBlHfxftqDx1TQiofzsFeU2IEmE08agTnvXs$ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GDKFHRGUDRODZUSKAB77Q4CIOGI2WOIS/
[ovirt-users] Re: [External] : about the network name rules on CentOS/Redhat 8 and the cloud-init network interface name
Thank you! But where to set in on oVirt Platform when I create the VM ? -Original Message- From: Marcos Sungaila Sent: Tuesday, August 24, 2021 9:10 PM To: Tommy Sway ; users@ovirt.org Subject: RE: [External] : [ovirt-users] 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 Sent: terça-feira, 24 de agosto de 2021 05:57 To: users@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! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AZZGRDFPJ77FMJA4HJCEXR6PPOWIMVDR/
[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 Sent: terça-feira, 24 de agosto de 2021 05:57 To: users@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! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HK7S7XZQ2T3ENVSQPUQZAIXCBFJUHWZO/
