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 22:53:40 +1300 Message-ID: <44041DA4.7080604@rimuhosting.com> References: <4402CC1E.3050604@rimuhosting.com> <89a93fa1ac5de98979696b82f1b18642@cl.cam.ac.uk> <440367E9.7050407@rimuhosting.com> <9f2c05a41fb2368b5bdf73af65ca1bcf@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: <9f2c05a41fb2368b5bdf73af65ca1bcf@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: >> 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? > > Unfortunately not, but I'd expect you to be able to create more than 41 > domains. When we've tested this we've been able to create about double > that number. We've hit this before. I'm not sure if it was on the same host server or not. Is there any other information we can collect that would be useful resolving this? Or are there any actions we can try to see if we can fix the issue (other than a reboot of the host server which seems to do the job, but is obviously a bit disruptive to other domUs). -- Peter