From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Pierard de Maujouy Subject: Help Date: Thu, 25 Jun 2015 07:51:45 +0300 Message-ID: <558B88E1.4080306@yahoo.fr> References: <557FA708.7020101@yahoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z7z9E-0006oZ-9z for xen-devel@lists.xenproject.org; Thu, 25 Jun 2015 04:52:24 +0000 In-Reply-To: <557FA708.7020101@yahoo.fr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org My apologize for been to late for subscription confirmation. Resubmitting. Env : xen 4.5 + kernel 4.0.5 + xl stack, working dom0/domU. Level : Quite critical despite integration env as using source distro (gentoo) tmem is on xen command line, and reported in xl dmesg. tmem module in loaded via init script (open-rc). tmem has been added at the end of the kernel command line, though syntax may be wrong. ballooning on in dom0 cfg file. maxmem is defined in domU cfg file. maxmem>memory. RAM can be manually redistributed beetween dom0 & domU via mem-set command. When domU is forced to require more RAM than currently reported as available via its top command, domU RAM is not automatically resized. domU is expected to request dom0 for additionnal RAM before starting to use swap. Is ballooning feature misunderstood should misconfiguration be suspected, what should be investigated? Thks 4 ur attention, interest & support.