[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] out of memory with xen
- To: "Maarten Vanraes" <maarten@xxxxx>
- From: "Arie Goldfeld" <arik.goldfeld@xxxxxxxxx>
- Date: Wed, 27 Jun 2007 11:04:26 +0300
- Cc: xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Wed, 27 Jun 2007 01:02:31 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=bz4YVkiNbYArrPxb6YaWfz/G0EtKb45uF8P1Og8S9HuEk/vEiQFuE3zxEobNWtdksN8i748a1M2k3RQdMxCxLDk3JZeii2Hu41bdQHA2Po78nM/WM/o4IFh2DZ01TmWZe4VKqBi4lb6rql2d/SSThj46Y1dFBkupG1cdLQoYOdw=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
You could use dom0_mem grub parameter to restrict the size of RAM dom0 occupies; it looks somethings like this:
kernel /xen.gz dom0_mem=400000
On 6/27/07, Maarten Vanraes <maarten@xxxxx> wrote:
our xen server has 8GB RAM.
dom0 is not doing anything, but has cached about 4.9GB of the ram, which
results in failure to create new hosts.
i'm using file based storage, and i've read in the mailing list archive about
the problem being /dev/loop being used internally in xen.
is there a way to flush this cache? is there already a fix for the extreme
caching of these devices?
I see that lvm is a possible workaround, but i'd rather not do this right now.
Plus it is not so easy to convert 500GB into lvm...
any solutions yet?
Sincerely,
--
Maarten Vanraes
BA NV: IT & Security
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
