To get a better idea of what is wrong can you run a test for me please? That is to boot the kernel+Xen without the 'dom0_mem' flag so that it crashes. But lets make sure that on the Linux command line you have: "console=hvc0 earlyprintk=xen debug loglevel=8" and for extra measure on the Xen command line pls also append: "sync_console console=com1 com1=38400,8n1 loglvl=all guest_loglvl=all".
That should pinpoint where we fail. Lastly, Stefan, is the kernel-debuginfo available somewhere easily? I am mighty curious what EIP: ffffffff816415e1 is? I figured it has to be pin_pagetable_pfn or xen_alloc_pte_init. And that the bug is somewhere in the E820 parsing where it includes 228000 as RAM. Also, it would be interesting to see if 'e820-mtrr-clip e820-verbose ' on the Xen command line resolves this as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1111470 Title: Precise kernel not bootable under Xen - alloc_l1_table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1111470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
