Description of problem:
We need to support configuration of IPv6 on virtual networks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
ip6tables support is currently also missing, see https://bugzilla.redhat.com/show_bug.cgi?id=567124
A series of patches to implement this feature has been pushed upstream:
It will be in the 0.8.7 release of libvirt
New virSocketAddr utility functions
New virNetworkDef utility functions
Fix logging of failed iptables commands
Consistently return 0 on success, -1 on failure in bridge_driver.c
Pass prefix rather than netmask into iptables functions
Make virtual network netmasks optional
Replace brSetInetAddress/brSetInetNetmask with brAddInetAddress
make the <dhcp> element optional in network.rng
Change virtual network XML parsing/formatting to support IPv6
Support multiple IP addresses on one network in bridge_driver.c
Update iptables.c to also support ip6tables.
Turn on IPv6 support in the bridge_driver.c virtual network driver
Run radvd for virtual networks with IPv6 addresses
I just created Bug 694155, requesting support for configuring IPv6 virtual networks in virt-manager.
This actually doesn't seem to be fixed. At least in part because https://bugzilla.redhat.com/show_bug.cgi?id=501934 turns off IPv6 on the bridge devices. Even having fixed that, I cannot get it to apply the addresses (with my xml file hand edited). It also doesn't radvd, or other wise send autoconfiguration, to the vms.
bug 501934 is irrelevant, because that is referring to an older libvirt where IPv6 was not supported. In current libvirt when you add an Ipv6 address in the configuration of the network XML, it will *not* disable IPv6 on the bridge. If you have problems with IPv6 support, please file new bugzillas with detailed information on the problem, rather than commenting on old closed bugs, since the latter will generally be ignored.