search for: virconnectref

Unknown sefault: http://itmag.es/2HxqM Why this might happen? Maybe i'm close last virConnectRef in threads? (but this is unlikely). Or maybe another reason? -- Fl@sh

On 11.04.2015 11:29, Fl@sh wrote: > Unknown sefault: > http://itmag.es/2HxqM > > Why this might happen? > Maybe i'm close last virConnectRef in threads? (but this is > unlikely). Or maybe another reason? > Doesn't ring any bell to me. What were you doing when the crash occurred? Do you have a small reproducer? Also - what's the libvirt version (maybe the bug was already fixed upstream so upgrading may help). Michal

On Mon, 13 Apr 2015 07:03:37 +0200 Michal Privoznik <mprivozn@redhat.com> wrote: > On 11.04.2015 11:29, Fl@sh wrote: > > Unknown sefault: > > http://itmag.es/2HxqM > > > > Why this might happen? > > Maybe i'm close last virConnectRef in threads? (but this is > > unlikely). Or maybe another reason? > > > > Doesn't ring any bell to me. What were you doing when the crash > occurred? Do you have a small reproducer? Also - what's the libvirt > version (maybe the bug was already fixed upstream so upg...

...llDomainStats ( 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( vir...

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

...llback == NULL) \ + callback = caml_named_value(NAME); \ + if (callback == NULL) \ + abort(); /* C code out of sync with OCaml code */ \ + if ((virDomainRef(dom) == -1) || (virConnectRef(conn) == -1)) \ + abort(); /* should never happen in practice? */ \ + \ + Begin_roots4(connv, domv, callback_id, result); \ + connv = Val_connect(conn); \ + domv =...

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