Bug 199414 - Xen network-bridge: fails to start bridge because module not loaded
Summary: Xen network-bridge: fails to start bridge because module not loaded
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xen   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-19 13:44 UTC by Mark McLoughlin
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-07-19 15:36:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
xen-network-iptables-bridge.patch (553 bytes, patch)
2006-07-19 13:44 UTC, Mark McLoughlin
no flags Details | Diff

Description Mark McLoughlin 2006-07-19 13:44:36 UTC
Trying to start domU with latest xen, I'm seeing this in /var/log/xend.log:

  VmError: Device 0 (vif) could not be connected. Hotplug scripts not working.

With such a helpful error message, the problem was obvious of course :-)


Issue is that the network-bridge script has been changed around a bit, and it
was failing with:

  error: "net.bridge.bridge-nf-call-arptables" is an unknown key

The bridge module wasn't being loaded.

Seems that brctl was previously being run before this point, and the ioctl is
uses would cause the bridge module to be loaded.

Attaching a fixed version of xen-network-iptables-bridge.patch which tweaks the
kernel params after starting the bridge.

Comment 1 Mark McLoughlin 2006-07-19 13:44:37 UTC
Created attachment 132682 [details]
xen-network-iptables-bridge.patch

Comment 2 Mark McLoughlin 2006-07-19 15:36:54 UTC
* Wed Jul 19 2006 Mark McLoughlin <markmc@redhat.com> 3.0.2-16
- Fix network-bridge error (#199414)



Note You need to log in before you can comment on or make changes to this bug.