It is indeed a pain. I'd like to see this get fixed eventually. Even the upstream patch that's around somewhere that allows you to simply manually specifiy a bridge would be pretty good.
It's not *impossible* to use libvirt/KVM in these conditions, incidentally, it's just that after defining a new domain you need to manually alter the domain's configuration: virsh qemu+ssh://[email protected]/system edit <domainname> (edit as appropriate), and then to change the default NAT network to bridge simply replace <interface type='network'> with type='bridge' and <source network='default'/> with <source bridge='br0'/> Not ideal, but not that hard either. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
