Description of problem: Everytime I try to connect to a remote virt-manager, I get an error. I followed the intructions from here: http://virt-manager.org/page/RemoteSSH All services are restarted but i still get this error from virt-manager.log: [ma., 14 jan. 2008 21:56:37 virt-manager 7750] DEBUG (connection:292) Scheduling background open thread for qemu+ssh://root.0.8/system [ma., 14 jan. 2008 21:56:37 virt-manager 7750] DEBUG (connection:299) Background thread is running [ma., 14 jan. 2008 21:56:37 virt-manager 7750] ERROR (connection:324) Unable to open connection to hypervisor URI 'qemu+ssh://root.0.8/system': <class 'libvirt.libvirtError'> virConnectOpenReadOnly() failed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 306, in _open_thread self.vmm = libvirt.openReadOnly(self.uri) File "/usr/lib/python2.5/site-packages/libvirt.py", line 144, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: virConnectOpenReadOnly() failed [ma., 14 jan. 2008 21:56:37 virt-manager 7750] DEBUG (connection:328) Background open thread complete, scheduling notify [ma., 14 jan. 2008 21:56:37 virt-manager 7750] DEBUG (connection:337) Notifying open result Version-Release number of selected component (if applicable): libvirt-0.4.0-2.fc8 virt-manager-0.5.3-1.fc8 How reproducible: Everytime Steps to Reproduce: 1. 2. 3. Actual results: Get an error and no connection Expected results: Should be able to connect to remote virt-manager Additional info:
Do you have the 'nc' RPM installed on the server, and is the 'libvirtd' service running ?
Yep. nc-1.84-13.fc8 is installed at both computers and libvirtd is running.
From a 'gnome-terminal' window, you able to run ssh root.0.8 And get a login shell, without being prompted for any kind of password/passphrase/etc ? What does running 'virsh --connect qemu+ssh://root.0.8/system' show ?
I can connect without being asked for any password. When i run the virsh-command, i get: libvir: Remote error : Can't allocate memory error: failed to connect to the hypervisor
That is bizarre. Please run the following strace -s 10000 -f -o virsh.txt virsh --connect qemu+ssh://root.0.8/system And attach the resulting 'virsh.txt' trace file.
Created attachment 291657 [details] Output of the strace
Created attachment 291658 [details] Fix off-by-one in SSH argv processing
Please try these test libvirt RPMs, on the client host where you run virsh/virt-manager. Either x86_64: http://koji.fedoraproject.org/koji/taskinfo?taskID=348812 Or i686: http://koji.fedoraproject.org/koji/taskinfo?taskID=348813 They ought to fix the problem you see.
You da man! :) Those rpm's made it work. Thank you very much!
Today the was an update of libvirt in yum (libvirt-0.4.0-3.fc8.i386.rpm) so I updated my other computer, which ran libvirtd yesterday. I the tried connecting the opposite way (the client yesterday, the server today), but that didn't work. I got the same error as yesterday. But when i updated libvirt from the koji-links above, everything worked. Aren't libvirt-0.4.0-3.fc8.i386.rpm and libvirt-0.4.0-3.fc8.1dan.i386.rpm from koji above, supposed to be the same?
libvirt-0.4.0-4.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.