[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Problems booting 32-bit PV; just me or more widespread?
On 09/02/2018 08:32 PM, Andy Smith wrote: > > This one should work though as it's their netboot installer: > > > http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-i386/current/images/netboot/xen/ > > When I do xl create with this one (direct kernel boot), I get this > crash in the xl dmesg: > > (XEN) domain_crash_sync called from entry.S: fault at ffff82d0803510d8 > x86_64/compat/entry.S#compat_create_bounce_frame+0xd9/0xed > (XEN) Domain 73 (vcpu#0) crashed on cpu#4: > (XEN) ----[ Xen-4.10.1 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 4 > (XEN) RIP: e019:[<00000000c1038ef9>] > (XEN) RFLAGS: 0000000000000292 EM: 1 CONTEXT: pv guest (d73v0) > (XEN) rax: 00000000c1cd3540 rbx: 00000000c18a01e0 rcx: 0000000000000000 > (XEN) rdx: 0000000000000000 rsi: 00000000c1bfdeec rdi: 00000000c1bfdf34 > (XEN) rbp: 00000000c1bfdf10 rsp: 00000000c1bfdecc r8: 0000000000000000 > (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 > (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 > (XEN) r15: 0000000000000000 cr0: 0000000080050033 cr4: 00000000003526e0 > (XEN) cr3: 0000003f56d54000 cr2: 0000000000000014 > (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=c1bfdecc: > (XEN) 00000000 c1038ef9 0001e019 00010092 c1cd3540 00000000 00000000 > 00000000 > (XEN) 00000000 00000000 00000000 ffffffff c1bfdf24 c1cd3540 c1cd3540 > c1bfdf30 > (XEN) c1bfdf34 c1bfdf50 c1039a77 c1bfdf3c c1bfdf38 c1bfdf40 0000202e > 00001000 > (XEN) 00000000 00000000 80000008 00000000 00000000 00000000 00000000 > c248a000 > (XEN) c1eda000 c1bfdffc c1cf5222 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 c248a000 c1eda000 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 > > Any ideas about that one? > No. You will need to find out what RIP points to in the vmlinux. And possibly unwrap the stack. (BTW, when replying, please include whoever you are replying to, not just the list) -boris _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |