Simon Déziel, if you apply this workaroud you can't control your virtual machine throw virtmanager. It's not a good idea, in this case you can simply install and configure VM using console virsh or something like this. For now there is only one ability to use virt manager in a proper way: use virt manager from Maverick, in which you can manually define bridge name for VM to connect to. But I really can't understand why so simle option like system bridges discovering is broken for such a long time.
-- libvirt-bin hypervisor does not support virConnectNumOfInterfaces / unable to create domain with virt-manager using network bridge https://bugs.launchpad.net/bugs/520386 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
