Bug 199414

Summary: Xen network-bridge: fails to start bridge because module not loaded
Product: [Fedora] Fedora Reporter: Mark McLoughlin <markmc>
Component: xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bstein, katzj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
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: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
xen-network-iptables-bridge.patch none

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> 3.0.2-16
- Fix network-bridge error (#199414)