[et-mgmt-tools] no longer can create shared network

[Mark Chaney]

You mean something like this?

[Fri, 11 Jul 2008 14:48:02 virt-manager 28541] ERROR (connection:175) Unable
to connect to HAL to list network devices: '%s'dbus_bindings.DBusException
Could not get owner of name 'org.freedesktop.Hal': no such name
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 155, in
__init__
    self.hal_iface.connect_to_signal("DeviceAdded",
self._net_phys_device_added)
  File "/usr/lib64/python2.4/site-packages/dbus/_dbus.py", line 291, in
connect_to_signal
    self._obj.connect_to_signal(signal_name, handler_function,
dbus_interface, **keywords)
  File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 151, in
connect_to_signal
    path=self._object_path,
  File "/usr/lib64/python2.4/site-packages/dbus/_dbus.py", line 179, in
add_signal_receiver
    named_service = bus_object.GetNameOwner(named_service,
dbus_interface='org.freedesktop.DBus')
  File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 25, in
__call__
    ret = self._proxy_method (*args, **keywords)
  File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 102, in
__call__
    reply_message = self._connection.send_with_reply_and_block(message,
timeout)
  File "dbus_bindings.pyx", line 455, in
dbus_bindings.Connection.send_with_reply_and_block
DBusException: Could not get owner of name 'org.freedesktop.Hal': no such
name

Also, how in the world can RHEL 5.2 be considered old?


Mark Chaney wrote:
> I am running Centos 5.2 x86_64, Xen 3.2.1, and virt-manager 0.5.4. 
> 
> Ever since I upgraded xen and virt-manager to the newest, I cant seem to
> create a new xen pv domU with a shared network device (bridged I guess?).
> Nothing shows up in the shared network device list. Heck, even when I try
> the default network option, the domU created cant connect to the internet.
I
> have 3 domU's that I created before this upgrade that seem to work fine.
Any
> ideas?
> 
> Thanks,
> Mark
> 

Check ~/.virt-manager/virt-manager.log and see if there is a traceback
anywhere.
If you pulled down the stock 0.5.4 my guess is you will hit a number of
issues
on centos since we use newer dbus calls and rely on updated versions of
gtk-vnc
and possibly libvirt.

- Cole