similar to: "virsh" list

Hi Daniel, sorry. Here the requested stack trace. Best regards Holger ===================================================================================== Thread 18 (Thread 0x7f0d495e0700 (LWP 10742)): #0  0x00007f0d55e690bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 No symbol table info available. #1  0x00007f0d5892176a in virCondWait (c=c@entry=0x5557f238db28,

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

On Thu, Jan 18, 2018 at 11:30:16AM +0700, Artem Likhachev wrote: >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

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},

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 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

On 04/04/2018 02:59 PM, Vincent Bernat wrote: > ❦ 4 avril 2018 11:17 +0200, Michal Privoznik <mprivozn@redhat.com> : > >> Dunno, this is the first time I hear about this issue. Maybe you can 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

❦ 4 avril 2018 11:17 +0200, Michal Privoznik <mprivozn@redhat.com> : > Dunno, this is the first time I hear about this issue. Maybe you can 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

On 11/15/2017 06:54 AM, Holger Schranz wrote: > Thread 1 (Thread 0x7f4a069cc700 (LWP 10178)): > #0 0x00007f49ff969170 in qemuDomainChangeEjectableMedia ( > driver=driver@entry=0x7f49f841b700, vm=vm@entry=0x7f49ec02fbd0, > disk=disk@entry=0x7f49ec0375d0, newsrc=0x7f49e8014d10, force=force@entry=false) > at qemu/qemu_hotplug.c:303 This is fixed in current upstream by

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

Hi, first sorry for the cross-posting, but i don ́t known exactly if my problem belongs to xen or libvirt. I have an VM-Host with Xen 4.6.0 und libvirt 1.2.19. The Job of the Host is to resume in parallel 20 VM ́s (HVM WinXp) attach a block-device to each VM , wait 60 Seconds, kill the VM and start from beginning. For that, a python script create for each vm a thread and each thread get a

В письме от Воскресенье, 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: >>>>>> В письме

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

В письме от Вторник, 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"); > >

В письме от Четверг, 20-июн-2013 13:25:06 пользователь Michal Privoznik написал: > 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: > >>>>> В письме

On Thu, Apr 20, 2017 at 06:10:04PM +0200, Rafał Wojciechowski wrote: > 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 The attached core send in private mail helped to figure out where the crash happened. Backtrace: Thread 1 (Thread 0x7f194b99d700 (LWP 5631)):

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

Description of problem: libvirt 3.9 on CentOS Linux release 7.4.1708 (kernel 3.10.0-693.21.1.el7.x86_64) on Qemu version 2.10.0 I’m currently facing a strange situation. Sometimes my vm is shown by ‘virsh list’ as in state “in shutdown” but there is no qemu-kvm process linked to it. Libvirt log when “in shutdown” state occur is as follows: “d470c3b284425b9bacb34d3b5f3845fe” is vm’s name,

Hi, all, We were running OpenStack with Ubuntu and libvirt 0.9.10. We found that libvirt monitor command not working well. There were a lot of error in libvirtd.log like this 2013-02-07 06:07:39.000+0000: 18112: error : qemuDomainObjBeginJobInternal:773 : Timed out during operation: cannot acquire state change lock We dig into libvirtd by strace and find one of the thread only have the following