From: Glauber Costa <glommer@redhat.com>
To: npiggin@suse.de
Cc: avi@redhat.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, mtosatti@redhat.com
Subject: kvm broken with new vmap
Date: Mon, 27 Oct 2008 21:07:28 -0200 [thread overview]
Message-ID: <20081027230728.GA30906@poweredge.glommer> (raw)
Hello Nick,
KVM is currently broken upstream, starting with commit
db64fe02258f1507e13fe5212a989922323685ce (rewrite vmap layer)
The symptoms are some vmallocs from kvm fail.
cat /proc/meminfo shows this at the time of the fail:
VmallocTotal: 122880 kB
VmallocUsed: 15184 kB
VmallocChunk: 83764 kB
so there's plenty of space.
The allocation that fails seem to be 512 bytes long. I'm not
sure it always fails in there, but it seems so.
reply other threads:[~2008-10-27 23:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081027230728.GA30906@poweredge.glommer \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=npiggin@suse.de \
/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