Re: [libvirt] [Question] capabilities.pidfile is left behind while starting and stopping libvirtd repeatly

On Tue, Sep 30, 2014 at 04:47:14PM +0200, Martin Kletzander wrote: > On Tue, Sep 30, 2014 at 05:34:54PM +0800, Wang Yufei wrote: > >Hi, all > > > >I started and stopped libvirtd service repeatly with high frequency(1 per second), and found that the file capabilities.pidfile is left behind, as well as a qemu process. If I then restart libvirtd, qemu-kvm will fail to start as it's unable to flock capabilities.pidfile's fd. > > > > Have you tried current master? Or at least -rc2? It should already > be fixed there: > > commit 9e159b521dbf18c6da6976e54e29c8553f831eb6 > Author: Guido Günther <agx(a)sigxcpu.org&gt; > Date: Thu Sep 25 10:30:58 2014 +0200 > > qemu: remove capabilities.monitor.sock when done > This one removes the monitor socket, not the pidfile since I didn't see that one lingering around in my tests. Cheers,