Red Hat Bugzilla – Bug 517371
Starting a guest with a non-exist bridge gives misleading error message
Last modified: 2009-08-18 08:40:20 EDT
Description of problem:
I have a guest containing the following:
(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:
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):
Thanks Matt, I've sent a fix upstream: