hi,
there is something, what i don''t understand.
I have in my DomU config:
memory = "128"
maxmem = "1024"
tsles:~ # cat /proc/xen/balloon
Current allocation: 237568 kB
Requested target: 237568 kB
Minimum target: 237568 kB
Maximum target: 1048576 kB
Low-mem balloon: 804352 kB
High-mem balloon: 0 kB
Driver pages: 1024 kB
Xen hard limit: ??? kB
I can set the memory up to 1024M, but if i set the memory to 64M, than i
won''t remove the memory in the guest, but xm list shows:
tsles 6 64 1 -b---- 24.2
--long output:
(maxmem 1024)
(memory 64)
(shadow_memory 0)
so, what is the reason?
cu denny
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Denny Schierz wrote:>I can set the memory up to 1024M, but if i set the memory to 64M, than i >won''t remove the memory in the guest, but xm list shows: > >tsles 6 64 1 -b---- 24.2 > > > --long output: > > >(maxmem 1024) >(memory 64) >(shadow_memory 0)I believe the way the balloon driver works is simply to ''lock out'' the DomU from accessing memory - it can''t change the amount of ''physical'' memory the client thinks it has available. So when you balloon down, the memory becomes free to the Dom0, but from the DomU, it just looks like it''s there but in use. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi, Am Dienstag, den 25.11.2008, 13:54 +0000 schrieb Simon Hobson:> ''physical'' memory the client thinks it has available. So when you > balloon down, the memory becomes free to the Dom0, but from the DomU, > it just looks like it''s there but in use.so that means, that the DomU can''t use more than 64M ram of the system? I assumed, that he (Dom_U) trys to swap out, if he doesn''t have enough physical ram. cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Denny Schierz wrote:> > ''physical'' memory the client thinks it has available. So when you >> balloon down, the memory becomes free to the Dom0, but from the DomU, >> it just looks like it''s there but in use. > > >so that means, that the DomU can''t use more than 64M ram of the system? >I assumed, that he (Dom_U) trys to swap out, if he doesn''t have enough >physical ram.Yes, if you balloon down to 64M, then the guest will only play in 64M of real memory - and will swap/whatever in order to keep going. I gather that it''s not quite the same as starting it with only 64M as some things (like kernel buffers) are sized at boot time according to the available memory. So starting with 1024M and ballooning down to 64M is likely to result in slight differences to starting with 64M in the first place. I''m not expert though ! -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users