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


[Xen-devel] Weird RAM handling with Xen 3.4.3-RC3

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Weird RAM handling with Xen 3.4.3-RC3
From: Thomas Goirand <thomas@xxxxxxxxxx>
Date: Fri, 02 Apr 2010 04:06:55 +0800
Delivery-date: Thu, 01 Apr 2010 13:07:15 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=cNbWo5ATR WpazeZno/9rAKgirTA=; b=sO65XNRAJspVSagZjWwudY+vnSxft2x6QPw2CGq9y fjkHiIKkiOWZIX5Oju6DAnbXzmKx5pu+Pf1zBOKbn4d6tvHP+wBRfQ/bcddHkM5d jXoWhKUpMUxKQR4DFynklutZMQo2jxSB9eQ8N3zE7VxciC7fUZJQGfKAL8Alsr8n Vk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=goirand.fr; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=sDM 3tXc7uoXxJMGbD2DTGK352gcjFmq2i0rGx0FW6xzlNQVO5C5kte8kThcrioCV5m0 /mKCI1LjItLeSzmksmvOcb4hvvzVjIsyLkZ8CMgl0CCw8c46J/dXTtjkF8mqOz2j aR9iviynAc+kyRFePXuUcoka0bAl1LWm+rxDp4kM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19380.52196.965181.226230@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=98EF9A49
Organization: GPLHost
References: <4BB11706.5020301@xxxxxxxxxxxxxxxxxxxxxx> <C7D7600A.ECD8%keir.fraser@xxxxxxxxxxxxx> <19380.52196.965181.226230@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird (X11/20090707)

Using the latest Debian SID Xen kernel (pv_ops 2.6.32-4) that I compiled
in Lenny, I had weird RAM handling issues. Let me explain.

If in grub, I put:

kernel          /boot/xen-3.4-amd64.gz dom0_mem=2048M

then when starting KDM, it gets stuck and doesn't work. If I press e in
grub, remove the dom0_mem part, then my laptop is able to boot and start
X window. Quite annoying, because I quite want to use the directive. It
might be linked to the experimental version of the graphic driver that
I'm using, but I also read that others had issues with X, so I thought
this could be interesting.

Then another very strange behavior. Once I start using xend, I do:

root@GPLHost:buzzig>_ ~# xm info
total_memory           : 3990
free_memory            : 131
root@GPLHost:buzzig>_ ~# xm list
Name     ID   Mem VCPUs  State    Time(s)
Domain-0  0  3800     2  r-----   54.8
root@GPLHost:buzzig>_ ~# xm mem-set Domain-0 2048
root@GPLHost:buzzig>_ ~# xm list
Name     ID   Mem VCPUs  State    Time(s)
Domain-0  0  2048     2  r-----   56.3
root@GPLHost:buzzig>_ ~# xm info
total_memory           : 3990
free_memory            : 1113

After I set my dom0 to use 2048 MB of RAM, I get only 1113 MB of free
RAM. It as if a part of the RAM (829 MB of RAM) has gone! Quite wacko
isn't it? Could it be that the memory management is broken somehow? What
is going on here?

I posted the above to the Debian pkg-xen list, and Ian suggested me to
also send it here.


Xen-devel mailing list

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