From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkChC-0008IZ-RW for qemu-devel@nongnu.org; Tue, 13 May 2014 09:24:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WkCh5-0000xm-TL for qemu-devel@nongnu.org; Tue, 13 May 2014 09:24:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:19540) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkCh5-0000xS-N2 for qemu-devel@nongnu.org; Tue, 13 May 2014 09:24:31 -0400 Message-ID: <53721D04.2090803@redhat.com> Date: Tue, 13 May 2014 15:24:20 +0200 From: =?ISO-8859-1?Q?J=E1n_Tomko?= MIME-Version: 1.0 References: <533B22F2.4030209@windriver.com> <20140506133957.GX15810@stefanha-thinkpad.redhat.com> In-Reply-To: <20140506133957.GX15810@stefanha-thinkpad.redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2i0oE5DVEPIap9mbACdG5n5gVC6hGpncl" Subject: Re: [Qemu-devel] [libvirt] qemu leaving unix sockets behind after VM is shut down List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi , Chris Friesen Cc: libvir-list@redhat.com, qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2i0oE5DVEPIap9mbACdG5n5gVC6hGpncl Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 05/06/2014 03:39 PM, Stefan Hajnoczi wrote: > On Tue, Apr 01, 2014 at 02:34:58PM -0600, Chris Friesen wrote: >> When running qemu with something like this >> >> -device virtio-serial \ >> -chardev socket,path=3D/tmp/foo,server,nowait,id=3Dfoo \ >> -device virtserialport,chardev=3Dfoo,name=3Dhost.port.0 >> >> the VM starts up as expected and creates a socket at /tmp/foo as expec= ted. >> >> 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? I have sent a libvirt patch to clean up the sockets on qemu shutdown: https://www.redhat.com/archives/libvir-list/2014-May/msg00398.html Jan >=20 > Libvirt has a special case for the monitor socket in its > qemuProcessStop() function. >=20 > Are you using the OpenStack libvirt driver? >=20 > Perhaps QEMU should support cleanup but first I think we should check > the situation with libvirt. >=20 > Stefan >=20 > -- > libvir-list mailing list > libvir-list@redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list >=20 --2i0oE5DVEPIap9mbACdG5n5gVC6hGpncl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTch0KAAoJEMr6XT10/wJpqjQP/3I9FXUh6SIhno7PQ+RvleDs RyFyziM6bzBHKHM9R5aUBw/2/FU11C2NO21ASnkwjACe6bxFl1or8srXEHDVO6Os K1nOfAkmHTctrtxLoUBbVgDQNqSDB7rAdqnHOwhNqHPDzAoj2xNiAa8wJYJUWTg+ HgDcMPMIoGNzI9AOGRiB6POuUpjzeXTGA4bTBmlksc/37q5dmiSUBpc/+gy/+rma o5lkIyGn0V0VIHJqYJNJluqaO8bCcf9VYZeeKIK+OgnKZpj0BXy4Kt8gvFKsvQcu o15FImmfNLC6cLctHTnRUxEbvHTrQ/mwRAPrlfYbXqHR2biuL/OfztyXf/h0Ap6A aJ7aJudDWZYORoo+Pf6Lk7XK0QeRA+fJvbjByMsQWlgWO+xGhwkORTIpD0OrBoUo f+3nWQ2XmcB7b87i4DCq5EkgTwmvXLf5k7pL8p94EFgTDuD+HVC/QR8T9XoPkOa0 Yw6KURIgtmTDvsuDrwXUbXEX6vj2YXX7BJDljlfFUUsv9WdRvHw0iHeBpy9XfWtP r+D2e+74dXLjJ1Ho2PQ8PIdDBuxn0N+rK1OOlT6AWLs0y+cIVs08Otp3pkCnAWC2 er0LrNEBTKb+3ocl/LacBcF7qu9peBifdUFHSbEjGmTVhB6E/dzdxNtkaEKvlVuR pBzEMf1aAsNbeLWNS3hq =23SZ -----END PGP SIGNATURE----- --2i0oE5DVEPIap9mbACdG5n5gVC6hGpncl--