UFW blocks libvirtd default network from starting automatically in Saucy

Bug #1245321 reported by Claude Durocher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
orchestra (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Running KVM under Ubuntu 13.10 64 bits.

When UFW is enabled, the default network won't start automatically when set to do so. Manual startup of the network must be done before starting the first guest.

Error in /var/log/libvirt/libvirtd.log when UFW is enabled :

2013-10-28 02:53:31.732+0000: 1485: error : virCommandWait:2348 : internal error: Child process (/sbin/iptables --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT) unexpected exit status 4: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
2013-10-28 02:53:31.732+0000: 1485: error : networkAddGeneralFirewallRules:1895 : failed to add iptables rule to allow DHCP requests from 'virbr0'

Disabling UFW and rebooting solves the issue (default network is started automatically).

This behaviour is new in 13.10 (it was working fine in 13.04 and before).

Tags: libvirtd
Revision history for this message
Claude Durocher (claude-d) wrote :

Sorry, wrong section for reporting the bug. Please delete it.

tags: added: libvirtd
Changed in orchestra (Ubuntu):
status: New → Invalid
Revision history for this message
Ads20000 (ads20000) wrote :

In the future, you can just click the arrow next to 'orchestra (Ubuntu)' and then just change the package and click `Save Changes`

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.