Bug 517371

Summary:	Starting a guest with a non-exist bridge gives misleading error message
Product:	[Fedora] Fedora	Reporter:	Matthew Booth <mbooth>
Component:	libvirt	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	berrange, clalance, crobinso, itamar, markmc, veillard, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-08-18 12:40:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Booth 2009-08-13 16:28:02 UTC

Description of problem:
I have a guest containing the following:
    <interface type='bridge'>
      <mac address='00:16:3e:02:67:ef'/>
      <source bridge='virbr0'/>
      <model type='virtio'/>
    </interface>

(Note the source bridge name)

My default network has:
  <bridge name='virbr1' stp='on' forwardDelay='0' />

Clearly these don't match up. Starting a guest gives the following error message:

error: internal error Failed to add tap interface 'vnet%d' to bridge 'virbr0' : No such device

My attention is much more strongly drawn to 'vnet%d' than to 'virbr0' as the target of 'No such device'.

Additionally, note that after unsuccessfully attempting to start the guest, virsh dumpxml on the guest contains:
      <target dev='vnet%d'/>

This is not present in dumpxml before the guest has failed to start. It is never present in the configuration file on disk.

Version-Release number of selected component (if applicable):
libvirt-0.6.2-13.fc11.x86_64

Comment 1 Mark McLoughlin 2009-08-18 12:40:20 UTC

Thanks Matt, I've sent a fix upstream:

  http://www.redhat.com/archives/libvir-list/2009-August/msg00364.html