[libvirt] increase number of libvirt threads by starting tansient guest doamin - is it a bug?

[Jim Fehlig]

ustermann78 at web.de wrote:
> hello,
>
> if i start a transient guest doamin via "virsh create abcd.xml" i see an additional libvirt thread and also some open files:
>
> pstree -h `pgrep libvirtd`
> libvirtd───11*[{libvirtd}]
>
> libvirtd 3016 root   21w      REG              253,0      6044 1052094 /var/log/libvirt/libxl/abcd.log
> libvirtd 3016 root   22r     FIFO                0,8       0t0  126124 pipe
> libvirtd 3016 root   23w     FIFO                0,8       0t0  126124 pipe
> libvirtd 3016 root   24u      REG               0,37         0       4 /proc/xen/privcmd
> libvirtd 3016 root   25u     unix 0xffff8807d2c3ad80       0t0  126125 socket
> libvirtd 3016 root   26r     FIFO                0,8       0t0  126127 pipe
> libvirtd 3016 root   27w     FIFO                0,8       0t0  126127 pipe
> libvirtd 3016 root   28r     FIFO                0,8       0t0  124783 pipe
> libvirtd 3016 root   29w     FIFO                0,8       0t0  124783 pipe
> libvirtd 3016 root   30r     FIFO                0,8       0t0  127140 pipe
> libvirtd 3016 root   31w     FIFO                0,8       0t0  127140 pipe
>
> if i destroy these vm via "virsh destroy abcd", i see that the additional thread still exists and also the list of openfiles is the same.
>   

I don't see this behavior with current libvirt git master

# pstree `pgrep libvirtd`
libvirtd───10*[{libvirtd}]
# virsh create ./test.xml
Domain test created from ./test.xml
# pstree `pgrep libvirtd`
libvirtd───11*[{libvirtd}]
# virsh destroy test
Domain test destroyed
# pstree `pgrep libvirtd`
libvirtd───10*[{libvirtd}]

All file descriptors opened when the domain was created were closed as well.

What version of libvirt are you using?

Regards,
Jim