[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] RE:Memory assignment

To: gepatino@xxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
From: Sweekar Pinto <sweekarpinto@xxxxxxxxx>
Date: Thu, 22 Sep 2005 10:12:37 +0530
Delivery-date: Thu, 22 Sep 2005 04:40:21 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=jWiXdMSWayVdONwvfbNWF/H8cLdgnZWiaMGKsfOPFmrRfrxeTTdEwMGwc/iPrc1jFDnwriHxiIgcIIjbBgReWw+uDh0Fp74gKD/iFR5CR9e8z/oshDGVJoRvH4IP293cGJXxCl2Fw6r4e8R6Zxp73/aPFZ9dWFMC5M3VGsKXH1A=
List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,
I'm not sure about this... but even I've experienced problems allocating memory using xm mem-set..
You could directly write to proc... this might help

# echo 2048M > /proc/xen/balloon

all the best,
Sweekar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

Prev by Date: Re: [Xen-users] rhel4 and compile patch
Next by Date: [Xen-users] conceptualizing dom0
Previous by thread: [Xen-users] Fedora and Xen slowdown
Next by thread: [Xen-users] conceptualizing dom0
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.