From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools) Date: Tue, 22 Jun 2010 20:16:29 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kathy Hadley , George Dunlap Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 22/06/2010 20:10, "Kathy Hadley" wrote: > Looking at the output to the serial channel, I see the following message > (which was not output on an earlier version of Xen [xen-unstable downloaded > May 27] where I can successfully start other domains): > > (XEN) traps.c:2301:d2 Domain attempted WRMSR c0000080 from 0x0000080000000000 > to 0x0000080000000800. > > Would this explain why the new domain appears to hang? I think it might be a side effect of some MSR cleanup patches in the hypervisor, and pribably not related to your hang. You'll need to track down where your guest kernel is hanging. Add some early printks or maybe use the xenctx tool to get an EIP value and map that to a location in the kernel code. -- Keir