Public bug reported:
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).
** Affects: orchestra (Ubuntu)
Importance: Undecided
Status: Invalid
** Tags: libvirtd
** Tags added: libvirtd
** Changed in: orchestra (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245321
Title:
UFW blocks libvirtd default network from starting automatically in
Saucy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/orchestra/+bug/1245321/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
