Ask Your Question
0

F18/Xen bridged network not coming up on boot

asked 2013-03-17 08:19:04 -0600

stormandsong gravatar image

Hello all,

I have a problem with Fedora 18. Booting as Dom0 on Xen, the network fails to come up on boot. If I manually start the network service after boot, it comes up just fine.

I have disabled NetworkManager because bridging is required. I did remember to enable the network service, and it does attempt to start the network service on boot, but fails with the following (from journalctl):

Mar 17 07:19:09 localhost.localdomain network[745]: Bringing up loopback interface:  [  OK  ]
Mar 17 07:19:09 localhost.localdomain kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Mar 17 07:19:09 localhost.localdomain network[745]: Bringing up interface br0:  ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device br0 does not seem to be present, delaying initialization.
Mar 17 07:19:09 localhost.localdomain /etc/sysconfig/network-scripts/ifup-eth[964]: Device br0 does not seem to be present, delaying initialization.
Mar 17 07:19:09 localhost.localdomain network[745]: [FAILED]
Mar 17 07:19:10 localhost.localdomain kernel: Bridge firewalling registered
Mar 17 07:19:10 localhost.localdomain kernel: r8169 0000:05:00.0 p14p1: link down
Mar 17 07:19:10 localhost.localdomain kernel: r8169 0000:05:00.0 p14p1: link down
Mar 17 07:19:10 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): p14p1: link is not ready
Mar 17 07:19:10 localhost.localdomain kernel: device p14p1 entered promiscuous mode
Mar 17 07:19:10 localhost.localdomain network[745]: Bringing up interface p14p1:  [  OK  ]
Mar 17 07:19:10 localhost.localdomain systemd[1]: network.service: control process exited, code=exited status=1
Mar 17 07:19:10 localhost.localdomain systemd[1]: Failed to start LSB: Bring up/down networking.
Mar 17 07:19:10 localhost.localdomain systemd[1]: Unit network.service entered failed state

What on earth am I missing? It seems like the system is trying to bring up the network before the bridge device exists.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2013-03-19 07:00:15 -0600

stormandsong gravatar image

The answer was so simple I am kicking myself right now.

The original contents of my ifcfg-br0 file:

DEVICE=br0
TYPE=bridge
BOOTPROTO=dhcp
ONBOOT=yes
DELAY=0
NM_CONTROLLED=no

The updated contents:

DEVICE=br0
TYPE=Bridge
BOOTPROTO=dhcp
ONBOOT=yes
DELAY=0
NM_CONTROLLED=no

Notice the TYPE= line.

The moral of the story: case-sensitivity will bite you in the butt.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-03-17 08:19:04 -0600

Seen: 2,519 times

Last updated: Mar 19 '13