From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42981) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WV5Oq-0004oz-Mq for qemu-devel@nongnu.org; Tue, 01 Apr 2014 16:35:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WV5Oh-0001Me-59 for qemu-devel@nongnu.org; Tue, 01 Apr 2014 16:35:12 -0400 Received: from mail1.windriver.com ([147.11.146.13]:50464) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WV5Og-0001HR-T8 for qemu-devel@nongnu.org; Tue, 01 Apr 2014 16:35:03 -0400 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.5) with ESMTP id s31KYxCC007929 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 1 Apr 2014 13:35:00 -0700 (PDT) Message-ID: <533B22F2.4030209@windriver.com> Date: Tue, 1 Apr 2014 14:34:58 -0600 From: Chris Friesen MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qemu leaving unix sockets behind after VM is shut down List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org When running qemu with something like this -device virtio-serial \ -chardev socket,path=/tmp/foo,server,nowait,id=foo \ -device virtserialport,chardev=foo,name=host.port.0 the VM starts up as expected and creates a socket at /tmp/foo as expected. However, when I shut down the VM the socket at /tmp/foo is left behind in the filesystem. Basically qemu has "leaked" a file. With something like OpenStack where we could be creating/destroying many VMs this could end up creating a significant number of files in the specified directory. Has any thought been given to either automatically cleaning up the unix socket in the filesystem when qemu exits, or else supporting the abstract namespace for unix sockets to allow for automatic cleanup? Chris