| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] memory=x & maxmem=y
|
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?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home