From mboxrd@z Thu Jan 1 00:00:00 1970 From: andrew thomas Subject: Re: [Xen-devel] Re: Hypervisor hangs on startup, 2.6.32-5-xen dom0 kernel panic Date: Tue, 11 Jan 2011 10:39:29 -0800 Message-ID: <4D2CA3E1.4030604@oracle.com> References: <4D0AD782.8030204@wavecon.de> <4D0B3DF2.5000100@wavecon.de> <20101217115132.GG2754@reaktio.net> <4D0B7E79.4010106@wavecon.de> <20101220201819.GN2754@reaktio.net> <1292937209.4500.1852.camel@zakaz.uk.xensource.com> <4D2496DE.1000007@wavecon.de> <20110111163828.GF10897@dumpdata.com> <4D2C8D6C.1080906@wavecon.de> <20110111172002.GJ10897@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110111172002.GJ10897@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: Arno Toell , "xen-devel@lists.xensource.com" , Ian Campbell , "xen-users@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Konrad Rzeszutek Wilk wrote: > Hmm, let me ping Andrew, he might know. Andrew, do you remember what fix > you needed to get Dom0 to boot when you had more than 64GB of memory > with the VT-d enabled? > > From the xen-4.0-testing.hg repo: changeset: 21403:e7d9d8d46730 user: Keir Fraser date: Wed Dec 15 10:31:59 2010 +0000 files: xen/arch/x86/domain_build.c description: x86/iommu: account for necessary allocations when calculating Dom0's initial allocation size As of c/s 21812:e382656e4dcc, IOMMU related allocations for Dom0 happen only after it got all of its memory allocated, and hence the reserve (mainly for setting up its swiotlb) may get exhausted without accounting for the necessary allocations up front.