Re: [Users] oVirt Node Interface Renaming Problem
Am Donnerstag, den 30.01.2014, 10:43 -0800 schrieb David Li: Hi, I am using oVirt node 3.0.3. It seems systemd renames all the interfaces from ethx to something else. Not sure why but this creates lots of problems for some old scripts. For example: [root@localhost ~]# dmesg | grep -i eth0 [2.441579] bnx2 :10:00.0 eth0: Broadcom NetXtreme II BCM5709 1000Base-SX (C0) PCI Express found at mem fa00, IRQ 30, node addr 5c:f3:fc:20:6e:58 [ 27.222803] systemd-udevd[822]: renamed network interface eth0 to enp16s0f0 Is there anyway to prevent this? Hey David, as Antoni already pointed out, this is a basic Fedora / systemd feature. It actually solves problems and I'd also suggest - like Antoni - to take these new names. I don't know of a way of turning this naming off. This upstream document gives some more insight: http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ One note: The CentOS based Node is still using the old NIC naming. - fabian signature.asc Description: This is a digitally signed message part ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt Node Interface Renaming Problem
- Original Message - From: David Li david...@sbcglobal.net To: users@ovirt.org Sent: Thursday, January 30, 2014 7:43:09 PM Subject: [Users] oVirt Node Interface Renaming Problem Hi, I am using oVirt node 3.0.3. It seems systemd renames all the interfaces from ethx to something else. Not sure why but this creates lots of problems for some old scripts. For example: [root@localhost ~]# dmesg | grep -i eth0 [ 2.441579] bnx2 :10:00.0 eth0: Broadcom NetXtreme II BCM5709 1000Base-SX (C0) PCI Express found at mem fa00, IRQ 30, node addr 5c:f3:fc:20:6e:58 [ 27.222803] systemd-udevd[822]: renamed network interface eth0 to enp16s0f0 Is there anyway to prevent this? There is on a normal Fedora on which you can disable the new udev naming policy. In general I'd say that it is better to use the new consistent names (the old way of naming had problems to parallelize). Thanks. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
