From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: vballoon: page allocation failure. order:0 -> Kernel panic Date: Wed, 25 Feb 2009 11:34:06 +0100 Message-ID: <49A51E9E.20807@wpkg.org> References: <49A3DC82.2030704@wpkg.org> <49A3E7D8.4060108@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:52733 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752597AbZBYKdm (ORCPT ); Wed, 25 Feb 2009 05:33:42 -0500 In-Reply-To: <49A3E7D8.4060108@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity schrieb: > Tomasz Chmielewski wrote: >> I'm trying to use ballooning with kvm-83. >> >> Although I'm able to limit the guest's memory, when I try to increase >> it right after that, I get "vballoon: page allocation failure. >> order:0" followed by a kernel panic. >> >> Is it expected? >> >> The guest is running Debian Lenny with 2.6.26 kernel. It had initially >> 256 MB memory. >> > > It's a guest bug, fixed in 2.6.27 by Indeed it works with 2.6.27. BTW, is it possible to "balloon" to a bigger amount of memory that what was available when the guest started? Or is it only possible to "shrink" and "grow" within initial memory available to the guest, but never "grow" beyond it? For example, if I start a 2.6.27 guest with 256 MB memory on a kvm-83 host, it is not possible to balloon to 300 MB? -- Tomasz Chmielewski http://wpkg.org