search for: remote_dispatch

...2e0000f80, domains=0x7f931f813af0, flags=48) at ../../../src/libvirt-domain.c:6491 #4 0x0000559f219f6dca in remoteDispatchConnectListAllDomains (server=0x559f23795530, msg=0x559f237b78c0, ret=0x7f92d0000920, args=0x7f92d0000ad0, rerr=0x7f931f813bc0, client=<optimized out>) at ../../../daemon/remote_dispatch.h:1244 #5 remoteDispatchConnectListAllDomainsHelper (server=0x559f23795530, client=<optimized out>, msg=0x559f237b78c0, rerr=0x7f931f813bc0, args=0x7f92d0000ad0, ret=0x7f92d0000920) at ../../../daemon/remote_dispatch.h:1220 #6 0x00007f932eb5c5b9 in virNetServerProgramDispatchCall (msg=0x559...

...0f80, domains=0x7f931f813af0, flags=48) at ../../../src/libvirt-domain.c:6491 > #4 0x0000559f219f6dca in remoteDispatchConnectListAllDomains (server=0x559f23795530, msg=0x559f237b78c0, ret=0x7f92d0000920, args=0x7f92d0000ad0, rerr=0x7f931f813bc0, client=<optimized out>) at ../../../daemon/remote_dispatch.h:1244 > #5 remoteDispatchConnectListAllDomainsHelper (server=0x559f23795530, client=<optimized out>, msg=0x559f237b78c0, rerr=0x7f931f813bc0, args=0x7f92d0000ad0, ret=0x7f92d0000920) at ../../../daemon/remote_dispatch.h:1220 > #6 0x00007f932eb5c5b9 in virNetServerProgramDispatchCall...

...t;hdc\" bus=\"sata\" tr"..., flags=0) > at libvirt-domain.c:8338 > #5 0x000056177c3e3c3e in remoteDispatchDomainUpdateDeviceFlags (server=0x56177ca8ba60, > msg=0x56177ca98210, args=0x7f49e8002e10, rerr=0x7f4a069cbc90, > client=<optimized out>) 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 virNetServerProgramDispa...

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

...__func__ = "virDomainGetInfo" __FUNCTION__ = "virDomainGetInfo" #7 0x0000000000439bca in remoteDispatchDomainGetInfo (ret=0x7f6998000c20, args=<optimized out>, rerr=0x7f69c5782c50, client=0x157e730, server=<optimized out>, msg=<optimized out>) at remote_dispatch.h:1640 rv = -1 tmp = {state = 1 '\001', maxMem = 2097152, memory = 0, nrVirtCpu = 0, cpuTime = 5981880000000} dom = 0x7f69980e3650 priv = <optimized out> #8 remoteDispatchDomainGetInfoHelper (server=<optimized out>, client=0x157e730, msg=<opti...

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)

...-47a5-875d-be5d6b28af2c</uuid>\n <memory>1048576</"..., flags=0) at libvirt-domain.c:180 #10 0x00007f195b6e8dfa in remoteDispatchDomainCreateXML (server=0x7f195bc4eb40, msg=0x7f195bc73ee0, ret=0x7f19240038b0, args=0x7f1924003a70, 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=0x7f195bc71...

...ver.c:1507 #13 0x00007fc33723cd37 in virDomainDestroy (domain=domain@entry=0x7fc3380e3770) at libvirt.c:2342 #14 0x00007fc337cb9ba4 in remoteDispatchDomainDestroy (args=<optimized out>, rerr=0x7fc32f67bcd0, client=0x7fc32400ee60, server=<optimized out>, msg=<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=0x7f...

...quot; />\n <mac address=\"00:27:0e:0c:01:09\" />\n </interface>") at libvirt-domain.c:8351 #18 0x00007f793be11a1f in remoteDispatchDomainAttachDevice (server=0x7f793c2e0a90, client=0x7f793c2f34c0, msg=0x7f793c2feca0, rerr=0x7f792a92bab0, 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=0x7f793c...

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

...<optimized out>         __func__ = "virDomainCreate"         __FUNCTION__ = "virDomainCreate" #8  0x00005557f0d53ea3 in remoteDispatchDomainCreate (server=0x5557f23853d0, msg=0x5557f23936a0, args=<optimized out>,     rerr=0x7f0d525aac90, client=0x5557f238fac0) at remote_dispatch.h:4222         dom = 0x7f0d4009b1c0         priv = <optimized out> ---Type <return> to continue, or q <return> to quit--- #9  remoteDispatchDomainCreateHelper (server=0x5557f23853d0, client=0x5557f238fac0, msg=0x5557f23936a0, rerr=0x7f0d525aac90,     args=<optimized out>...

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

...n=0x7fd358000c30, from=0x7fd35c0014a0 "/root/hive2/src/domU.state", dxml=0x0, flags=0) at libvirt.c:2975 #15 0x00007fd39b5011f6 in remoteDispatchDomainRestoreFlags (server=<optimized out>, msg=<optimized out>, args=0x7fd35c01a430, rerr=0x7fd38a444c80, 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=0x7fd39c93...