From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dietmar Hahn Subject: Re: Need help in debugging partially blocked hypervisor Date: Thu, 22 Oct 2009 09:21:17 +0200 Message-ID: <200910220921.17217.dietmar.hahn@ts.fujitsu.com> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" 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: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org > On 22/10/2009 07:23, "Dietmar Hahn" wrote: > > > 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. > > Okay, so output just dies early during dom0 boot. I guess if you try the 'd' > debug key that you get no output from that either (CTRL-a three times > followed by d)? Sorry, CTRL-a doesn't work. > > Does xen-unstable work on other machines with that dom0 kernel, do you know? > It's not at this point clear whether the issue is related to the hardware or > the particular dom0 kernel. Yes it works on older machines, I can send you the log. > > If you haven't seen that dom0 kernel work with xen-unstable on any system, > can I get that dom0 kernel from somewhere to give it a go? Perhaps your > exact dom0 kernel binary to start with, to make things as close as possibel > to your setup? If needed I can put the kernel on an outgoing ftp server. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html