From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Need help in debugging partially blocked hypervisor Date: Wed, 21 Oct 2009 14:28:00 +0100 Message-ID: References: <200910211507.05738.dietmar.hahn@ts.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200910211507.05738.dietmar.hahn@ts.fujitsu.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: Dietmar Hahn , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 21/10/2009 14:07, "Dietmar Hahn" wrote: > I need some help in debugging a strange hypervisor behavior together > with using fully virtualized performance counters. > > For info I use SLES11, means xen-3.3.1 and linux-2.6.27.19-5... on a > Intel nehalem machine. > I tried the hypervisor from xen-unstable but the machine didn't boot. That in itself is frankly more of a concern to me. Probably recent irq-handling changes, or some other platform change, has broken boot on some machines. If we don't get reports and testing help with that, it'll end up broken in the next major stable release too, which we really don't want. Meanwhile, can you at least boot with 3.4? At least we still maintain that. And do a debug build (debug=y make ...) so that the backtraces from the 'd' debug key are more meaningful. -- Keir