From: Chris Friesen <chris.friesen@windriver.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu leaving unix sockets behind after VM is shut down
Date: Tue, 1 Apr 2014 14:34:58 -0600 [thread overview]
Message-ID: <533B22F2.4030209@windriver.com> (raw)
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
next reply other threads:[~2014-04-01 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 20:34 Chris Friesen [this message]
2014-05-06 13:39 ` [Qemu-devel] qemu leaving unix sockets behind after VM is shut down Stefan Hajnoczi
2014-05-06 14:29 ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2014-05-06 14:52 ` [Qemu-devel] " Chris Friesen
2014-05-06 17:25 ` [Qemu-devel] [libvirt] " Eric Blake
2014-05-13 13:24 ` Ján Tomko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=533B22F2.4030209@windriver.com \
--to=chris.friesen@windriver.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).