search for: virinitialize

...your case you don't have any registered when >>> calling it. >>> >>> Michal >> >> thank you very match, it now working as expected, but one thing are >> missed from documentations, current api docs says what i do not need >> to >> call virInitialize(), but if i call virEventRegisterDefaultImpl() >> without calling virInitialize() programm crashing (i have not used >> virInitialize() in my programm, just virConnectOpen() as docs said). >> problem solved now. > > From virInitialize documentation [1]: > > "The...

Hi, I have a host with 6 VMs set to autostart. When this host reboots, it starts libvirtd, pegasus cimom and libvirt-cim. It also restarts the VMs. Intermittently we noticed a core during start up that points to the last call made by libvirt-cim to "virInitialize". I am thinking that it is a timing issue where virInitialize is called while libvirt is trying to autostart the VMs. Is this a known issue? Thanks, Sharad Mishra -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvir...

...ctOpen detects if there's an even loop > registered. And in your case you don't have any registered when calling > it. > > Michal thank you very match, it now working as expected, but one thing are missed from documentations, current api docs says what i do not need to call virInitialize(), but if i call virEventRegisterDefaultImpl() without calling virInitialize() programm crashing (i have not used virInitialize() in my programm, just virConnectOpen() as docs said). problem solved now.

...n't have any registered when >>>> calling it. >>>> >>>> Michal >>> >>> thank you very match, it now working as expected, but one thing are >>> missed from documentations, current api docs says what i do not need to >>> call virInitialize(), but if i call virEventRegisterDefaultImpl() >>> without calling virInitialize() programm crashing (i have not used >>> virInitialize() in my programm, just virConnectOpen() as docs said). >>> problem solved now. >> >> From virInitialize documentation [1]: &...

...even loop >> registered. And in your case you don't have any registered when >> calling it. >> >> Michal > > thank you very match, it now working as expected, but one thing are > missed from documentations, current api docs says what i do not need to > call virInitialize(), but if i call virEventRegisterDefaultImpl() > without calling virInitialize() programm crashing (i have not used > virInitialize() in my programm, just virConnectOpen() as docs said). > problem solved now. >From virInitialize documentation [1]: "The only time it would be neces...

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 { if(virEventRunDefaultImpl() < 0) { virErrorPtr err = virGetLastError(); fprintf(stderr, "Failed to run event loop: %s\n", err && err->message ? err->message : "Unknown

I'm using the Ruby/FFI libvirt library and getting this consistently on Mac OS X: ruby-1.9.2-p0 > FFI::Libvirt.virInitialize dyld: lazy symbol binding failed: Symbol not found: _virThreadInitialize Referenced from: /usr/local/lib/libvirt.dylib Expected in: flat namespace dyld: Symbol not found: _virThreadInitialize Referenced from: /usr/local/lib/libvirt.dylib Expected in: flat namespace Trace/BPT trap I expor...

...nformation. I would appreciate your help. export LIBVIRT_DEBUG=1 [eucalyptus at hp-a ~]$ virsh list 21:48:08.342: 5830: info : libvirt version: 0.9.4, package: 23.el6_2.4 (CentOS BuildSystem <http://bugs.centos.org>, 2012-01-17-10:52:29, c6b18n1.dev.centos.org) 21:48:08.342: 5830: debug : virInitialize:415 : register drivers 21:48:08.342: 5830: debug : virRegisterDriver:770 : driver=0x3848dc5c40 name=Test 21:48:08.342: 5830: debug : virRegisterDriver:794 : registering Test as driver 0 21:48:08.342: 5830: debug : virRegisterNetworkDriver:587 : registering Test as network driver 0 21:48:08.342: 583...

...irt/libvirt.h> void* loop(void *arg) { while (1) { assert (virEventRunDefaultImpl() >= 0); } return NULL; } void callback(virConnectPtr conn, virDomainPtr dom, void *opaque) { // Do nothing. } void freecb(void *opaque) { // Do nothing. } int main() { assert(virInitialize() >= 0); assert(virEventRegisterDefaultImpl() >= 0); pthread_t event_loop; assert(pthread_create(&event_loop, NULL, loop, NULL) == 0); virConnectPtr conn = virConnectOpen("test:///default"); assert(conn != NULL); int cbid = virConnectDomainEventRegiste...

libvirt version: 3.4.0 architecture: x86_64 ubuntu16.04-server hypervisor: kvm,qemu My program use libvirt event , the program is a module(.so) file in cloud application, when unload the module, program will dump in virEventPoolRunOnce call. program frame virInitialize virEventAddTimeOut virEventRunDefaultImpl virConnectXXX virConnectDomainEventRegisterAny ... virConnectDomainEventDeregisterAny ... when unload the module will dump , the gdb bt commad output is [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-g...

HI, all My daemon exists a libvirt API call: virEventRegisterDefaultImpl(); once I called the virEventRegisterDefaultImpl() ,must be core ,the bt stack is: (gdb) bt #0 free (ptr=0x1) at include/jemalloc/internal/arena.h:652 #1 0x00007f57690a488a in virFree () from /lib64/libvirt.so.0 #2 0x00007f57690c3562 in virResetError () from /lib64/libvirt.so.0 #3 0x00007f57690c49ad in

...irt-users/2011-August/msg00069.html Here is the gist of his investigation - I've looked into the libvirt source code and the reason for issues with the unload of libvirt-cim providers is there (and cimprovider -r forces an unload, just as cimserver shutdown does). virConnectOpen() does call virInitialize() which then will initialize the gcrypt library after initializes the thread setup ->virThreadInitialize(), creates the error reporting structure ->virErrorInitialize() and initialize a random number generator ->virRandomInitialize(). The issue is hidden in virErrorInitialize(). It calls...

...path (Cole Robinson) - qemudDomainMigrateFinish2: handle a case of virDomainSaveStatus failure (Jim Meyering) - Fix potential NULL dereference in remoteDomainMigratePrepare2 (Jiri Denemark) - qemudDomainRestore: handle a case of virDomainSaveStatus failure (Jim Meyering) - python: don't ignore virInitialize failure in module initialization (Jim Meyering) - tests: do not ignore virInitialize failure (Jim Meyering) - qemuMonitorTextMigrate: avoid leak on OOM-error path (Jim Meyering) - virNWFilterDefParseXML: avoid leak on error paths (Jim Meyering) - virDomainNetDefParseXML: avoid leak upon multiple &q...

...ibvirt.ErrorHandler.processError(ErrorHandler.java:28) at org.libvirt.Connect.<init>(Connect.java:195) at VBOX.main(VBOX.java:32) Otherwise, from virsh, I can correctly connect to the vbox hypervisor: $ export LIBVIRT_DEBUG=1 $virsh -c vbox:///session list --all 11:37:18.318: debug : virInitialize:336 : register drivers 11:37:18.318: debug : virRegisterDriver:837 : registering Test as driver 0 11:37:18.318: debug : virRegisterNetworkDriver:675 : registering Test as network driver 0 11:37:18.318: debug : virRegisterInterfaceDriver:706 : registering Test as interface driver 0 11:37:18.318: deb...

...stdlib.h> -#include <string.h> -#include <unistd.h> -#include <errno.h> - -#include <libvirt/libvirt.h> - -#include "guestfs.h" -#include "guestfs-internal-frontend.h" - -int -main (int argc, char *argv[]) -{ - unsigned long ver; - guestfs_h *g; - - virInitialize (); - - /* Check that the version of libvirt we are linked against - * supports the new test-driver auth feature. - */ - virGetVersion (&ver, NULL, NULL); - if (ver < 1002001) { - fprintf (stderr, "%s: test skipped because libvirt is too old (%lu)\n", - argv[0...

...bin:/usr/bin:/sbin:/bin:/usr/games HOME=/home/heath USER=heath LOGNAME=heath /usr/local/sbin/libvirtd --timeout=30', just like it appears virsh is trying to do. I get a return code of 1 with the following output: 22:29:33.295: 8389: info : libvirt version: 0.9.3 22:29:33.295: 8389: debug : virInitialize:412 : register drivers 22:29:33.295: 8389: debug : virRegisterDriver:767 : driver=0x3745e0 name=Test 22:29:33.295: 8389: debug : virRegisterDriver:791 : registering Test as driver 0 22:29:33.295: 8389: debug : virRegisterNetworkDriver:584 : registering Test as network driver 0 22:29:33.295: 8389...

...> >> I executed the commands "export LIBVIRT_DEBUG=1" and "virsh dominfo 2" >> (ID 2 was a running domU), this is the output: >> >> ----------------------------------------------------------------------------------------- >> DEBUG: libvirt.c: virInitialize (register drivers) >> DEBUG: xen_internal.c: xenHypervisorInit (Using new hypervisor call: 30002 >> ) >> DEBUG: xen_internal.c: xenHypervisorInit (Using hypervisor call v2, sys >> ver6 dom ver5 >> ) >> DEBUG: libvirt.c: virConnectOpenAuth (name=(null), auth=0xb7...

...PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games HOME=/home/heath USER=heath LOGNAME=heath /usr/local/sbin/libvirtd --timeout=30". I got a return code of 1 with the following output: 22:29:33.295: 8389: info : libvirt version: 0.9.3 22:29:33.295: 8389: debug : virInitialize:412 : register drivers 22:29:33.295: 8389: debug : virRegisterDriver:767 : driver=0x3745e0 name=Test 22:29:33.295: 8389: debug : virRegisterDriver:791 : registering Test as driver 0 22:29:33.295: 8389: debug : virRegisterNetworkDriver:584 : registering Test as network driver 0 22:29:33.295: 8389...

...te ( virDomainPinVcpu ( virDomainRef( virDomainSetMaxMemory ( virDomainSetMemory ( virDomainSetSchedulerParameters ( virDomainSetVcpus ( virDomainStatsRecordListFree ( virEventAddTimeout( virEventRegisterDefaultImpl ( virEventRemoveTimeout( virEventRunDefaultImpl ( virGetLastError ( virGetVersion ( virInitialize ( virNetworkFree ( virNodeGetCellsFreeMemory ( virNodeGetFreeMemory ( virNodeGetInfo ( virResetLastError ( virSecretDefineXML ( virSecretFree ( virSecretGetUUIDString ( virSecretGetValue ( virSecretLookupByUsage ( virSecretLookupByUUIDString ( virSecretSetValue ( virSetErrorFunc ( virStoragePoolFre...

Hi, test-qemu-drive-libvirt.sh fails to run with libvirt < 1.1.3, because the <test:runstate> attribute (used to keep the domains shut off) has been introduced in that libvirt version. Create a small (uninstalled) C tool which just does this version check, to be used in all the tests (just one, so far) written in shell/scripting language. Pino Toscano (2): tests: add a a simple