similar to: can not connect hypervisor using libvirt-0.9.11 on windows

I have a CIM provider that just calls virConnectOpen("qemu:///system"); and virConnectClose(). When cimom unloads this provider segfaults - #0 0x000000305b420cd0 in ?? () (gdb) bt #0 0x000000305b420cd0 in ?? () #1 0x00000031a3e05ad9 in __nptl_deallocate_tsd () from /lib64/libpthread.so.0 #2 0x00000031a3e0674b in start_thread () from /lib64/libpthread.so.0 #3 0x00000031a32d3d1d in

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() -

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:

The documentation says something that concerns me: http://libvirt.org/html/libvirt-libvirt.html#virConnectClose "It is possible for the last virConnectClose<http://libvirt.org/html/libvirt-libvirt.html#virConnectClose>to return a positive value if some other object still has a temporary reference to the connection, but the application should not try to further use

Hi, I'm experiencing weird things with the vbox driver when using multiple threads. Following is the snippet of code I experience problems with /*****************************************************/ #include <stdlib.h> #include <stdio.h> #include <pthread.h> #include <libvirt/libvirt.h> void *create_and_destroy(void *arg) { virDomainPtr dom = (virDomainPtr)arg;

Hey! It seems that if I close a connection while a domain event callback is in progress, I can easily have a crash. Here is a backtrace: #v+ #0 virFree (ptrptr=0x0) at ../../../src/util/viralloc.c:582 save_errno = <optimized out> #1 0x00007fc8328a4ad2 in virObjectEventCallbackListPurgeMarked (cbList=0xadfc30) at ../../../src/conf/object_event.c:282 freecb = <optimized

Hi, I need some help in building a Java client on Windows 7 64 bit plaftorm to manage a KVM using the libvirt APIs. Using the instructions at http://libvirt.org/java.html, i was able to build libvirt.jar. My understanding is that libvirt.jar uses JNA to call libvirt's native windows library. I tried using the libvirt dlls in the experimental Windows installation package mentioned in

Hello, i am interested in developing against the libvirt library. But we would also need an actively developed version for Windows. The links I found on the website for Windows related builds are all pretty outdated and do not really work for me. * https://github.com/SPICE/virt-viewer Last commit 2 years ago * https://github.com/photron/msys_setup Last commit 5 years ago So before

On Thu, Feb 01, 2018 at 01:19:03PM +0000, Robin Stegk wrote: > Hello, > > i am interested in developing against the libvirt library. But we would > also need an actively developed version for Windows. > The links I found on the website for Windows related builds are all > pretty outdated and do not really work for me. > > * https://github.com/SPICE/virt-viewer Last

Hi, Does the libvirt support the bios delay ? I mean that after set a special number of seconds or minutes, when the domain starts, the bios will delay after the time I set Thanks for your time wade xuteng via foxmail -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Fri, Jan 10, 2020 at 02:15:10PM +0000, Daniel P. Berrangé wrote: > Do you use the libvirt "secret" APIs at all (disk encryption, network > disk auth passwords) ? If so you will need "libvirt-daemon-driver-secret" > too. How about any other libvirt sub-driver APIs ? Networking ? Host > dev, etc ? The full list of APIs we use is attached, assuming I got my

Hi? All: I have two physical machines as KVM hosts (clusterA.RHCS and clusterB.RHCS) , an iscsi target set into GFS. All I want is a HA Cluster which could migrate all the virtual machines on a node to another when the first node failed into some error status. So I created a cluster "cluster" using RHCS ,added the two hosts into the cluster . created a fence device . for every virtual

After an "exaustive" search on what may be causing this, I still can''t figure it out. I keep getting this same error when trying to run virt-install: # virt-install Traceback (most recent call last): File "/usr/bin/virt-install", line 666, in ? main() File "/usr/bin/virt-install", line 518, in main conn = libvirt.open(options.connect) File

*Hello,* * * *My environment is "Xen3.1 in Fedora8" with "libvirt0.3 & python2.5". When I ran the following * *commands as a non-root user "nimbus":* $python >>> import libvirt >>> libvirt.open("xen:///") --------- Console --------- [nimbus at localhost-120 ~]$ python Python 2.5.1 (r251:54863, Oct 30 2007, 13:54:11) [GCC 4.1.2

Enhance the Libvirt_utils module with libvirt connection objects, and read-only and read-writen open functions for them; adapt the rest of the mini-binding to use these objects, instead of opening + closing libvirt connections every time. This has different improvements: a) a libvirt connection is reused for different API calls, improving the communication with remote (input) servers b)

Michal Privoznik писал 2013-10-14 11:39: > On 14.10.2013 10:33, Alexandr wrote: >> Michal Privoznik писал 2013-10-14 08:48: >>> On 14.10.2013 02:42, Alexandr wrote: >>>> good day to all. >>>> i still have not solved my problem with event handling. >>>> currently i have following code >>>> >>>> >>>> void

On 14.10.2013 10:33, Alexandr wrote: > Michal Privoznik писал 2013-10-14 08:48: >> On 14.10.2013 02:42, Alexandr wrote: >>> good day to all. >>> i still have not solved my problem with event handling. >>> currently i have following code >>> >>> >>> void libvirt_eventloop_thr_func() >>> { >>> while(true) //TODO:

On 14.10.2013 10:57, Alexandr wrote: > Michal Privoznik писал 2013-10-14 11:39: >> On 14.10.2013 10:33, Alexandr wrote: >>> Michal Privoznik писал 2013-10-14 08:48: >>>> On 14.10.2013 02:42, Alexandr wrote: >>>>> good day to all. >>>>> i still have not solved my problem with event handling. >>>>> currently i have following

Michal Privoznik писал 2013-10-14 08:48: > On 14.10.2013 02:42, Alexandr wrote: >> good day to all. >> i still have not solved my problem with event handling. >> currently i have following code >> >> >> void libvirt_eventloop_thr_func() >> { >> while(true) //TODO: stop somehow on exit >> { >>

Currently virt-v2v has few custom C-based functions for libvirt operations, which are limited in what they do, and there is a lot of duplicated code. Instead, switch to ocaml-libvirt for all the libvirt interaction currently done by the Libvirt_utils module. This has few advantages: - each input & output module now opens a libvirt connection only once, only when needed - no need to pass