that file , but i don´t understand while it is listed
under the openfiles of libvirtd after the vm is started/destroyed???
all the best
max
ursprüngliche Nachricht-
Von: web2 usterman...@web.de
An: Jim Fehlig jfeh...@suse.com , web2 usterman...@web.de
Kopie: Michal
ursprüngliche Nachricht-
Von: Jim Fehlig jfeh...@suse.com
An: web2 usterman...@web.de
Kopie: Michal Privoznik mpriv...@redhat.com , libvirt-users redhat.com
, libvirt-list redhat.com
Datum: Wed, 01 Oct 2014 21:38:05 -0600
Hi Jim,
i use libvirt 1.1.3.5 on fedora core 20, the vm´s i startet are xen-vm´s.
i also take a look on libvirt 1.1.2 on an openSuSE 13.1 und also on libvirt
1.0.2 on an OpenSuSE 12.3 and i didn´t see threads that are created and not
closed . But on the openSuSE-Systems the vm´s are KVM/qemu.
Hello,
sorry for my later answer.
so, after i started libvirtd (no vm´s running) and attach gdb i get the
following threads
(gdb) info thread
Id Target Id Frame
11 Thread 0x7f18fef4e700 (LWP 20695) libvirtd pthread_cond_wait@@GLIBC_2.3.2
() at
Hi
ursprüngliche Nachricht-
Von: Michal Privoznik mpriv...@redhat.com
An: web2 usterman...@web.de , libvirt-users redhat.com
, libvirt-list redhat.com
Datum: Wed, 01 Oct 2014 18:12:45 +0200
-
On 01.10.2014
