Description of problem: I am attempting to use virsh/libvirt/phyp to connect to one of our hmc's. Connection is accepting password but then hangs, when I press enter or type list and enter it says: error: no valid connection error: this function is not supported by the connection driver: virConnectSetKeepAlive Segmentation fault: 11 Version-Release number of selected component (if applicable):1.2.4RC2 How reproducible:Everytime I try to connect to any HMC with any user. Steps to Reproduce: 1. virsh -c phyp://[user]@[hmc]/[managed system] 2. enter password 3. hangs 4. press enter or "list" then enter 5. seg faults Actual results: error: no valid connection error: this function is not supported by the connection driver: virConnectSetKeepAlive Segmentation fault: 11 Expected results: opens connection and allows me to list Additional info:
Created attachment 891206 [details] Config log from libvirt build Here is my build log from ./configure on the libvirt
Created attachment 891207 [details] connection log from phyp attempts Here is the log from my connection attempts using phyp
I tried it using another managed system (the first one was in standby) here are the results of that: 2014-04-30 15:30:06.963+0000: 18446744073709551615: info : libvirt version: 1.2.4 2014-04-30 15:30:06.963+0000: 18446744073709551615: warning : phypUUIDTable_ReadFile:627 : Unable to read from information from local file. error: failed to connect to the hypervisor error: An error occurred, but the cause is unknown
Heres what's happening on the HMC: Apr 30 11:36:50 hmcXXXXXXX sshd[5669]: user *myusername* is type LDAP_USER Apr 30 11:36:50 hmcXXXXXXX sshd[5669]: pam_unix_session(sshd:session): session opened for user *myusername* by (uid=0) Apr 30 11:36:50 hmcXXXXXXX sshd[5669]: pam_hsc open session. Apr 30 11:39:19 hmcXXXXXXX sshd[5669]: pam_unix_session(sshd:session): session closed for user *myusername* I left virsh hanging for that time period, it wasn't until I hit enter is when it closed the connection and gave my the UUID error.
Sorry this never received a response. Unfortunately the phyp driver is not materially maintained upstream these days, so unless someone provides a patch I doubt this will be fixed. Closing as DEFERRED since this bug isn't going to accomplish much