From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [timer/ticks related] dom0 hang during boot on large 1TB system Date: Tue, 22 Dec 2009 10:03:42 -0800 Message-ID: <4B3109FE.70605@goop.org> References: <4B30F5A2020000780002736B@vpn.id2.novell.com> <526a5845-c007-4740-b0a2-f6f1cf372a08@default> <4B3109CD02000078000273FF@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B3109CD02000078000273FF@vpn.id2.novell.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: Jan Beulich Cc: kurt.hackel@oracle.com, Dan Magenheimer , Xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org On 12/22/2009 09:02 AM, Jan Beulich wrote: > No, that won't help. I'm referring to things like Dom0 accesses to the > M2P table it sees, which doesn't cover even nearly all memory. I can't > say whether that can go without problem, but without closely looking > at it I don't think you can assume this would work. Likewise I would > suspect tools issues (if you use the tools from xen-unstable et al), > though I have no precise pointer right now at specific issues. > 32-bit dom0 is the standard use model for Citrix product, and I think people tend to run it even with xen-unstable. Its a fairly well-tested combination. J