On Wed, Jun 08, 2011 at 09:42:22AM -0600, Trever L. Adams wrote: > On 06/08/2011 09:32 AM, Tom Hughes wrote: > > > > Works fine for my VMs with bridged networking - they see the radvd on > > the network and configure an address. > > > > Tom > > > Would you care to share some documentation of some kind? > > <network> > <name>TheCommons</name> > <uuid>....</uuid> > <forward mode='route'/> > <bridge name='virbr0' stp='off' delay='0' /> > <ip address='10.0.1.1' netmask='255.255.255.0'> > </ip> > <ip family='ipv6' address='fd00:xxxx:xxxx:1::1' prefix='64'> > </ip> > <ip family='ipv6' address='2001:xxxx:xxxx:0::1' prefix='64'> > </ip> > </network> > > That didn't automatically add any of the ipv6 addresses. As I said, no > radvd. If I read the bug reports correctly, it is supposed to be automagic. Yes, when you add that <ip family='ipv6'> line and then restart the network (virsh net-destroy TheCommons && virsh net-create TheCommons) it should have started radvd automatically. The guest should then have automatically got an address from radvd. This all works fine in my testing. > Also, the systctl stuff mentioned in the bugs reports I mentioned were > set to not allow ipv6, etc. Did you override these defaults somewhere? That other bug is irrelevant, refering to much older libvirt prior to the introduction of IPv6 support. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
