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-users] Java memory allocation in guest domain with mem and max-

To: Roberto Lo Giacco <rlogiacco@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Java memory allocation in guest domain with mem and max-mem properties
From: Robert Read <rread@xxxxxxxxxxxxx>
Date: Thu, 17 Jul 2008 09:58:02 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 17 Jul 2008 09:58:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <a217661a0807170928y78824310p15b8b8af6e899118@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <a217661a0807170928y78824310p15b8b8af6e899118@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Jul 17, 2008, at 09:28 , Roberto Lo Giacco wrote:

* The question

Have I missed something (I'm quite new to xen) in my configuration
files, like using mem-min and mem-max instead of mem and mem-max?
Anyone out there has already encountered this behavior and solved it?
Does this error depends on the used JVM or is there any solution which
is not just "set your DomU memory to a fixed value of 2GB" (btw, this
is the only solution which comes to me)?

Thank you in advance for your patience guys (and ladies, if any!)

It's possible this has be implemented in more recent releases, but 3.0 does not support guest autoballooning. In other words, you'll need to track guest memory and add more manually, at least in 3.0.

Automating this shouldn't be too difficult, though, so if this hasn't been done yet in xen 3.3 then we really should find some volunteers to take this on...


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>