From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Domain-0 kernel boot failurewithxen-unstableandlinux-2.6.18-xen Date: Thu, 14 Jan 2010 11:26:12 +0000 Message-ID: References: <34CA9509B98113kanno.masaki@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <34CA9509B98113kanno.masaki@jp.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: Masaki Kanno , Jan Beulich Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 14/01/2010 11:07, "Masaki Kanno" 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