search for: virconnectisalive

Hi In my program , When libvirtd restart , the old libvirtd connection(virConnectPtr) has to reconnect, Before usr old virConnectPtr , I call virConnectIsAlive. but when I restart libvirtd , virConnectIsAlive return 1, and I continue other operate use the old virConnectPtr, program will receive signal pipe. I use libvirt event. before any api use, I call virEventRegisterDefaultImpl, and run virEventRunDefaultImpl. then use virConnectIsAlive, when I re...

Hi Michal, virConnectOpen is for connecting to a host right..? I want to check the host status, whether the connection to the host is active or not.. for that purpose we have to use virConnectIsAlive() I'm using libvirt python bindings, here is the function defnintion. def isAlive(self): """Determine if the connection to the hypervisor is still alive A connection will be classed as alive if it is either local, or running over a channel (TCP or U...

...- Application logic And in the registered callback, I would: - virConnectUnregisterCloseCallback() - virConnectClose() - virConnectOpen() - virConnectRegisterCloseCallback() - virConnectSetKeepAlive() However, looking at the source code of virsh, I see that it additional stuff, notably: - virConnectIsAlive() - checking error codes of all calls to check if they are the result of a disconnect Are those steps needed? Randomly checking virConnectIsAlive() doesn't seem reliable. Checking individual error codes either (maybe I will miss one of them or misinterpret another one). virsh code uses th...

Hi, Using libvirt how can we check the status of a remote/local host machine.. isAlive() method is giving true even if the internet connection is broken OR libvirt demon in the remote machine is being stopped. so isAlive() does not seems to be handy, Is there some other way to get the status of remote host..? Thanks -Sijo

...allback, I would: > > - virConnectUnregisterCloseCallback() > - virConnectClose() > - virConnectOpen() > - virConnectRegisterCloseCallback() > - virConnectSetKeepAlive() > >However, looking at the source code of virsh, I see that it additional >stuff, notably: > > - virConnectIsAlive() > - checking error codes of all calls to check if they are the result of > a disconnect > >Are those steps needed? Randomly checking virConnectIsAlive() doesn't >seem reliable. Checking individual error codes either (maybe I will miss >one of them or misinterpret another o...

Hi, What's the best way to tell if a virConnect object is not good to use anymore? (For example because the libvirtd on the other side crashed/has been stopped or because of some network failure) When I try this, the first API call I do on a broken connection yields an error with error number 38 (VIR_ERR_SYSTEM_ERROR) and all subsequent calls yield an error number 1

...iver 0 Test returned DECLINED debug : do_open:1332 : nwfilter driver 1 ESX returned DECLINED debug : do_open:1332 : nwfilter driver 2 remote returned SUCCESS debug : virConnectRegisterCloseCallback:21344 : conn=0x2aad62a1e10 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a1e10 debug : virConnectIsAlive:21292 : conn=0x2aad62a1e10 debug : virDomainLookupByName:2242 : conn=0x2aad62a1e10, name=vm1 debug : virNetMessageNew:44 : msg=0x2aad62a2ce0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 36 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad...