From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: vballoon: page allocation failure. order:0 -> Kernel panic Date: Wed, 25 Feb 2009 12:37:17 +0200 Message-ID: <49A51F5D.6040800@redhat.com> References: <49A3DC82.2030704@wpkg.org> <49A3E7D8.4060108@redhat.com> <49A51E9E.20807@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Tomasz Chmielewski Return-path: Received: from mx2.redhat.com ([66.187.237.31]:33987 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758793AbZBYKhU (ORCPT ); Wed, 25 Feb 2009 05:37:20 -0500 In-Reply-To: <49A51E9E.20807@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski wrote: > > BTW, is it possible to "balloon" to a bigger amount of memory that > what was available when the guest started? No. The guest won't have its data structures set up to handle the extra memory. > > Or is it only possible to "shrink" and "grow" within initial memory > available to the guest, but never "grow" beyond it? > Right. One workaround is to start the guest with more memory than you need and immediately balloon it down. Hopefully we'll have memory hotplug one day so it can be fixed properly. -- error compiling committee.c: too many arguments to function