similar to: segfault while unloading libvirt provider.

Displaying 20 results from an estimated 900 matches similar to: "segfault while unloading libvirt provider."

2011 Aug 11
2
virInitialize dumps core intermittently.
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.
2010 Sep 16
1
virConnectOpen question.
Hi, I am using virConnectOpen(const char *uri) to connect to the local hypervisor. When uri is set to "lxc:///", an error gets logged in /var/log/messages about failed connection. But I do not see any error for "xen:///". The machine does not have these drivers installed, and I am using libvirt 0.6.3. My questions are - 1. Why I see error in /var/log/messages for container
2012 Jun 14
0
can not connect hypervisor using libvirt-0.9.11 on windows
Hi,ALL: I compiled the libvirt-0.9.11 source code with mingw on windows according to the website: https://github.com/photron/msys_setup Then I wrote a simple test case ,as below: #include <stdio.h> #include <stdlib.h> #include "libvirt/libvirt.h" int main(int argc,char **argv) { virConnectPtr conn; conn =
2016 Jul 24
2
Lifecycle of a connection to libvirtd
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() -
2016 Jul 25
0
Re: Lifecycle of a connection to libvirtd
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:
2011 Aug 22
0
issue with virErrorInitialize
One of my team mate investigated the issue where libvirt-cim was segfaulting when unloading providers. More info on this issue is at https://www.redhat.com/archives/libvirt-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
2011 Aug 16
1
Detecting the last user of a connection has closed.
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
2011 Dec 13
1
Thread-safety issues with vbox driver ?
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;
2010 Aug 27
1
Unable to autostart storage pool.
Following xml file was used to create storage pool using 'virsh pool-create <xml>' <pool type='dir'> <name>my-diskpool</name> <uuid>2fbc894e-7619-6cda-a33c-b27fae5fbe8b</uuid> <capacity>136024670208</capacity> <allocation>11416657920</allocation> <available>124608012288</available> <source>
2012 Jun 14
1
question regarding CMPIObjectPath
Folks, I'm a new user and I'm trying to build a standalone application using libvirt-cim (rather than use a full-fledged CIMOM). I need some help. While calling the CMPIInstanceMI->ft->enumerateInstances, I need to pass a reference to CMPIObjectPath. My application is crashing because I don't know what is the correct constructor for this. If I do ref = CMPIObjectPath () then
2016 Aug 03
0
Crash after connection close when callback is in progress
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
2008 Aug 23
3
Postfix and Dovecot SASL authentication error
ear All, I configured Postfix 2.3.3-2 on CentOS 5.2 using SASL Dovecot authentication put I am facing the problem to receive mails . My postconf -n result is: [root at mails ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2
2020 Jan 10
2
Re: [PATCH Fedora libguestfs] Don't depend on libvirt-daemon-kvm monolith.
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
2007 Oct 31
3
virt-install fails in b75a
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
2010 Jul 01
0
non-root user "virConnectOpen() faile" in libvirt-0.3
*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
2017 Sep 08
2
[PATCH] RFC: v2v: add and use libvirt connection objects
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)
2013 Oct 14
2
Re: event handler
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
2013 Oct 14
0
Re: event handler
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:
2013 Oct 14
0
Re: event handler
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
2013 Oct 14
2
Re: event handler
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 >> { >>