New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
KVM Bridge doesn't get interface at boot, Any Idea ?
Mahfuz_SS_EHL
Host Rep, Veteran
in Help
Hello,
I installed KVM on My Home PC. But, the bridge is making weird issues.
Bridge isn't getting interface at the boot.
[root@node1 ~]# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.18c04d08cd06 no
So, I checked the Network.service log.
Apr 15 13:23:09 node1 systemd[1]: Starting LSB: Bring up/down networking...
Apr 15 13:23:09 node1 network[853]: Bringing up loopback interface: [ OK ]
Apr 15 13:23:09 node1 network[853]: Bringing up interface eno1: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device eno1 does not seem to be present, delaying initialization.
Apr 15 13:23:09 node1 network[853]: [FAILED]
Apr 15 13:23:13 node1 network[853]: Bringing up interface br0: [ OK ]
Apr 15 13:23:13 node1 systemd[1]: network.service: control process exited, code=exit
Apr 15 13:23:13 node1 systemd[1]: Failed to start LSB: Bring up/down networking.
Apr 15 13:23:13 node1 systemd[1]: Unit network.service entered failed state.
Apr 15 13:23:13 node1 systemd[1]: network.service failed.
Without any configuration change, when I issue command "systemctl start network.service", bridge gets interface & everything comes back.
Apr 15 13:26:15 node1 systemd[1]: Starting LSB: Bring up/down networking...
Apr 15 13:26:15 node1 network[1971]: Bringing up loopback interface: [ OK ]
Apr 15 13:26:15 node1 network[1971]: Bringing up interface eno1: [ OK ]
Apr 15 13:26:15 node1 network[1971]: Bringing up interface br0: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: [ OK ]
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 network[1971]: RTNETLINK answers: File exists
Apr 15 13:26:15 node1 systemd[1]: Started LSB: Bring up/down networking.
&
[root@node1 ~]# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.18c04d08cd06 no eno1
Any Workaround, why is this happening ??
Comments
Boot priority? Init bridge AFTER eno1 is up.
I understand the same but is there any guide how to do it ?? I can't find any tutorial to init bridge after eno1.
Here is tutorial: https://wiki.debian.org/BridgeNetworkConnections#Configuring_bridging_in_.2Fetc.2Fnetwork.2Finterfaces
Section "add the static IP options under the br0 interface setup". In case tutorial is not clear, paste your current network cfg here.
I have 3 files.
Then,
Lastly,
Set br0 "ONBOOT=yes" and eno1 "ONBOOT=no". Is this CentOS? I hate that OS for no apparent reason.
Yes, CentOS.