From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen 4.1 regression - can't boot on 1TB anymore (Xen 4.0 could). Date: Wed, 28 Mar 2012 10:34:08 -0400 Message-ID: <20120328143408.GF18161@phenom.dumpdata.com> References: <20120327181332.GA6014@phenom.dumpdata.com> <4F73273B020000780007B70A@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4F73273B020000780007B70A@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: tim@xen.org, xen-devel@lists.xensource.com, keir@xen.org, david.vrabel@citrix.com List-Id: xen-devel@lists.xenproject.org On Wed, Mar 28, 2012 at 01:59:07PM +0100, Jan Beulich wrote: > >>> On 27.03.12 at 20:13, Konrad Rzeszutek Wilk wrote: > > With Xen 4.0 we could boot up dom0 with 1TB of memory. But with > > Xen 4.1 that is no longer the case. Any ideas of what might be the culprit? > > > > Please see attached logs. > > Is this with the same kernel? I suspect not, in particular because of No, it is a pvops kernel (the older was a 2.6.32 classic one). > > (XEN) Phys-Mach map: ffffea0000000000->ffffea007e5acc80 > > vs > > (XEN) Dom0 memory clipped to 130846720 pages > > (the former suggesting a kernel making use of XEN_ELFNOTE_INIT_P2M, > i.e. a forward ported one based on ours, the latter suggesting one > that doesn't, e.g. pv-ops). If booting fails completely, I'd suppose > the clipping calculation might be off by a few pages. Does output look > the same with "sync_console"? If so, does "watchdog" allow you to > get a stack trace and register dump of where execution hangs? Ok, will try those out. > > I also suppose that the second kernel boots fine when you pass > dom0_mem= with a value below 400G. It does indeed. Thought the value that was used was a more conservative of 4G. > > Jan