Debian Bug report logs - #514803
internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : No such device

version graph

Package: libvirt-bin; Maintainer for libvirt-bin is Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>; Source for libvirt-bin is src:libvirt.

Reported by: Nico Prenzel <nico.prenzel@pn-systeme.de>

Date: Tue, 10 Feb 2009 23:24:04 UTC

Severity: normal

Tags: moreinfo

Found in version libvirt/0.6.0-1

Done: Guido Günther <agx@sigxcpu.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Tue, 10 Feb 2009 23:24:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Nico Prenzel <nico.prenzel@pn-systeme.de>:
New Bug report received and forwarded. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Tue, 10 Feb 2009 23:24:07 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Nico Prenzel <nico.prenzel@pn-systeme.de>
To: submit@bugs.debian.org
Subject: internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : No such device
Date: Wed, 11 Feb 2009 00:19:09 +0100
[Message part 1 (text/plain, inline)]
Package: libvirt-bin
Version:0.6.0-1

Hi,

After upgrade to libvirt-bin 0.6.0-1 I do get the following error message 
when I try to start a guest:
internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : 
No such device

With libvirt-bin version 0.5.1-5 everything worked with the same 
configuration.
After downgrade to libvirt-bin 0.5.1-5 again, everything work as expected.

NicoP.
[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Wed, 11 Feb 2009 08:54:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Nico Prenzel <nico.prenzel@pn-systeme.de>:
Extra info received and forwarded to list. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Wed, 11 Feb 2009 08:54:02 GMT) Full text and rfc822 format available.

Message #10 received at 514803@bugs.debian.org (full text, mbox):

From: Nico Prenzel <nico.prenzel@pn-systeme.de>
To: 514803@bugs.debian.org
Subject: missed information
Date: Wed, 11 Feb 2009 09:50:08 +0100
[Message part 1 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Fri, 13 Feb 2009 10:39:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Guido Günther <agx@sigxcpu.org>:
Extra info received and forwarded to list. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Fri, 13 Feb 2009 10:39:05 GMT) Full text and rfc822 format available.

Message #15 received at 514803@bugs.debian.org (full text, mbox):

From: Guido Günther <agx@sigxcpu.org>
To: Nico Prenzel <nico.prenzel@pn-systeme.de>, 514803@bugs.debian.org
Subject: Re: [Pkg-libvirt-maintainers] Bug#514803: internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : No such device
Date: Fri, 13 Feb 2009 11:35:35 +0100
On Wed, Feb 11, 2009 at 12:19:09AM +0100, Nico Prenzel wrote:
> Package: libvirt-bin
> Version:0.6.0-1
> 
> Hi,
> 
> After upgrade to libvirt-bin 0.6.0-1 I do get the following error message 
> when I try to start a guest:
> internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : 
> No such device
What kind of guest? What kind of network? Is virbr0 already up
(you can check ifconfig)? Does "virsh net-start <yournetwork>" help?
 -- Guido




Tags added: moreinfo Request was from Guido Günther <agx@sigxcpu.org> to control@bugs.debian.org. (Tue, 17 Mar 2009 15:39:20 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Tue, 07 Apr 2009 20:12:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Laurent Vivier <laurent@vivier.eu>:
Extra info received and forwarded to list. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Tue, 07 Apr 2009 20:12:08 GMT) Full text and rfc822 format available.

Message #22 received at 514803@bugs.debian.org (full text, mbox):

From: Laurent Vivier <laurent@vivier.eu>
To: Debian Bug Tracking System <514803@bugs.debian.org>
Subject: libvirt-bin: "virsh net-create /etc/libvirt/qemu/networks/default.xml" allows to start the VM
Date: Tue, 07 Apr 2009 22:09:34 +0200
Package: libvirt-bin
Version: 0.4.6-10
Followup-For: Bug #514803


This bug is found using virt-manager.

The VM has been created and run without problem the first time.
After a reboot of the host, when I try to start the VM the problem 
appears.

My VM is defined by:

<domain type='kvm'>
  <name>debian-i386</name>
  <uuid>a8c92ab9-870d-3965-3ab4-5100d43ff5e4</uuid>
  <memory>524288</memory>
  <currentMemory>524288</currentMemory>
  <vcpu>2</vcpu>
  <os>
    <type arch='x86_64' machine='pc'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='cdrom'>
      <target dev='hdc' bus='ide'/>
      <readonly/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/mapper/Quad-debian--i386'/>
      <target dev='vda' bus='virtio'/>
    </disk>
    <interface type='network'>
      <mac address='54:52:00:0a:7f:c2'/>
      <source network='default'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/3'/>
      <target port='0'/>
    </serial>
    <console type='pty' tty='/dev/pts/3'>
      <source path='/dev/pts/3'/>
      <target port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='fr'/>
    <sound model='es1370'/>
  </devices>
</domain>

virt-manager.log:

[mar, 07 avr 2009 21:51:59 virt-manager 6727] DEBUG (error:67) Uncaught 
Error: Error starting domain: internal error Network 'default' not found 
: Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 531, in 
run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 380, in 
startup
    self.vm.create()
  File "/usr/lib/python2.5/site-packages/libvirt.py", line 262, in 
create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', 
dom=self)
libvirtError: internal error Network 'default' not found

If I run:
$ sudo virsh net-create /etc/libvirt/qemu/networks/default.xml
Network default created from /etc/libvirt/qemu/networks/default.xml

The VM can be started without problem.

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libvirt-bin depends on:
ii  adduser                3.110             add and remove users and groups
ii  libavahi-client3       0.6.23-3lenny1    Avahi client library
ii  libavahi-common3       0.6.23-3lenny1    Avahi common library
ii  libc6                  2.7-18            GNU C Library: Shared libraries
ii  libdbus-1-3            1.2.1-5           simple interprocess messaging syst
ii  libgcrypt11            1.4.1-1           LGPL Crypto library - runtime libr
ii  libgnutls26            2.4.2-6+lenny1    the GNU TLS library - runtime libr
ii  libgpg-error0          1.4-2             library for common error values an
ii  libpolkit-dbus2        0.9-2             library for accessing PolicyKit vi
ii  libpolkit2             0.9-2             library for accessing PolicyKit
ii  libreadline5           5.2-3.1           GNU readline and history libraries
ii  libsasl2-2             2.1.22.dfsg1-23   Cyrus SASL - authentication abstra
ii  libselinux1            2.0.65-5          SELinux shared libraries
ii  libtasn1-3             1.4-1             Manage ASN.1 structures (runtime)
ii  libvirt0               0.4.6-10          library for interfacing with diffe
ii  libxenstore3.0         3.2.1-2           Xenstore communications library fo
ii  libxml2                2.6.32.dfsg-5     GNOME XML library
ii  logrotate              3.7.1-5           Log rotation utility
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages libvirt-bin recommends:
ii  bridge-utils                  1.4-5      Utilities for configuring the Linu
ii  dnsmasq                       2.45-1     A small caching DNS proxy and DHCP
ii  iptables                      1.4.2-6    administration tools for packet fi
ii  netcat-openbsd                1.89-3     TCP/IP swiss army knife
ii  qemu                          0.9.1-10   fast processor emulator

Versions of packages libvirt-bin suggests:
pn  policykit                     <none>     (no description available)

-- no debconf information




Reply sent to Guido Günther <agx@sigxcpu.org>:
You have taken responsibility. (Tue, 07 Apr 2009 20:27:08 GMT) Full text and rfc822 format available.

Notification sent to Nico Prenzel <nico.prenzel@pn-systeme.de>:
Bug acknowledged by developer. (Tue, 07 Apr 2009 20:27:08 GMT) Full text and rfc822 format available.

Message #27 received at 514803-done@bugs.debian.org (full text, mbox):

From: Guido Günther <agx@sigxcpu.org>
To: 514803-done@bugs.debian.org
Subject: Re: [Pkg-libvirt-maintainers] Bug#514803: libvirt-bin: "virsh net-create /etc/libvirt/qemu/networks/default.xml" allows to start the VM
Date: Tue, 7 Apr 2009 22:24:27 +0200
Version: 0.4.6-10

On Tue, Apr 07, 2009 at 10:09:34PM +0200, Laurent Vivier wrote:
> [mar, 07 avr 2009 21:51:59 virt-manager 6727] DEBUG (error:67) Uncaught 
> Error: Error starting domain: internal error Network 'default' not found 
> : Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/engine.py", line 531, in 
> run_domain
>     vm.startup()
>   File "/usr/share/virt-manager/virtManager/domain.py", line 380, in 
> startup
>     self.vm.create()
>   File "/usr/lib/python2.5/site-packages/libvirt.py", line 262, in 
> create
>     if ret == -1: raise libvirtError ('virDomainCreate() failed', 
> dom=self)
> libvirtError: internal error Network 'default' not found
> 
> If I run:
> $ sudo virsh net-create /etc/libvirt/qemu/networks/default.xml
> Network default created from /etc/libvirt/qemu/networks/default.xml
> 
> The VM can be started without problem.
You need to start the network then. This is not a bug in
virt-manager/libvirt. If you want to autostart the network use
	virsh net-autostart default
Cheers and thanks for reporting back!
 -- Guido




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Tue, 07 Apr 2009 21:03:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Nico Prenzel <nico.prenzel@pn-systeme.de>:
Extra info received and forwarded to list. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Tue, 07 Apr 2009 21:03:02 GMT) Full text and rfc822 format available.

Message #32 received at 514803@bugs.debian.org (full text, mbox):

From: Nico Prenzel <nico.prenzel@pn-systeme.de>
To: 514803@bugs.debian.org
Date: Tue, 7 Apr 2009 23:00:35 +0200
If I remember the behaviour correctly I've had my "default" network 
disabled and set to another IP adress/subnet. After I've enabled the 
network the guest started. But why I have to mantain an, unwanted default 
network? Of course, I've configured my own "DMZ" virtual network. Or, do 
I've undestood something wrong?

P.S.: After I've got my guest running I've driven into another problem. 
All my guest configured for usage of virtio-net couldn't connect to the 
internal virtual network. After switching back to e1000 all worked fine 
again. I think it is the bug described here: 
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/331128

Sorry, for the noise. But I wasn't clear to me how I first had resolved 
this problem.

Thanks for mantain the cool debian package.




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Wed, 08 Apr 2009 07:09:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Guido Günther <agx@sigxcpu.org>:
Extra info received and forwarded to list. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Wed, 08 Apr 2009 07:09:02 GMT) Full text and rfc822 format available.

Message #37 received at 514803@bugs.debian.org (full text, mbox):

From: Guido Günther <agx@sigxcpu.org>
To: Nico Prenzel <nico.prenzel@pn-systeme.de>, 514803@bugs.debian.org
Subject: Re: [Pkg-libvirt-maintainers] Bug#514803:
Date: Wed, 8 Apr 2009 09:04:25 +0200
On Tue, Apr 07, 2009 at 11:00:35PM +0200, Nico Prenzel wrote:
> If I remember the behaviour correctly I've had my "default" network 
> disabled and set to another IP adress/subnet. After I've enabled the 
> network the guest started. But why I have to mantain an, unwanted default 
> network? Of course, I've configured my own "DMZ" virtual network. Or, do 
> I've undestood something wrong?
You only have to have the default network running if you use it. Your VM
configuration has:

    <interface type='network'>
      <mac address='54:52:00:0a:7f:c2'/>
      <source network='default'/>
    </interface>

So as long as you reference it, you need to have it running. Drop that
from your VM configuration and you won't need it.

[..snip..] 
> Thanks for mantain the cool debian package.
Thanks for helping to improve the package by filing reports!
 -- Guido




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Sun, 09 Aug 2009 02:36:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to coders | brueckenschlaeger <coders@brueckenschlaeger.de>:
Extra info received and forwarded to list. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Sun, 09 Aug 2009 02:36:02 GMT) Full text and rfc822 format available.

Message #42 received at 514803@bugs.debian.org (full text, mbox):

From: coders | brueckenschlaeger <coders@brueckenschlaeger.de>
To: <514803@bugs.debian.org>
Subject: Re: [Pkg-libvirt-maintainers] Bug#514803:
Date: Sun, 09 Aug 2009 02:33:15 +0000
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


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30.4-stp (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages virt-manager depends on:
ii  libatk1.0-0                  1.26.0-1    The ATK accessibility toolkit
ii  libc6                        2.9-12      GNU C Library: Shared
libraries
ii  libcairo2                    1.8.6-2+b1  The Cairo 2D vector graphics
libra
ii  libfontconfig1               2.6.0-4     generic font configuration
library
ii  libfreetype6                 2.3.9-4.1   FreeType 2 font engine, shared
lib
ii  libglib2.0-0                 2.20.1-2    The GLib library of C routines
ii  libgtk2.0-0                  2.16.1-2    The GTK+ graphical user
interface
ii  libpango1.0-0                1.24.0-3+b1 Layout and rendering of
internatio
ii  librsvg2-common              2.26.0-1    SAX-based renderer library for
SVG
ii  python-dbus                  0.83.0-1    simple interprocess messaging
syst
ii  python-glade2                2.14.1-3    GTK+ bindings: Glade support
ii  python-gnome2                2.26.1-1    Python bindings for the GNOME
desk
ii  python-gtk-vnc               0.3.8-2     A VNC viewer widget for GTK+
(Pyth
ii  python-gtk2                  2.14.1-3    Python bindings for the GTK+
widge
ii  python-libvirt               0.6.4-1     libvirt Python bindings
ii  python-urlgrabber            3.1.0-4     A high-level cross-protocol
url-gr
ii  python-vte                   1:0.20.5-1  Python bindings for the VTE
widget
ii  python2.5                    2.5.4-1     An interactive high-level
object-o
ii  virtinst                     0.400.3-5   Programs to create and clone
virtu

Versions of packages virt-manager recommends:
ii  hal                           0.5.11-8   Hardware Abstraction Layer
ii  libvirt-bin                   0.6.4-1    the programs for the libvirt
libra

Versions of packages virt-manager suggests:
ii  virt-viewer                   0.0.3-2    Displaying the graphical
console o

-- no debconf information




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>:
Bug#514803; Package libvirt-bin. (Sun, 09 Aug 2009 10:42:29 GMT) Full text and rfc822 format available.

Acknowledgement sent to Guido Günther <agx@sigxcpu.org>:
Extra info received and forwarded to list. Copy sent to Debian Libvirt Maintainers <pkg-libvirt-maintainers@lists.alioth.debian.org>. (Sun, 09 Aug 2009 10:42:29 GMT) Full text and rfc822 format available.

Message #47 received at 514803@bugs.debian.org (full text, mbox):

From: Guido Günther <agx@sigxcpu.org>
To: coders | brueckenschlaeger <coders@brueckenschlaeger.de>, 514803@bugs.debian.org
Subject: Re: [Pkg-libvirt-maintainers] Bug#514803: Bug#514803:
Date: Sun, 9 Aug 2009 12:34:40 +0200
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.




No longer marked as found in versions libvirt/0.4.6-10. Request was from Andreas Beckmann <anbe@debian.org> to control@bugs.debian.org. (Fri, 01 Nov 2013 22:33:30 GMT) Full text and rfc822 format available.

No longer marked as fixed in versions 0.4.6-10. Request was from Andreas Beckmann <anbe@debian.org> to control@bugs.debian.org. (Fri, 01 Nov 2013 22:33:31 GMT) Full text and rfc822 format available.

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Sat, 30 Nov 2013 07:26:44 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Mon Apr 21 06:04:01 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.