Bug 760436 - virsh connect fails with remote machine which has different libvirt version
Summary: virsh connect fails with remote machine which has different libvirt version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-06 08:01 UTC by Min Zhan
Modified: 2012-06-20 06:37 UTC (History)
8 users (show)

Fixed In Version: libvirt-0.9.9-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 06:37:51 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0748 0 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2012-06-19 19:31:38 UTC

Comment 3 Jiri Denemark 2011-12-06 08:47:41 UTC
This is already fixed upstream by v0.9.8-rc2-4-g8fcee13:

commit 8fcee135e816a59bea96768feb15e6f32db328ef
Author: Guido Günther <agx>
Date:   Sun Dec 4 15:26:23 2011 +0100

    remote_driver: don't fail if keepalive check fails
    
    Otherwise connections to older libvirt abort with:
    
    $ virsh -c qemu+ssh://host.example.com/system list
    error: invalid connection pointer in virDrvSupportsFeature
    error: failed to connect to the hypervisor
    
    Tested against 0.8.3 and 0.9.8-rc2.

Comment 4 Daniel Veillard 2011-12-06 08:49:18 UTC
Confirmed, that commit fixes it for me too !

Daniel

Comment 5 zhpeng 2011-12-13 08:35:22 UTC
I tested with libvirt-0.9.8-1.el6.x86_64 and passed.

Comment 7 Huang Wenlong 2012-01-10 02:37:08 UTC
Verify this bug with 
libvirt-0.9.9-1.el6.x86_64

Client : libvirt-0.9.9-1.el6.x86_64

Host: libvirt-0.9.4-23.el6_2.4.x86_64

Client :

## virsh -c qemu+ssh://10.66.85.216/system list 
The authenticity of host '10.66.85.216 (10.66.85.216)' can't be established.
RSA key fingerprint is 89:75:2b:2e:61:75:2c:dc:c3:8f:67:52:9f:b4:7f:67.
Are you sure you want to continue connecting (yes/no)? yes
root.85.216's password: 
 Id Name                 State
----------------------------------
  3 mig                  running

Comment 9 errata-xmlrpc 2012-06-20 06:37:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0748.html


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