On 7/15/05, aq <aquynh@xxxxxxxxx> wrote:
> On 7/15/05, aq <aquynh@xxxxxxxxx> wrote:
> > On 7/14/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote:
> > > <snip>
> > >
> > > > When I had a closer look to the mem line:
> > > > Mem: 257488K total, 255368K used, 2120K free, 128K buffers
> > > >
> > > > ...it looked strange to me. I checked and found my config file for this
> > > > domain looking like this:
> > > >
> > > > ...
> > > > memory = 128
> > > > extra = "mem=268435456"
> > > > ...
> > >
> > > Well spotted!
> > >
> > > > This was left over from my tries to get the "xm balloon" working. I
> > > > removed the extra line from the config file - and voila, it works... Is
> > > > this config above wrong at all or is the strange behaviour I found
> > > > related to the bugs with balloon feature..?
> > >
> > > The config line looks OK at first glance but... I wonder what units the
> > > mem
> > > parameter expects: if it expects KB then you've just caused it to
> > > allocate a
> > > frame table for an absolutely *huge* physical memory, which would account
> > > for
> > > all the real memory being allocated.
> > >
> >
> > in domain config file, you can give memory parameters this way:
> > - <number>: memory unit is Byte
> > - <number>{k.K}: memory unit is Kilobyte
> > - <number>{m.M}: memory unit is Megabyte
> > - <number>{g.G}: memory unit is Gigabyte
> >
>
> oops, i took another look, and looks like the default memory unit is
> Kilobyte, if you dont specify. if so, it is impossible to give the
> maxmem memory in Byte unit, and the configuration above is probably
> *invalid* because that amount of memory is way too much.
hmm.. another oops :~p
the unit for programming interface is KB, but for *domain*
configuration, if you dont specify then the memory unit is MB. so you
should adjust your domain config file, and give it another shoot.
sorry for so much confuses ;-)
aq
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|