>>> On 22.05.17 at 10:39, <xudong....@intel.com> wrote: > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
Not this - Xen is unavoidably going to go down in such a case, yet your log has no hint at all what kind of problem Dom0 experienced (e.g. whether one of the injected #MC-s caused this). > (XEN) ----[ Xen-4.9-rc x86_64 debug=y Tainted: MCE ]---- > (XEN) CPU: 0 > (XEN) RIP: e008:[<0000000065eb1e13>] 0000000065eb1e13 > ... > (XEN) Pagetable walk from 00000000682ab009: > (XEN) L4[0x000] = 000000102c961063 ffffffffffffffff > (XEN) L3[0x001] = 000000005f812063 ffffffffffffffff > (XEN) L2[0x141] = 0000000000000000 ffffffffffffffff Here you're apparently hitting a firmware bug: While RIP points into runtime services memory, CR2 doesn't: (XEN) 0000065eb8000-00000682acfff type=0 attr=000000000000000f You may try working around this via one of "reboot=acpi" or "efi=no-rs" on the hypervisor command line. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
