xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williams <awilliams@iweb.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: Possible regression: XEN 4.0.0 total_memory decrease
Date: Thu, 15 Apr 2010 13:42:01 -0400	[thread overview]
Message-ID: <4BC74FE9.5090603@iweb.com> (raw)
In-Reply-To: <4BC74DD5.3020809@iweb.com>

Hi,

I also want to add, my build process is practically automated. The only 
difference I had to make for 4.0.0 was:

- Install Debian package dependencies: uuid-dev iasl gcc-multilib

Let me know if you need more information.

Thanks.


Alex Williams wrote:
> Hello,
> 
> Both builds run a 64-bit Xen kernel and 64-bit Dom0 kernel.
> 
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 
> 0xffffffff805d388c
> 
> As for the RAM:
> 
> Xen 3.4.2: (XEN) System RAM: 3946MB (4041012kB)
> Xen 4.0.0: (XEN) System RAM: 4084MB (4182064kB)
> 
> I have also verified with only 2048MB installed in the system. Here are 
> the results:
> 
> Xen 3.4.2: (XEN) System RAM: 2036MB (2084912kB)
> Xen 4.0.0: (XEN) System RAM: 1898MB (1943860kB)
> 
> Still 150MB RAM missing... it appears this problem is static and 
> independant of the amount of RAM installed in the system.
> 
> Regards,
> 
> 
> 
> Keir Fraser wrote:
>> Are the hypervisor and dom0 kernel 64-bit or 32-bit? Xen prints a message
>> "System RAM: xxx" early during boot. Do these differ significantly for 
>> you
>> between 3.4.2 and 4.0.0?
>>
>>  K.
>>
>> On 15/04/2010 16:54, "Alex Williams" <awilliams@iweb.com> wrote:
>>
>>> Hello,
>>>
>>> I noticed a significant *decrease* (150MB) in "total_memory" on a host
>>> build using XEN 4.0.0 with kernel 2.6.18.
>>>
>>> Here are the details:
>>>
>>> Server = 4096MB RAM
>>> XEN 3.4.2 + kernel 2.6.18: xm info | grep total_memory = 4084
>>> XEN 4.0.0 + kernel 2.6.18: xm info | grep total_memory = 3946
>>>
>>> The exact same kernel config file was used for both builds. I also made
>>> sure there is absolutely no difference on the hosts (while the builds
>>> are created on a different machine).
>>>
>>> This seems like a regression, unless someone can provide suggestions on
>>> how to correct this?
>>>
>>> Thanks.
>>>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
> 

-- 
Alexander Williams
IT Architecture Specialist
Spécialiste de l'Architecture TI
http://www.iWeb.com/

  reply	other threads:[~2010-04-15 17:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 15:54 Possible regression: XEN 4.0.0 total_memory decrease Alex Williams
2010-04-15 16:33 ` Keir Fraser
2010-04-15 17:33   ` Alex Williams
2010-04-15 17:42     ` Alex Williams [this message]
2010-04-15 18:05     ` Keir Fraser
2010-04-15 18:23       ` Keir Fraser
2010-04-16  7:53         ` Jan Beulich
2010-04-16 17:37           ` Keir Fraser
2010-04-19  7:35             ` Jan Beulich
2010-04-19  7:51               ` Keir Fraser
2010-04-15 18:26       ` Alex Williams
2010-04-15 18:34         ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BC74FE9.5090603@iweb.com \
    --to=awilliams@iweb.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=keir.fraser@eu.citrix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).