Bug 431723 - ssh remote connection errors with "Cannot allocate memory"
ssh remote connection errors with "Cannot allocate memory"
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Daniel Berrange
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2008-02-06 12:33 EST by Cole Robinson
Modified: 2009-12-14 16:16 EST (History)
4 users (show)

See Also:
Fixed In Version: RHBA-2008-0291
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-21 12:48:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fix SSH args checking (744 bytes, patch)
2008-03-19 12:25 EDT, Daniel Berrange
no flags Details | Diff

  None (edit)
Description Cole Robinson 2008-02-06 12:33:26 EST
Description of problem:

Trying to connect to a remote hypervisor from a 5.2 guest fails. Doesn't
need to be a 5.2 remote to trigger.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
virsh connect xen+ssh://remote.host/
Actual results:
libvir: Remote error : Cannot allocate memory
error: Failed to connect to remote hypervisor
Comment 1 Daniel Berrange 2008-02-06 13:05:51 EST
The 2-liner patch is in this thread:

Comment 3 Daniel Berrange 2008-03-19 12:25:59 EDT
Created attachment 298536 [details]
Fix SSH args checking
Comment 4 Daniel Berrange 2008-03-19 12:31:19 EDT
Fix built into libvirt-0.3.3-6.el5
Comment 7 errata-xmlrpc 2008-05-21 12:48:03 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.