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] Need help in debugging partially blocked hypervisor

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Need help in debugging partially blocked hypervisor
From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
Date: Thu, 22 Oct 2009 08:23:07 +0200
Delivery-date: Wed, 21 Oct 2009 23:24:12 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=dietmar.hahn@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1256192717; x=1287728717; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Dietmar=20Hahn=20<dietmar.hahn@xxxxxxxxxxxxxx> |Subject:=20Re:=20[Xen-devel]=20Need=20help=20in=20debugg ing=20partially=20blocked=20hypervisor|Date:=20Thu,=2022 =20Oct=202009=2008:23:07=20+0200|Message-Id:=20<200910220 823.07962.dietmar.hahn@xxxxxxxxxxxxxx>|To:=20xen-devel@li sts.xensource.com|MIME-Version:=201.0; bh=rYGgd4wk0X6O8EmycX9ZdiJAjxjklsTqdoH2ZNSqSH0=; b=WAkgfa6I9gAoQ9EieDSoFPM03NQGI/OfF0cMiGwf/Lujxkb/wEZgRQAf jHBN66tZrydPcVt8UFYCPFE8Z2TMcFGh8tDfBx/aMvgJbe4J1AN63qLvP +D5CQiUoZft96gMX7pqMyusTFTzRNtwNZZ1A01gDj2Nn13JobgR4NC+rW 8qFBwG64uIWmSuE7idPU2IZ4KxxWNXfu6+lORsGI9SiDt3emaOF1O15Qi JM0ZO5rHBxVBJ7l2H/oZoq6yBCiiQ;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:To:Subject:From:Date:MIME-Version: Content-Type:Message-Id; b=lQAhG0SiDzaf+FtQjKN2hXbRgnG7zupy99fdmaAGGl2OJqVEPfvHOldX bfLfCp0BqrZ2c4breplyICKwFq4C0i2Y2aXdhkc4QzPegkKBMiwtgfKLM fc+t95V9AuD2Y6mnMvEhEv+l46rSTVIedATvfR77uIMeMmW9RA64zAWDF f4PndPbw5vDgY0DBrPQon6js2THj3EMNDtFd2jvSBX84pTlsee7saY4/p f4QUttKia3RybB3Q3ZxP84nHWegYe;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Am 21.10.2009 schrieb Keir Keir Fraser:
> On 21/10/2009 14:07, "Dietmar Hahn" <dietmar.hahn@xxxxxxxxxxxxxx> 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

OK, I tried xen-3.4-testing.hg and the system booted fine ;-)
Then I did a fresh hg pull from xen-unstable and the boot stopped in
the linux kernel.
Attached are the loggings from the serial console for both hypervisors.
The tests with the performance counters needs more time for some preparations.
Thanks.
Dietmar.

-- 
Company details: http://ts.fujitsu.com/imprint.html

Attachment: xen-3.4.2-rc2-log.txt
Description: Text document

Attachment: xen-unstable-log.txt
Description: Text document

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