UFW blocks libvirtd default network from starting automatically in Saucy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Saucy |
Fix Released
|
High
|
Unassigned |
Bug Description
=======
SRU justification
=======
1. Impact: libvirt may fail to start
2. Development fix: have libvirt use -w flag to iptables to have it wait rather than fail on lock contention
3. Stable fix: same as dev fix
4. Test case: install ufw and libvirt; reboot a few times.
5. Regression potential: there should be none, this only passes the -w flag to iptables if it is supported.
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/
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 : networkAddGener
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: | added: patch |
no longer affects: | ufw |
description: | updated |
Changed in libvirt (Ubuntu Saucy): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in libvirt (Ubuntu): | |
importance: | Medium → High |
I don't believe this is a libvirt bug, but I'm not sure what the
right answer is.
affects: ufw