[Pkg-libvirt-maintainers] Bug#514803: Bug#514803: Bug#514803:

[Guido Günther]

tags 514803 + moreinfo

On Sun, Aug 09, 2009 at 02:33:15AM +0000, coders | brueckenschlaeger wrote:
> 
> project: virt-manager: internal error Failed to add tap interface 'vnet%d'
> to bridge 'virbr0' : No such device
> Package: virt-manager
> Version: 0.7.0-4
> Severity: important
> 
> *** Please type your report below this line ***
> 
> Error message reappeared after upgrading libvirt to 0.6.4-1
> 
> virt-manager denotes:
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/engine.py", line 493, in
> run_domain
>     vm.startup()
>   File "/usr/share/virt-manager/virtManager/domain.py", line 558, in
> startup
>     self.vm.create()
>   File "/usr/lib/python2.5/site-packages/libvirt.py", line 291, in create
>     if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: internal error Failed to add tap interface 'vnet%d' to bridge
> 'virbr0' : No such device
This looks as if the network is not running. Which network should the
device get attached to? What's the networks xml (virh net-dumpxml
<network>)? Can you reproduce with virsh? What does "virsh net-list
--all" show?

Cheers,
 -- Guido

P.S.: if possible please also check with 0.8.0 from experimental.