Hello, I can also reproduce with Xen 4.8.2-10.el6: (XEN) d6v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from 0000000000000028: (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d08023d440 cpufreq.c#create_bounce_frame+0x137/0x146 (XEN) Domain 6 (vcpu#0) crashed on cpu#8: (XEN) ----[ Xen-4.8.2-10.el6 x86_64 debug=n Not tainted ]---- (XEN) CPU: 8 (XEN) RIP: e033:[<ffffffff8103f261>] (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d6v0) (XEN) rax: 0000000000000000 rbx: ffffffff81e05720 rcx: 0000000000000000 (XEN) rdx: 0000000000000030 rsi: ffffffff82203efc rdi: ffffffff8241d460 (XEN) rbp: ffffffff82203ec8 rsp: ffffffff82203e10 r8: 0000000000000000 (XEN) r9: ffffffff82203f00 r10: 00000000ffffffff r11: ffffffff82203f04 (XEN) r12: ffffffff82203e78 r13: ffffffff82203e7c r14: ffffffff82203e80 (XEN) r15: ffffffff82203e84 cr0: 000000008005003b cr4: 00000000000026e0 (XEN) cr3: 0000000c15f0d000 cr2: 0000000000000028 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff82203e10: (XEN) 0000000000000000 ffffffff82203f04 0000000000000000 ffffffff8103f261 (XEN) 000000010000e030 0000000000010092 ffffffff82203e58 000000000000e02b (XEN) 0000000000000000 ffffffff8241d460 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff8241d460 ffffffff82203f04 (XEN) ffffffff82203f00 ffffffff82203efc ffffffff82203ef8 ffffffff82203f40 (XEN) ffffffff8103fce6 ffffffff82203f14 ffffffff82203f10 ffffffff82203f0c (XEN) ffffffff82203f08 0000000000003028 0000000000000000 0000000080000008 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff82203ff8 ffffffff8246c490 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0f00000060c0c748 ccccccccccccc305 (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc Karl On Tue, Jan 30, 2018 at 7:01 PM, Adi Pircalabu <adi at ddns.com.au> wrote: > Replicated on another Xen node, CentOS 6.9 running Xen-4.6.6-8.el6. xl > dmesg: > (XEN) d38v0: unhandled page fault (ec=0000) > (XEN) Pagetable walk from 0000000000000028: > (XEN) L4[0x000] = 0000000000000000 ffffffffffffffff > (XEN) domain_crash_sync called from entry.S: fault at ffff82d080230983 > create_bounce_frame+0x12b/0x13a > (XEN) Domain 38 (vcpu#0) crashed on cpu#2: > (XEN) ----[ Xen-4.6.6-8.el6 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 2 > (XEN) RIP: e033:[<ffffffff8103f261>] > (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d38v0) > (XEN) rax: 0000000000000000 rbx: ffffffff81e05720 rcx: 0000000000000000 > (XEN) rdx: 0000000000000030 rsi: ffffffff82203efc rdi: ffffffff8241d460 > (XEN) rbp: ffffffff82203ec8 rsp: ffffffff82203e10 r8: 0000000000000000 > (XEN) r9: ffffffff82203f00 r10: 00000000ffffffff r11: ffffffff82203f04 > (XEN) r12: ffffffff82203e78 r13: ffffffff82203e7c r14: ffffffff82203e80 > (XEN) r15: ffffffff82203e84 cr0: 000000008005003b cr4: 00000000000426e4 > (XEN) cr3: 000000049c571000 cr2: 0000000000000028 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > (XEN) Guest stack trace from rsp=ffffffff82203e10: > (XEN) 0000000000000000 ffffffff82203f04 0000000000000000 ffffffff8103f261 > (XEN) 000000010000e030 0000000000010092 ffffffff82203e58 000000000000e02b > (XEN) 0000000000000000 ffffffff8241d460 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffff8241d460 ffffffff82203f04 > (XEN) ffffffff82203f00 ffffffff82203efc ffffffff82203ef8 ffffffff82203f40 > (XEN) ffffffff8103fce6 ffffffff82203f14 ffffffff82203f10 ffffffff82203f0c > (XEN) ffffffff82203f08 0000000000003026 0000000000000000 0000000080000008 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffff82203ff8 ffffffff8246c490 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0f00000060c0c748 ccccccccccccc305 > (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > (XEN) cccccccccccccccc cccccccccccccccc cccccccccccccccc cccccccccccccccc > > --- > Adi Pircalabu > > > On 31-01-2018 10:37, Adi Pircalabu wrote: > >> Hi, has anyone managed to boot 4.15.0 as Xen PV domU? I've been >> loading 4.14.12 to 4.14.15 ELRepo builds no problem, but 4.15 crashes. >> Replicates on 2 CentOS 7.4 hypervisors running xen-4.6.6-9.el7.x86_64 >> on: >> - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz >> - AMD Phenom(tm) II X6 1090T Processor > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20180202/37f80213/attachment-0002.html>