From mboxrd@z Thu Jan  1 00:00:00 1970
From: Glauber Costa <glommer@redhat.com>
Subject: kvm broken with new vmap
Date: Mon, 27 Oct 2008 21:07:28 -0200
Message-ID: <20081027230728.GA30906@poweredge.glommer>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: avi@redhat.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	mtosatti@redhat.com
To: npiggin@suse.de
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:38970 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751153AbYJ0XGH (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 27 Oct 2008 19:06:07 -0400
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.