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

>>> On 01.09.10 at 16:50, Michal Novotny <minovotn@xxxxxxxxxx> wrote:
> On 09/01/2010 04:26 PM, Jan Beulich wrote:
>>>>> On 01.09.10 at 16:18, Michal Novotny<minovotn@xxxxxxxxxx>  wrote:
>>>>>          
>>> Oh, ok. It's not limited to dom0 nevertheless I don't see anything to be
>>>      
>> And how does this play together with physical memory hotplug?
>>
>> Jan
>>
>>    
> Well, it's reading the physical memory size using the xc.physinfo() call 
> so if this is handled correctly by hypervisor (since this  basically 
> issues a hypercall) then it should be working fine.

Meaning the tools would auto-adjust maxmem_kb' for Dom0 when
new memory got added? I can't see where that happens.

Jan


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

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