The latest rawhide kernel-xen (kernel-xen-2.6-2.6.25-0.1.rc4.fc9), fails to boot on x86_64: [<ffffffff8142d7e0>] __alloc_bootmem_core+0x2c8 <-- [<ffffffff8142d7e0>] __alloc_bootmem_core+0x2c8 [<ffffffff8142d654>] __alloc_bootmem_core+0x13c [<ffffffff8142d946>] __alloc_bootmem_node+0x25 [<ffffffff812862ac>] sparse_index_alloc+0x48 [<ffffffff8142ea2c>] memory_present+0x51 [<ffffffff81429c1d>] paging_init+0x3d [<ffffffff81420e4c>] setup_arch+0x57b [<ffffffff8141980c>] start_kernel+0x84 [<ffffffff8141f850>] xen_start_kernel+0x32f Eduardo is investigating, but what's been determined so far: - It boots fine with Eduardo's original config, but not the stock fedora config - CONFIG_SPARSEMEM would look to be the obvious culprit, but Eduardo had that enabled in his config - It could be this: -CONFIG_PHYSICAL_START=0x200000 -CONFIG_PHYSICAL_ALIGN=0x200000 +CONFIG_PHYSICAL_START=0x1000000 +CONFIG_PHYSICAL_ALIGN=0x200000 but reverting that just makes it crash somewhere else
.config changes for x86_64 committed to Fedora CVS. Changed PHYSICAL_START and SPARSEMEM_VMEMMAP so it doesn't explode on boot.
kernel-xen 2.6.25-0.2.rc4.fc9xen package is on Rawhide.