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, <dario.faggi...@citrix.com> 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
