Bug 428743
Summary: | Can't connect to remote virt-manager | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Espen Stefansen <libbe> | ||||||
Component: | libvirt | Assignee: | Daniel Berrangé <berrange> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 8 | CC: | hbrock | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | 0.4.0-4.fc8 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2008-01-22 15:53:29 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Espen Stefansen
2008-01-14 21:27:18 UTC
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. |