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).
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? alFirewallRules :1895 : failed to add iptables rule to allow DHCP requests from 'virbr0'
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).