From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Error booting Xen Date: Tue, 19 Jan 2016 15:07:04 +0000 Message-ID: <569E5118.4030704@citrix.com> References: <569D2A49.1090409@citrix.com> <1453141749.11427.92.camel@citrix.com> <569E4A0102000078000C8917@prv-mh.provo.novell.com> <1453215095.11427.144.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1453215095.11427.144.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Harmandeep Kaur Cc: Dario Faggioli , Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 19/01/16 14:51, Dario Faggioli wrote: > On Tue, 2016-01-19 at 06:36 -0700, Jan Beulich wrote: >>>>> On 18.01.16 at 19:29, wrote: >>> >>> Yeah, but again, it was booting as dom0 with another Xen... doesn't >>> that mean that Xen at least has a role in exposing it? >>> >>> Also, what would you think it's better to try next... try another >>> kernel? >> Figure out what the GP fault that gets recovered from is being >> caused by. >> > Yep, thanks. > > Harmandeep is looking at (learning how to do) this already. If you feel > like sharing any knowledge/giving any advice on how to best achieve > that, I'm sure she'll appreciate (but if you can't or don't have time, > no problem :-D). First, locate exactly where the fault is `addr2line -e xen-syms ffff82d0801af585` will give you a file/line reference. xen-syms must be from the same build of the hypervisor that you booted. ~Andrew