James Bardin wrote:
> Cole Robinson wrote:
>> What virt-manager version are you using?
>> Distro?
>
> libvirt: 0.4.0-2ubuntu8
> virt-manager: 0.5.3-0ubuntu10
>
> Distro: Ubuntu 8.04.1 server x86_64
>
>> Is there anything showing up in the shared device drop
>> down (even if you can't select it?)
>>
>
> The drop-down activates, but is empty.
>
>> Also if you could attach ~/.virt-manager/virt-manager.log
>> it might help.
>>
>
> This group popped up a lot yesterday:
>
> [Tue, 19 Aug 2008 14:55:19 virt-manager 5811] WARNING (connection:494)
> Unable to list active networks
> [Tue, 19 Aug 2008 14:55:19 virt-manager 5811] WARNING (connection:498)
> Unable to list inactive networks
> [Tue, 19 Aug 2008 14:55:19 virt-manager 5811] ERROR (engine:158) Could
> not refresh connection qemu:///system
> <class 'libvirt.libvirtError'> virConnectListDomainsID() failed Broken pipe
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/engine.py", line 152, in _tick
> self.connections[uri]["connection"].tick()
> File "/usr/share/virt-manager/virtManager/connection.py", line 550, in
> tick
> newActiveIDs = self.vmm.listDomainsID()
> File "/usr/lib/python2.5/site-packages/libvirt.py", line 795, in
> listDomainsID
> if ret is None: raise libvirtError ('virConnectListDomainsID()
> failed', conn=self)
> libvirtError: virConnectListDomainsID() failed Broken pipe
>
This is probably from a libvirtd restart while virt-manager
was running. If so, nothing to worry about.
>
> Here's the output when I try to add a new network device:
>
> [Wed, 20 Aug 2008 10:57:39 virt-manager 6673] ERROR (connection:158)
> Unable to connect to HAL to list network devices: '%s'<class
> 'dbus.exceptions.DBusException'>
> org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal
> was not provided by any .service files
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/connection.py", line 144, in
> detect_network_devices
> hal_object = self.bus.get_object('org.freedesktop.Hal',
> '/org/freedesktop/Hal/Manager')
> File "/var/lib/python-support/python2.5/dbus/bus.py", line 244, in
> get_object
> follow_name_owner_changes=follow_name_owner_changes)
> File "/var/lib/python-support/python2.5/dbus/proxies.py", line 241, in
> __init__
> self._named_service = conn.activate_name_owner(bus_name)
> File "/var/lib/python-support/python2.5/dbus/bus.py", line 183, in
> activate_name_owner
> self.start_service_by_name(bus_name)
> File "/var/lib/python-support/python2.5/dbus/bus.py", line 281, in
> start_service_by_name
> 'su', (bus_name, flags)))
> File "/var/lib/python-support/python2.5/dbus/connection.py", line 607,
> in call_blocking
> message, timeout)
> DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Hal was not provided by any .service files
> [Wed, 20 Aug 2008 10:57:47 virt-manager 6673] ERROR (console:106) Cannot
> initialize notification
> systemorg.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute
> dbus-launch to autolaunch D-Bus session
>
>
This is the problem: we use dbus to contact hal to list
physical net devices on the system, then we probe their
/sys path to determine if they are in a bridge, among
other things.
Make sure hald (or some equivalently named service) is
running. Bar that, you'll probably have to ask the
ubuntu folks.
Thanks,
Cole
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
