>>> On 08.07.15 at 10:45, <li...@eikelenboom.it> wrote: > Here we go: > > (XEN) [2015-07-08 08:31:00.384] traps.c:3227: GPF (0000): ffff82d080195583 -> > ffff82d080239d85 > (XEN) [2015-07-08 08:31:00.384] traps.c:3227: GPF (0000): ffff82d080195583 -> > ffff82d080239d85 > > which leads to: > # addr2line -e /usr/lib/debug/xen-syms-4.6-unstable ffff82d080195583 > /usr/src/new/xen-unstable/xen/arch/x86/traps.c:2758 > > # addr2line -e /usr/lib/debug/xen-syms-4.6-unstable ffff82d080239d85 > ??:? > > Were /usr/src/new/xen-unstable/xen/arch/x86/traps.c:2758 leads to: > > case MSR_EFER: > rdmsr_normal: > /* Everyone can read the MSR space. */ > /* gdprintk(XENLOG_WARNING,"Domain attempted RDMSR %p.\n", > _p(regs->ecx));*/ > HERE --> if ( rdmsr_safe(regs->ecx, val) )
Right, so as Andrew suspected - we won't know whether that's legitimate/reasonable without knowing the MSR being accessed. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
