Hi, Should I be able to boot a 686-pae i686 kernel on a xen domU (bullseye - but bookworm fails too)
(XEN) d46v0 Unhandled page fault fault/trap [#14, ec=0010] (XEN) Pagetable walk from 0000000001000000: (XEN) L4[0x000] = 0000000009790027 0000000000001f90 (XEN) L3[0x000] = 00000000097a4027 0000000000001fa4 (XEN) L2[0x008] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S: fault at ffff82d040271ed8 x86_64/compat/entry.S#compat_create_bounce_frame+0xd9/0xf6 (XEN) Domain 46 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.14.5 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e019:[<0000000001000000>] (XEN) RFLAGS: 0000000000000246 EM: 1 CONTEXT: pv guest (d46v0) (XEN) rax: 0000000001000000 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) rdx: 0000000000000000 rsi: 00000000c1f8d000 rdi: 0000000000000001 (XEN) rbp: 0000000000000000 rsp: 00000000c20a5ff0 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000001006e4 (XEN) cr3: 000000000f25b000 cr2: 0000000001000000 (XEN) fsb: 0000000000000000 gsb: 0000000000000000 gss: 0000000000000000 (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 (XEN) Guest stack trace from esp=c20a5ff0: (XEN) 00000010 01000000 0001e019 00010046 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 This is a minimal install - I've now tried both as a fresh install and upgrading from buster but I always get this same failure. The 4.19 buster kernel boots bullseye fine. Dom0 is bullseye. I cannot find anybody else reporting this so either I'm doing something wrong, doing something that is no longer supposed to work, or nobody is using xen any more... Assuming there isn't a simple solution, what do people think is the best way forwards: 1. Convert to using KVM instead - this seems to be more popular now - when I started using xen I don't think it even existed. 2. Convert my few remaining i686-pae images into amd64 images. Will KVM boot a 686-pae kernel? If not then it seems I need to do 2 first anyway. My processor says it supports VT-x although I don't see that in flags - perhaps because I'm looking in a dom0? So changing to KVM might need new hardware... Tim.
