On Tue, 2009-07-28 at 12:58 +0200, Gianluca Sforna wrote:
> On Tue, Jul 28, 2009 at 12:29 PM, Mark McLoughlin<markmc(a)redhat.com> wrote:
>> Can you use 'virsh edit' to add e.g.:
>>
>> <interface type='bridge'>
>> <mac address='54:52:00:49:73:9a'/>
>> <source bridge='br0'/>
>> </interface>
> This leads to another traceback when starting the VM:
Did you file a bug with the first traceback?
> 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 573, in
startup
> self.vm.create()
> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 287, in
create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: internal error Failed to add tap interface 'vnet%d' to
> bridge 'br0' : No such device
What exactly is the guest's configuration? Is 'vnet%d' mentioned
anywhere? What version of libvirt?
>> See also:
>>
>>
http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging
>>
https://fedoraproject.org/wiki/Reporting_virtualization_bugs#Networking
> Thanks for the pointers, I found this suspicious message in virt-manager.log:
>
> [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (proxies:400)
> Introspect error on
> :1.1:/org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7:
> dbus.exceptions.DBusException: No device with id
> /org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7
> [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] DEBUG (proxies:403)
> Executing introspect queue due to error
> [Tue, 28 Jul 2009 12:54:16 virt-manager 3653] ERROR (connection:218)
> Exception in handler for D-Bus signal:
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
> 214, in maybe_handle_message
> self._handler(*args, **kwargs)
> File "/usr/share/virt-manager/virtManager/connection.py", line 170,
> in _net_phys_device_added
> if objif.QueryCapability("net"):
> File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in
__call__
> return self._proxy_method(*args, **keywords)
> File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in
__call__
> **keywords)
> File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
> 630, in call_blocking
> message, timeout)
> DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id
> /org/freedesktop/Hal/devices/net_d2_eb_bc_ff_01_a7
>
> still confused...
Odd, dbus telling us a device has added and then failing to find it.
Seen this one before Cole?
I don't think so. Filing a bug with both those tracebacks would be best.
Thanks,
Cole