|
Okay, this at least clarifies there is a (relatively big) RMRR. There is
a change to the handling of these among the ones that'll become
4.3.3 - mind giving
a try on top of your 4.3.2 (or trying the tip of the stable-4.3 branch)?
> What else did I miss that could be useful info?
At least the resolution of these addresses
(XEN) traps.c:3061: GPF (0000): ffff82c4c0186a91 -> ffff82c4c0218daa
(XEN) traps.c:3061: GPF (0000): ffff82c4c0186a91 -> ffff82c4c0218daa
into (symbol,offset) pairs, so we can at least make a first guess at
whether these are in any way related to your problem.
Booted into xen compiled with xen-syms.
Hope this is right. :)
root@xen-3:~# xl dmesg |grep trap |grep GPF
(XEN) traps.c:3061: GPF (0000): ffff82c4c0186ae1 -> ffff82c4c0218e3a
(XEN) traps.c:3061: GPF (0000): ffff82c4c0186ae1 -> ffff82c4c0218e3a
root@xen-3:~# gdb xen-4.3.0/xen/xen-syms
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
Reading symbols from /root/xen-4.3.0/xen/xen-syms...done.
(gdb) list *0xffff82c4c0186ae1
0xffff82c4c0186ae1 is in do_general_protection (traps.c:2597).
2592 case MSR_EFER:
2593 rdmsr_normal:
2594 /* Everyone can read the MSR space. */
2595 /* gdprintk(XENLOG_WARNING,"Domain attempted RDMSR %p.\n",
2596 _p(regs->ecx));*/
2597 if ( rdmsr_safe(regs->ecx, msr_content) )
2598 goto fail;
2599 regs->eax = (uint32_t)msr_content;
2600 regs->edx = (uint32_t)(msr_content >> 32);
2601 break;
(gdb) quit
root@xen-3:~#
I am a noob when working with source code. How do I bump my xen up to 4.3.3?
Thanks,
| 
