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-users

Re: [Xen-users] memory=x & maxmem=y

After doing some more research, I finally found out what's going on. In order to allocate more memory to a domU, it has to be freed from somewhere else first. In other words, if memory=256 and maxmem=512, then before you run 'xm mem-set mydomU 512', you have to run 'xm mem-set 0 <current memory for dom0 - 256>'. I suppose this would work just as well by taking the memory from another domU (or some combination of domU's and dom0), but I haven't tried that.

I haven't played with VCPU's, but it probably works on the same principle.

Paul


Tomorrow, suyash jape wrote:

  Hi everyone , I have also been facing the same problem for the past few
days. The max-mem parameter in the domU  config file is completely
ignored.Even if we specifiy maxmem parameter in the config file at boot time
, boot time allocated memory is taken as the max memory possible for the
domain.
         Also i observed that the max vcpu parameter also behaves the same
way.
VCPU Observations:
 1]We can play around with only the no of VCPUs allotted at boot time or
less.

Allocating max no of VCPUs  dynamically is not reflected. i.e we can make
max VCPUs of a domain from 5 to 10 dynamically BUT the 5 new ones are never
used...they are always paused (possibly a bug in open source xen ?)

Is there a fix around these problems?

Thanks.....

Suyash



Paul Archer <tigger@xxxxxx> wrote:

> I have been playing with memory= and maxmem=, but I'm not seeing what
> I think I should be seeing, namely that the memory available to a
> domU can be increased on the fly.
>
>


Brad wrote :
>I wasn't able to achieve this using xen-3.1. The maximum amount of RAM
appears to be dictated by the value that >the machine is booted with. Has
anyone else managed to increase the amount of memory allocated to a domU to
>more than what the domU was booted with and have the domU utilise this
memory? I.e. show up with free -m on the >domU?




--------Brady's First Law of Problem Solving:-------
When confronted by a difficult problem, you can
solve it more easily by reducing it to the question,
"How would the Lone Ranger have handled this?"
----------------------------------------------------

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