That's because virsh uses the root libvirtd and virt manager uses the userspace one. The same result is achieved by running virt-manager with sudo.
Still, thanks a lot for the information because I was experiencing the same problem, but then on a personal Ubuntu server I access remotely. X-forwarding and sudo aren't the best of friends and so virsh is a very welcome alternative to virt-manager. I do believe that this means that the userspace virt-manager is isn't able to bridge. So I guessing that bug https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/192605 is still or again an issue. -- Error starting domain: virDomainCreate() failed Failed to add tap interface 'vnet%d' to bridge 'br0' : Permission denied https://bugs.launchpad.net/bugs/247677 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
