search for: virnetserverprogram

...n try > to set a break point on virHashIterationError() and when it's hit get > stacktrace of all threads 't a a bt'. That might shed more light into > the issue. Smells like we are not locking somewhere properly. So, we have two threads iterating. Both of them originates from virNetServerProgramDispatchCall. So, it seems there is a lock missing? Thread 10 (Thread 0x7f931f814700 (LWP 126453)): #0 virHashForEach (table=0x7f92fc69a480, iter=iter@entry=0x7f932ea8fbf0 <virDomainObjListCollectIterator>, data=data@entry=0x7f931f813a20) at ../../../src/util/virhash.c:597 #1 0x00007f932ea9...

...ak point on virHashIterationError() and when it's hit get >> stacktrace of all threads 't a a bt'. That might shed more light into >> the issue. Smells like we are not locking somewhere properly. > > So, we have two threads iterating. Both of them originates from > virNetServerProgramDispatchCall. So, it seems there is a lock missing? No. As suspected, both threads are reading internal list of domains (actually hash table). They are not modifying the list so they grab a read lock. > > Thread 10 (Thread 0x7f931f814700 (LWP 126453)): > #0 virHashForEach (table=0x7f92f...

...>) at remote_dispatch.h:12339 > #6 remoteDispatchDomainUpdateDeviceFlagsHelper (server=0x56177ca8ba60, > client=<optimized out>, msg=0x56177ca98210, rerr=0x7f4a069cbc90, > args=0x7f49e8002e10, ret=0x7f49e8004770) at remote_dispatch.h:12315 > #7 0x00007f4a0ce49a02 in virNetServerProgramDispatchCall (msg=0x56177ca98210, > client=0x56177ca99b80, server=0x56177ca8ba60, prog=0x56177ca986f0) > at rpc/virnetserverprogram.c:437 > #8 virNetServerProgramDispatch (prog=0x56177ca986f0, > server=server@entry=0x56177ca8ba60, client=0x56177ca99b80, msg=0x56177ca98210)...

Hey! On many of our servers, we often have the following error: error : virHashForEach:597 : Hash operation not allowed during iteration When querying the list of domains, this means libvirt will silently return 0 domain (most uses of virHashForEach don't handle the return code). We are using a hook, but the hook doesn't query libvirt back, so it should be safe from this point of view.

hello, I attached core dump - not sure if it was what you have asked for I am rather just admin not developer :) Regards, Rafal Wojciechowski W dniu 20.04.2017 o 16:44, Pavel Hrdina pisze: > On Thu, Apr 20, 2017 at 07:36:42AM +0200, Rafał Wojciechowski wrote: >> hello, >> >> I am getting such error: >> libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp

...remoteDispatchDomainGetInfoHelper (server=<optimized out>, client=0x157e730, msg=<optimized out>, rerr=0x7f69c5782c50, args=<optimized out>, ret=0x7f6998000c20) at remote_dispatch.h:1616 __func__ = "remoteDispatchDomainGetInfoHelper" #9 0x00007f69c9fbb915 in virNetServerProgramDispatchCall (msg=0x1689cc0, client=0x157e730, server=0x1577c90, prog=0x15825d0) at rpc/virnetserverprogram.c:416 ret = 0x7f6998000c20 "" rv = -1 i = <optimized out> arg = 0x7f6998027950 "\360e\n\230i\177" dispatcher = 0x73de40...

On Tue, Nov 14, 2017 at 07:19:01PM +0100, Holger Schranz wrote: > Ups ... my fault ... > > libvirtd instead libvirt .... > > > etcsvms5:/var/lib/systemd/coredump # coredumpctl info libvirtd >            PID: 10177 (libvirtd) >            UID: 0 (root) >            GID: 0 (root) >         Signal: 11 (SEGV) >      Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago)

...4003a70, rerr=0x7f194b99cc50, client=0x7f195bc71e90) at remote_dispatch.h:4257 #11 remoteDispatchDomainCreateXMLHelper (server=0x7f195bc4eb40, client=0x7f195bc71e90, msg=0x7f195bc73ee0, rerr=0x7f194b99cc50, args=0x7f1924003a70, ret=0x7f19240038b0) at remote_dispatch.h:4235 #12 0x00007f195aaea002 in virNetServerProgramDispatchCall (msg=0x7f195bc73ee0, client=0x7f195bc71e90, server=0x7f195bc4eb40, prog=0x7f195bc62fa0) at rpc/virnetserverprogram.c:437 #13 virNetServerProgramDispatch (prog=0x7f195bc62fa0, server=server@entry=0x7f195bc4eb40, client=0x7f195bc71e90, msg=0x7f195bc73ee0) at rpc/virnetserverprogram.c:307...

...optimized out>) at remote_dispatch.h:3165 #15 remoteDispatchDomainDestroyHelper (server=<optimized out>, client=0x7fc32400ee60, msg=<optimized out>, rerr=0x7fc32f67bcd0, args=<optimized out>, ret=<optimized out>) at remote_dispatch.h:3143 #16 0x00007fc3372b4d79 in virNetServerProgramDispatchCall (msg=0x7fc324014070, client=0x7fc32400ee60, server=0x7fc3380dbba0, prog=0x7fc324007750) at rpc/virnetserverprogram.c:435 #17 virNetServerProgramDispatch (prog=0x7fc324007750, server=server@entry=0x7fc3380dbba0, client=0x7fc32400ee60, msg=0x7fc324014070) at rpc/virnetserverprogram.c:...

...2bab0, args=0x7f791c009190) at remote_dispatch.h:2850 #19 0x00007f793be11923 in remoteDispatchDomainAttachDeviceHelper (server=0x7f793c2e0a90, client=0x7f793c2f34c0, msg=0x7f793c2feca0, rerr=0x7f792a92bab0, args=0x7f791c009190, ret=0x7f791c009130) at remote_dispatch.h:2826 #20 0x00007f793b1fccfc in virNetServerProgramDispatchCall (prog=0x7f793c2eefd0, server=0x7f793c2e0a90, client=0x7f793c2f34c0, msg=0x7f793c2feca0) at rpc/virnetserverprogram.c:437 #21 0x00007f793b1fc863 in virNetServerProgramDispatch (prog=0x7f793c2eefd0, server=0x7f793c2e0a90, client=0x7f793c2f34c0, msg=0x7f793c2feca0) at rpc/virnetserverprogr...

I am newbie to this gdb debugging. now i did the bt in the debugging. In my side still it showing the error. Following are the stacktrace which i got. Kindly refer the following logs for full information: **** [New Thread 0x7f8503695700 (LWP 20012)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00007f84f671281e in

...ainCreateHelper (server=0x5557f23853d0, client=0x5557f238fac0, msg=0x5557f23936a0, rerr=0x7f0d525aac90,     args=<optimized out>, ret=0x7f0d403683c0) at remote_dispatch.h:4198         rv = -231146816         __func__ = "remoteDispatchDomainCreateHelper" #10 0x00007f0d58a60ed2 in virNetServerProgramDispatchCall (msg=0x5557f23936a0, client=0x5557f238fac0, server=0x5557f23853d0,     prog=0x5557f2391a70) at rpc/virnetserverprogram.c:437         ret = 0x7f0d403683c0 ""         rv = -1         i = <optimized out>         identity = 0x7f0d400166e0         arg = 0x7f0d4033eaa0...

Hello, In the .xml file I use a media which is no longer available. In the past, I got the information media not available and the creation of the VM was stopped - O.k. behavior. Since 3.10 the libvirtd stopped promptly and all open consoles windows and the virt-manager closed promptly. For diagnose: etcsvms1:/kvm/CS8200/M5 # coredumpctl TIME PID UID GID SIG

Hi, I'm having problems with libvirt crashing after a couple hours when a specific domain monitoring program is running. I have pasted below the following: 1. libvirt version 2. qemu-kvm version 3. OS version 4. Kernel version 5. libvirt status post-crash 6. libvirtd.log (info level dump around crash; too long to post everything so just the beginning and end. UTC) 7. custom.log (on what

...4c80, client=0x7fd39c93bfd0) at remote_dispatch.h:6663 #16 remoteDispatchDomainRestoreFlagsHelper (server=<optimized out>, client=0x7fd39c93bfd0, msg=<optimized out>, rerr=0x7fd38a444c80, args=0x7fd35c01a430, ret=<optimized out>) at remote_dispatch.h:6642 #17 0x00007fd39ab24e4a in virNetServerProgramDispatchCall (msg=0x7fd39c93a560, client=0x7fd39c93bfd0, server=0x7fd39c91dc80, prog=0x7fd39c933440) at rpc/virnetserverprogram.c:435 #18 virNetServerProgramDispatch (prog=0x7fd39c933440, server=server@entry=0x7fd39c91dc80, client=0x7fd39c93bfd0, msg=0x7fd39c93a560) at rpc/virnetserverprogram.c:305...