similar to: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats

On 01/18/2018 08:25 AM, Ján Tomko wrote: > On Wed, Jan 17, 2018 at 04:45:38PM +0200, Serhii Kharchenko wrote: >> Hello libvirt-users list, >> >> We're catching the same bug since 3.4.0 version (3.3.0 works OK). >> So, we have process that is permanently connected to libvirtd via socket >> and it is collecting stats, listening to events and control the VPSes.

2018-01-17 17:32 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > Sounds like qemuConnectGetAllDomainStats() forgot to unset the job on a > domain. Can you please attach gdb to libvirtd and run 't a a bt' and > share the output? > > Michal > This is output of gdb 't a a bt' ~5 seconds after that error message appeared in log with

On 01/17/2018 03:45 PM, Serhii Kharchenko wrote: > Hello libvirt-users list, > > We're catching the same bug since 3.4.0 version (3.3.0 works OK). > So, we have process that is permanently connected to libvirtd via socket > and it is collecting stats, listening to events and control the VPSes. > > When we try to 'shutdown' a number of VPSes we often catch the

On Wed, Jan 17, 2018 at 04:45:38PM +0200, Serhii Kharchenko wrote: >Hello libvirt-users list, > >We're catching the same bug since 3.4.0 version (3.3.0 works OK). >So, we have process that is permanently connected to libvirtd via socket >and it is collecting stats, listening to events and control the VPSes. > >When we try to 'shutdown' a number of VPSes we often

Ján Tomko wrote 2018-01-18 14:27: > On Thu, Jan 18, 2018 at 11:30:16AM +0700, Artem Likhachev wrote: >> # strace -p 5786 >> read(53, "\0\0\0\34", 4) = 4 >> read(53, "keep\0\0\0\1\0\0\0\2\0\0\0\2\0\0\0\0\0\0\0\0", 24) = 24 >> poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=12, >> events=POLLIN}, {fd=13, events=POLLIN},

libvirtd will lock if for example kill programm which established connection, only sigkill + restart helps., to reproduce: virConnectPtr libvirt_connection = virConnectOpen("qemu:///system"); if(libvirt_connection == NULL) { std::cout<<"failed to connect to qemu:///system\n"; exit(-1); } exit(0);

В письме от Среда, 19-июн-2013 09:35:27 пользователь Michal Privoznik написал: > On 18.06.2013 22:21, Александр wrote: > > В письме от Вторник, 18-июн-2013 12:10:41 пользователь Michal Privoznik > > > > написал: > >> On 18.06.2013 07:14, Александр wrote: > >>> good day, i am trying to create domain via virDomainDefineXML. and my > >>> program

В письме от Вторник, 25-июн-2013 11:47:10 пользователь Michal Privoznik написал: > On 24.06.2013 11:36, Александр wrote: > > libvirtd will lock if for example kill programm which established > > connection,> > > only sigkill + restart helps., to reproduce: > > virConnectPtr libvirt_connection = virConnectOpen("qemu:///system"); > >

On 20.06.2013 12:56, Alexandr wrote: > On 20.06.2013 10:44, Michal Privoznik wrote: >> On 20.06.2013 09:40, Александр wrote: >>> В письме от Четверг, 20-июн-2013 09:15:14 Вы написали: >>>> On 19.06.2013 21:24, Александр wrote: >>>>> В письме от Среда, 19-июн-2013 09:35:27 пользователь Michal Privoznik >>> написал: >>>>>> On

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

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

I'm trying the following command on the source machine: virsh migrate --live --copy-storage-all --verbose TEST qemu+ssh:// 10.30.76.66/system If I ssh into the destination machine when this command is running, I can see NBD copying data as expected, and if I wait long enough it completes and succeeds. However if I ctrl+c this command above before it completes, it causes virsh commands

i did the debugging as you said. Kindly refer the following logs: (gdb) c Continuing. thread apply all bt [New Thread 0x7fc337c6b700 (LWP 29520)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) thread apply all bt Thread 12 (Thread 0x7fc337c6b700 (LWP 29520)): #0 0x00007fc33509f18d in read () from /lib/x86_64-linux-gnu/libpthread.so.0 #1

Hello everybody! We have a cluster of servers managed by VMmanager 5 KVM (by ispsystem). A typical node: # cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) # uname -r 3.10.0-693.11.6.el7.x86_64 # rpm -qa |grep libvirt libvirt-daemon-driver-qemu-3.7.0-1.el7.centos.x86_64 libvirt-daemon-driver-storage-disk-3.7.0-1.el7.centos.x86_64 libvirt-3.7.0-1.el7.centos.x86_64

I have tried to define a domain or using virt-install both failed. Could some one give me the correct command to do this? I used: virt-install --nographics --paravirt --os-type=solaris --os-variant=opensolaris --ram 1024 --name cam-host --disk path=/dev/dsk/c0t600A0B800049E902000008EB4A9CE744d0p0,driver=phy -l /export/media_images/sol-nv-b121-x86-dvd.iso thx, florian

Hi,I am having an issue on several KVM hosts which run CentOs7 and libvirt-daemon-1.2.17-13.el7_2.3.x86_64 .About once a week the libvirtd hangs forever and becomes unresponsive, the only help is to restart it. I attached gdb to it and the output of it can be seen at the end of the mail. Laine from the irc channel suggests it has to do with dbus/policykit. If anybody got an idea what it could be

Hello, I installed libvirt from package manager(debian apt) and want to modify feture in it, so i git clone from https://libvirt.org/git/?p=libvirt.git;a=summary But now i have trouble to start virsh. I have traced the email: https://www.redhat.com/archives/libvirt-users/2017-February/msg00074.html Here is output of command below: strace -o libvirt.log -f -s 1000 /usr/sbin/libvirtd

В письме от Воскресенье, 30-июн-2013 03:41:37 пользователь Александр написал: > В письме от Вторник, 25-июн-2013 11:47:10 пользователь Michal Privoznik > > написал: > > On 24.06.2013 11:36, Александр wrote: > > > libvirtd will lock if for example kill programm which established > > > connection,> > > > > > > only sigkill + restart helps., to

On 20.06.2013 10:44, Michal Privoznik wrote: > On 20.06.2013 09:40, Александр wrote: >> В письме от Четверг, 20-июн-2013 09:15:14 Вы написали: >>> On 19.06.2013 21:24, Александр wrote: >>>> В письме от Среда, 19-июн-2013 09:35:27 пользователь Michal Privoznik >> написал: >>>>> On 18.06.2013 22:21, Александр wrote: >>>>>> В письме

Hi Michal, thank you for your answer. so if i understand that correctly, no matter if i shutdown or destroy the domain and no matter if it is a transient or an persistent vm, the thread should disappear, right? in my case they still exist, also an hour after i destroy the domain (and don´t start any new one). i use libvirt-1.1.35 on fedora core 20, for information. all the best max