Red Hat Bugzilla – Bug 744814
dnsmasq breaks IPv6 virtual networks in libvirt
Last modified: 2012-11-19 06:47:11 EST
Description of problem:
dnsmasq: no interface with address (IPv6 address)
I get the following with my hosts that worked fine in Fedora 15. This keeps the virtual nets from starting and therefore the hosts.
Version-Release number of selected component (if applicable):
This is a very serious and very annoying regression. IPv6 is starting to be used. I use it heavily and depend on it.
The url above provides more information about what is going on. The patch in comment #10 appears to be correct. That or libvirt needs to set the bridge devices to active for dnsmasq to work correctly (comment #5).
In the url https://bbs.archlinux.org/viewtopic.php?id=123855 mentioned on the above page it mentions some information that makes me very much believe that this is another manifestation of bug #727924.
Ok, this is a bug in libvirt and company, not dnsmasq.
Sorry if this is an overly simplistic view, I haven't been able to dig into libvirt.
It appears libvirt is doing the following:
Create Bridge (virbrX)
Start dnsmasq on bridge
Create network(s) (vnetX) and attach them to bridge
Start virutal machine
With the patch in the kernel to not activate a bridge until a device is attached, this doesn't work. Whether or not this patch to the kernel (from 2.3.38 or thereabouts) is removed or not, should not the following work and work well?
Create networks and attach to bridge
Start virutal machine
I don't believe dnsmasq is needed except by virtual machines. For the non-error case, isn't this simply a matter of just changing the order of a few lines of code? In the error case, obviously it requires the removal of all the virtual networks, which in the old method, would not have existed yet.
Or, to keep the order of things, create a dummy device and attach it to the bridge, once dnsmasq is started and the virtual networks started, remove the dummy device. This might be the smaller change set.
Guys, dnsmasq 2.59 was fixed this bug.
Proof link: http://thekelleys.org.uk/dnsmasq/CHANGELOG
I've checked this.
dnsmasq-2.59-2.fc16 has been submitted as an update for Fedora 16.
Package dnsmasq-2.59-2 has fix this bug for me.
Thank you Alexei!
I concur. I believe this fixes the problem fully. Thank you very much!
Thank you Trever for the report/test!
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnsmasq-2.59-2.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dnsmasq-2.59-3.fc16 has been submitted as an update for Fedora 16.
dnsmasq-2.59-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
This has largely fixed the problem. Occasionally it still happens.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.