search for: virconnectsetkeepalive

Can anyone explain what is happening. After call virConnectOpen virEventRegisterDefaultImpl() call virConnectSetKeepAlive returns VirtError(1): internal error: the caller doesn't support keepalive protocol; perhaps it's missing event loop implementation, but the next call this sequence of commands returns success. Why virConnectSetKeepAlive not work right the first time? -- Fl at sh

Hey! I am trying to figure out how to reliably maintain a connection to libvirtd. From the documentation, I would expect something like that: - virConnectOpen() - virConnectRegisterCloseCallback() - virConnectSetKeepAlive() - 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:...

On Sun, Jul 24, 2016 at 11:13:08PM +0200, Vincent Bernat wrote: >Hey! > >I am trying to figure out how to reliably maintain a connection to >libvirtd. From the documentation, I would expect something like that: > > - virConnectOpen() > - virConnectRegisterCloseCallback() > - virConnectSetKeepAlive() > - Application logic > >And in the registered callback, I would: > > - virConnectUnregisterCloseCallback() > - virConnectClose() > - virConnectOpen() > - virConnectRegisterCloseCallback() > - virConnectSetKeepAlive() > >However, looking at the source code of virs...

At Tue, 1 Apr 2014 17:29:25 +0400, Fl@sh wrote: > > Can anyone explain what is happening. > After call > virConnectOpen > virEventRegisterDefaultImpl() > call virConnectSetKeepAlive returns > VirtError(1): internal error: the caller doesn't > support keepalive protocol; perhaps it's missing > event loop implementation, > but the next call this sequence of commands returns success. > Why virConnectSetKeepAlive not work right the first time? AFAIK, you...

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

...virConnectGetCapabilities ( virConnectGetDomainCapabilities ( virConnectGetMaxVcpus ( virConnectGetVersion ( virConnectListDefinedDomains ( virConnectListDomains ( virConnectNumOfDefinedDomains ( virConnectNumOfDomains ( virConnectOpen ( virConnectOpenAuth ( virConnectOpenReadOnly ( virConnectRef( virConnectSetKeepAlive( virConnResetLastError ( virConnSetErrorFunc ( virDomainAttachDeviceFlags ( virDomainBlockPeek ( virDomainBlockStats ( virDomainCreateXML ( virDomainDestroy ( virDomainDestroyFlags ( virDomainDetachDeviceFlags ( virDomainFree ( virDomainGetConnect ( virDomainGetCPUStats( virDomainGetID ( virDomainG...

libguestfs usually needs qemu. However it only requires an emulator for the same architecture, not for all architectures. libvirt-daemon-kvm pulls in qemu which pulls in emulators for all architectures, as well as a bunch of other stuff we don't need at all like network interface support and nwfilter. There are no Fedora TCG-only arches, so drop the conditional section. I also made support

...im value +ocaml_libvirt_connect_set_keep_alive(value connv, + value intervalv, value countv) +{ + CAMLparam3 (connv, intervalv, countv); + virConnectPtr conn = Connect_val(connv); + int interval = Int_val(intervalv); + unsigned int count = Int_val(countv); + int r; + + NONBLOCKING(r = virConnectSetKeepAlive(conn, interval, count)); + CHECK_ERROR (r == -1, "virConnectSetKeepAlive"); + + CAMLreturn(Val_unit); +} + +CAMLprim value +ocaml_libvirt_connect_credtypes_from_auth_default (value unitv) +{ + CAMLparam1 (unitv); + CAMLlocal2 (listv, itemv); + int i; + + listv = Val_emptylist; + +...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all