From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: Tracking "Cannot allocate memory" error in shadow_alloc_p2m_table Date: Fri, 12 Jan 2007 09:36:44 -0500 Message-ID: <45A79CFC.1000604@redhat.com> References: <45A4063D.8000207@redhat.com> <20070110113207.GD21843@york.uk.xensource.com> <45A71909.8070300@redhat.com> <20070112110702.GA18763@york.uk.xensource.com> <45A7878C.5070409@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45A7878C.5070409@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Steven Rostedt Cc: xen-devel@lists.xensource.com, Herbert Xu , Tim Deegan , Chris Lalancette List-Id: xen-devel@lists.xenproject.org OK, Herbert has been looking into this too, and he's discovered that it's a problem with the RHEL5 snapshot. The allocation of the shadow_enable is done later on in RHEL5 and thus the d->page_list is not empty, where as in the xen-unstable/testing version, shadow_enable is called in the hypervisor, so it is not affected by this bug. Thanks, -- Steve