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] Domain-0 kernel boot failurewithxen-unstableandlinux-2.6

To: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 14 Jan 2010 11:26:12 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 14 Jan 2010 03:26:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <34CA9509B98113kanno.masaki@xxxxxxxxxxxxxx>
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: AcqVCdKLjmcHRmc8Q1i0H5YEAzLMqwAAo2sA
Thread-topic: [Xen-devel] Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen
User-agent: Microsoft-Entourage/12.23.0.091001
On 14/01/2010 11:07, "Masaki Kanno" <kanno.masaki@xxxxxxxxxxxxxx> wrote:

> Hi Jan,
> 
> Thu, 14 Jan 2010 09:05:32 +0000, "Jan Beulich" wrote:
> 
>> You forgot to tell us in what way the boot fails.
> 
> Oops!  Could you refer to the following about a serial log when the
> problem occurred?
> 
> http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00338.html
> 
> Accurately, the problem is not "Domain-0 kernel boot fails" but "Domain-
> 0 kernel boot does not start".

I don't know how much experience with kernel issues you have, but I would
take the EIP from the CPU0 guest dump in that log file (the EIP is c01edc67)
and look at that code address in a disassembly of the dom0 kernel image
(objdump -d vmlinux). Seeing what function you're in would be a good start.
'addr2line -e vmlinux c01edc67' would also be useful: tells you the source
file and line number.

 -- Keir




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