From: "Andreas Färber" <afaerber@suse.de>
To: Christoffer Dall <cdall@cs.columbia.edu>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] pthread_create failed: Resource temporarily unavailable
Date: Thu, 03 Jan 2013 12:50:33 +0100 [thread overview]
Message-ID: <50E57089.7080805@suse.de> (raw)
In-Reply-To: <CAEDV+g+pShbxgj3pnj9D-2xeG+HVw-zA9cMnXHXsLoeAbQYGeQ@mail.gmail.com>
Hi,
Am 02.01.2013 20:17, schrieb Christoffer Dall:
> I am seeing some brutal crashes with QEMU running virtio using KVM/ARM.
>
> The culprit seems to be when the process runs out of virtual address
> space on 32-bit systems due to some subsystem (virtio?) creating a
> large number of pthreads under heavy workloads.
>
> Unfortunately my QEMU expertise is too limited to pin-point the exact
> fix, nor do I have resources right now to go into it, but I wanted to
> raise this issue and spread general awareness.
>
> Is this a known issue or something that needs to be tracked/documented at least?
It is a known issue that I reported long ago, but there have been higher
priorities. ;)
Note that this failure is not specifically about creating threads but
about thread creation being one of several operations requiring some
free virtual mem, it might as well be a malloc another run. If you trace
memory usage of the process you will likely see dramatic changes over
time... why exactly is still to be investigated.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-01-03 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 19:17 [Qemu-devel] pthread_create failed: Resource temporarily unavailable Christoffer Dall
2013-01-03 0:45 ` [Qemu-devel] [kvmarm] " Adrian Taylor
2013-01-03 0:50 ` Peter Maydell
2013-01-03 8:46 ` [Qemu-devel] " Stefan Hajnoczi
2013-01-03 11:50 ` Andreas Färber [this message]
2013-01-03 18:53 ` Christoffer Dall
2013-01-04 9:50 ` Stefan Hajnoczi
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=50E57089.7080805@suse.de \
--to=afaerber@suse.de \
--cc=cdall@cs.columbia.edu \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).