PBI: virt-manager 0.9.1 can't use qemu+ssh

[Alvin]

virt-manager 0.9.1 (also on 0.9.0)

It's not possible to connect using qemu+ssh. I don't have any servers configured to use the other connection methods, so these are not tested.

Tested qemu+ssh to:

• Debian wheezy (libvir 0.9.9)
• Debian 6.0.4 (libvir 0.8.3)
• Ubuntu 10.04.4 (libvir 0.7.5)

Debug code is when connection to Debian 6.0.4 server.

> virt-manager --debug --connect=qemu+ssh://virthost01                                                                                                    ~
2012-03-13 13:49:35,821 (cli:71): virt-manager startup
2012-03-13 13:49:35,822 (virt-manager:292): Launched as: /usr/pbi/virt-manager-amd64/share/virt-manager/virt-manager.py --debug --connect=qemu+ssh://virthost01
2012-03-13 13:49:35,822 (virt-manager:293): GTK version: (2, 24, 6)
2012-03-13 13:49:35,822 (virt-manager:294): virtManager import: <module 'virtManager' from '/usr/pbi/virt-manager-amd64/share/virt-manager/virtManager/__init__.pyc'>
2012-03-13 13:49:36,132 (keyring:30): gnomekeyring bindings not installed, no keyring support
2012-03-13 13:49:36,488 (engine:555): No inspection thread because libguestfs is too old, not available, or libvirt is not thread safe.
2012-03-13 13:49:36,492 (systray:138): Showing systray: False
2012-03-13 13:49:36,492 (engine:346): About to connect to uris ['qemu+ssh://virthost01']
2012-03-13 13:49:36,659 (manager:171): Showing manager
2012-03-13 13:49:36,696 (engine:471): window counter incremented to 1
2012-03-13 13:49:36,697 (manager:171): Showing manager
2012-03-13 13:49:36,699 (connection:991): Scheduling background open thread for qemu+ssh://virthost01
2012-03-13 13:49:36,701 (connection:1177): Background 'open connection' thread is running
2012-03-13 13:49:36,942 (connection:1227): Background open thread complete, scheduling notify
2012-03-13 13:49:36,985 (connection:1232): Notifying open result
2012-03-13 13:49:36,987 (cli:83): Uncaught exception:
Traceback (most recent call last):
  File "/usr/pbi/virt-manager-amd64/share/virt-manager/virtManager/manager.py", line 665, in _connect_error
    if conn.is_remote() and re.search(r"nc: .* -- 'U'", details):
UnboundLocalError: local variable 'details' referenced before assignment

Traceback (most recent call last):
  File "/usr/pbi/virt-manager-amd64/share/virt-manager/virtManager/manager.py", line 665, in _connect_error
    if conn.is_remote() and re.search(r"nc: .* -- 'U'", details):
UnboundLocalError: local variable 'details' referenced before assignment
2012-03-13 13:49:44,652 (manager:184): Closing manager
2012-03-13 13:49:44,653 (engine:475): window counter decremented to 0
2012-03-13 13:49:44,654 (manager:184): Closing manager
2012-03-13 13:49:44,661 (engine:548): Leaked <vmmConnection object at 0x8133c0cd0 (virtManager+connection+vmmConnection at 0x81177b860)>
2012-03-13 13:49:44,661 (engine:550): Exiting app normally.

[Alvin]

I'm sorry. I completely forgot I posted almost the same question about virt-manager 0.9.0.

The errors are different however, so only this question stands, as it is the latest version. I will now try to install in a Port Jail and see if virt-manager has the same issues there.

[Alvin]

No, not the same issues. It's worse.

The first error is:

exec: /usr/bin/python: not found

Not surprising. python is found in /usr/local/bin/, so I made a symbolic link.

This is the new error

virt-manager --debug --connect=qemu+ssh://virthost01/system
2012-03-15 11:05:15,239 (cli:71): virt-manager startup
2012-03-15 11:05:15,243 (virt-manager:292): Launched as: /usr/local/share/virt-manager/virt-manager.py --debug --connect=qemu+ssh://virthost01/system
2012-03-15 11:05:15,243 (virt-manager:293): GTK version: (2, 24, 6)
2012-03-15 11:05:15,244 (virt-manager:294): virtManager import: <module 'virtManager' from '/usr/local/share/virt-manager/virtManager/__init__.py'>
2012-03-15 11:05:16,021 (keyring:30): gnomekeyring bindings not installed, no keyring support
2012-03-15 11:05:16,044 (virt-manager:390): Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: The given address is empty)
Traceback (most recent call last):
  File "/usr/local/share/virt-manager/virt-manager.py", line 383, in <module>
    main()
  File "/usr/local/share/virt-manager/virt-manager.py", line 315, in main
    config = virtManager.config.vmmConfig(appname, appversion, glade_dir)
  File "/usr/local/share/virt-manager/virtManager/config.py", line 98, in __init__
    self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE)
GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: The given address is empty)
/usr/local/share/virt-manager/virtManager/error.py:41: GtkWarning: shmget failed: error 78 (Function not implemented)
  res = dialog.run()

The PBI looks like a better candidate for a working virt-manager.

[Alvin]

I have it on good authority (the maintainer) that it's not supposed to work yet.