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 bootfailurewithxen-unstableandlinux-2.6.

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Domain-0 kernel bootfailurewithxen-unstableandlinux-2.6.18-xen
From: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date: Thu, 14 Jan 2010 20:42:07 +0900
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 14 Jan 2010 03:42:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C774AFD4.6600%keir.fraser@xxxxxxxxxxxxx>
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>
References: <C774AFD4.6600%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thu, 14 Jan 2010 11:26:12 +0000, Keir Fraser wrote:

>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.
>

Thanks Keir.  I will try it tomorrow.

Best regards,
 Kan



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