LKML Archive on
help / color / mirror / Atom feed
From: Glauber Costa <>
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:

* 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 \ \ \ \ \ \ \
    --subject='Re: kvm broken with new vmap' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).