+++ This bug was initially created as a clone of Bug #950755 +++ Description of problem: Libvirt fails to start virtual networks with DHCP enabled. Version-Release number of selected component (if applicable): dnsmasq-2.65-6.fc18.x86_64 How reproducible: Always Steps to Reproduce: 1. Start libvirtd with default config. Actual results: "default" virtual network doesn't start Expected results: "default" virtual network starts More info: rebuilding the dnsmasq-2.66-3.fc19 src.rpm for fc18 does indeed fix the problem for me. Can we please have it built and pushed to stable? --- Additional comment from Jiri Denemark on 2013-04-12 05:30:54 EDT --- As far as I know, this should be fixed in dnsmasq-2.66rc5 --- Additional comment from Fedora Update System on 2013-04-12 06:08:20 EDT --- dnsmasq-2.66-1.rc5.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/dnsmasq-2.66-1.rc5.fc19 --- Additional comment from Fedora Update System on 2013-04-18 13:24:33 EDT --- Package dnsmasq-2.66-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnsmasq-2.66-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5540/dnsmasq-2.66-2.fc19 then log in and leave karma (feedback). --- Additional comment from Fedora Update System on 2013-04-22 13:19:49 EDT --- Package dnsmasq-2.66-3.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnsmasq-2.66-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5540/dnsmasq-2.66-3.fc19 then log in and leave karma (feedback). --- Additional comment from Fedora Update System on 2013-05-03 21:46:06 EDT --- dnsmasq-2.66-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. --- Additional comment from Suren Karapetyan on 2013-06-24 03:13:57 EDT --- Can we have this fixed on Fedora 18? --- Additional comment from Tomas Hozza on 2013-06-24 03:19:04 EDT --- (In reply to Suren Karapetyan from comment #6) > Can we have this fixed on Fedora 18? Sure, can you please create F18 Bug? Thanks!
+1 to fixing this, I started hitting it today on F18 (looks like its ever since dnsmasq-2.65-6.fc18 was push to updates)
Can you please test the following build? http://koji.fedoraproject.org/koji/taskinfo?taskID=5612726 Thanks!
works for me
dnsmasq-2.65-7.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/dnsmasq-2.65-7.fc18
Package dnsmasq-2.65-7.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnsmasq-2.65-7.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-13204/dnsmasq-2.65-7.fc18 then log in and leave karma (feedback).
Had the exact same problem - the updates-testing does fix it. Thanks for fixing this so quickly!
dnsmasq-2.65-7.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.