WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] Disallow setting maxmem to higher value than tot

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Disallow setting maxmem to higher value than total physical memory size
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 01 Sep 2010 09:53:55 -0700
Cc: Michal Novotny <minovotn@xxxxxxxxxx>, "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 01 Sep 2010 09:54:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1283345049.12544.9494.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C7E47B2.9010805@xxxxxxxxxx> <1283345049.12544.9494.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100806 Fedora/3.1.2-1.fc13 Lightning/1.0b2pre Thunderbird/3.1.2
 On 09/01/2010 05:44 AM, Ian Campbell wrote:
> On Wed, 2010-09-01 at 13:31 +0100, Michal Novotny wrote:
>> Hi,
>> this is the patch to disallow changing the maxmem value to higher value 
>> than total physical memory size since without this patch I was able to 
>> set dom0 maxmem to higher (invalid) value which is not correct.
> I think it is allowable for a domU though. Consider the scenario where
> you have two hosts, one of which has more physical RAM than the other.
> You may which to boot a domain on the smaller host, (i.e. booting
> ballooned with a current_pages suitable for the small host) and then
> migrate it to the large machine where you then want to be able to
> balloon to a value larger than was even possible on the previous
> machine.

But max-mem can change between hosts; on the small host it needn't have
a maxmem larger than the host's memory.  (The domain itself may have a
larger notion of maxmem internally, but that's separate.)

    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>