From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Subject: Re: Xen 3.0.1 Error creating domain: (12, 'Cannot allocate memory') Date: Tue, 28 Feb 2006 09:58:17 +1300 Message-ID: <440367E9.7050407@rimuhosting.com> References: <4402CC1E.3050604@rimuhosting.com> <89a93fa1ac5de98979696b82f1b18642@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <89a93fa1ac5de98979696b82f1b18642@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > > On 27 Feb 2006, at 09:53, Peter wrote: > >> Hi. I have a domU that refuses to start up. It reports an error >> allocating memory. There appears to be sufficient memory in dom0 as >> well as on the host. I can restart other domUs no problem. >> >> To resolve the issue I'm having to restart the whole server. Which is >> a bit disruptive. > > How many domains are already running? Xen's own private heap can be > exhausted even when there is guest memory available. > > -- Keir > I have 41 domains running (including dom0). Is there a way to help avoid Xen's private heap getting exhausted? e.g. increase the memory allocated to dom0? Or a setting change? or? -- Peter