WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add supp

To: Kathy Hadley <Kathy.Hadley@xxxxxxxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 22 Jun 2010 20:16:29 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 22 Jun 2010 12:17:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <D3E384327F5C6D48AADCEA84160B7D73014714A7@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsNbwzA3ljXALi4RuWicdpNTkcsxQAAMAgmAAAadBAAAEvrHQAABmIAAACZp+4AApBeQAAbRt37ARRzbBAAAJZcJg==
Thread-topic: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
User-agent: Microsoft-Entourage/12.24.0.100205
On 22/06/2010 20:10, "Kathy Hadley" <Kathy.Hadley@xxxxxxxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>