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/
Home Products Support Community News


Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't

On Tue, Apr 13, 2010 at 09:20:33AM +0800, Thomas Goirand wrote:
> Jeremy Fitzhardinge wrote:
> > On 04/11/2010 02:49 AM, Thomas Goirand wrote:
> >>> Excellent.
> >>>     
> >> Could this be also the reason why I had very funky memory management
> >> (eg: some RAM missing between "xm list" and "xm info")?
> >>   
> > 
> > I don't think so.  Before I added the "unused memory freeing" code, then
> > you'd see memory assigned to a domain that the domain itself couldn't
> > use, and so it was effectively wasted.  With the memory-freeing in
> > place, the "xm list" and the domain's internal view of memory should be
> > basically the same.
> > 
> > Either way, it shouldn't have any effect on the global memory accounting
> > shown by xm info.
> > 
> >     J
> Then do you have an idea why "xm info" shows a bit more, 900 MB free /
> 3990 MB total, while "xm list" shows only a 2048 dom0 running??? I'm not
> talking about just few bytes here, but one third of my RAM gone ...
> What's going on?

Please paste "xm list" and "xm info"

-- Pasi

Xen-devel mailing list

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